October 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3680) SOAP 1.2 fault reason xml:lang attribute not properly parsed on client side

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3680?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3680: ---------------------------------- Fix Version/s: jbossws-cxf-4.2.2 (was: jbossws-cxf-4.3) > SOAP 1.2 fault reason xml:lang attribute not properly parsed on client side > --------------------------------------------------------------------------- > > Key: JBWS-3680 > URL: https://issues.jboss.org/browse/JBWS-3680 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2.2 > > > See https://issues.apache.org/jira/browse/CXF-5186 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3690) XMLJavaTypeAdapter not working in Exception Classes

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3690?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3690: ---------------------------------- Fix Version/s: jbossws-cxf-4.2.2 (was: jbossws-cxf-4.3) > XMLJavaTypeAdapter not working in Exception Classes > --------------------------------------------------- > > Key: JBWS-3690 > URL: https://issues.jboss.org/browse/JBWS-3690 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Mustafa Musaji > Assignee: Mustafa Musaji > Fix For: jbossws-cxf-4.2.2 > > Attachments: cxf5219.diff, cxfTest.jar > > > @XMLJavaTypeAdapter usage in Exception Classes does not work when mapping to a class not in the JAXB Context. > {code:title=MyEJB.java} > @Stateless > @WebService > public class MyEJB { > public void launcheMyException() throws MyException { > return; > } > } > {code} > {code:title=MyException.java} > @XmlAccessorType(XmlAccessType.FIELD) > public class MyException extends Exception { > @XmlJavaTypeAdapter(Cl1ToCl2Adapter.class) > MyClass1 obj1; > @XmlJavaTypeAdapter(NoArgObjAdapter.class) > NoArgObj obj2; > public MyClass1 getObj1() { > return obj1; > } > > public void setObj1(MyClass1 obj1) { > this.obj1 = obj1; > } > public NoArgObj getObj2() { > return obj2; > } > public void setObj2(NoArgObj obj2) { > this.obj2 = obj2; > } > } > {code} > {code:title=Cl1ToCl2Adapter.java} > public class Cl1ToCl2Adapter extends XmlAdapter<MyClass2,MyClass1> { > @Override > public MyClass2 marshal(MyClass1 v) throws Exception { > return new MyClass2(); > } > @Override > public MyClass1 unmarshal(MyClass2 v) throws Exception { > MyClass1 mc1 = new MyClass1(v.getS2()); > return mc1; > } > } > {code} > This is what the resulting WSDL contains. Obj2 is mapped fine to a String, but MyClass1 is not and should have the MyClass2 mapping here. > {code:xml} > <xs:complexType name="MyException"> > <xs:sequence> > <xs:element name="str" nillable="true" type="xs:string"/> > <xs:element name="obj2" nillable="true" type="xs:string"/> > </xs:sequence> > </xs:complexType> > {code} > If you add the same adapter to a non Exception class it works just fine. > This is NOT a duplicate of JBWS-3552 as I believe in that use case only known JAXB types were tested (HashMap, Strings etc). This issue is when you are using custom classes that need to be mapped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3688) Upgrade to Apache CXF 2.7.7

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3688?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3688: ---------------------------------- Fix Version/s: jbossws-cxf-4.2.2 (was: jbossws-cxf-4.3) > Upgrade to Apache CXF 2.7.7 > --------------------------- > > Key: JBWS-3688 > URL: https://issues.jboss.org/browse/JBWS-3688 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3717) EndpointResolver implementations do not verify endpoint state before using endpoint

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3717: ----------------------------------------------- Alessio Soldano <asoldano(a)redhat.com> made a comment on [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550] As per Petr analysis, the actual reason for the problem here should be https://issues.jboss.org/browse/JBWS-3719 JBWS-3717 could also cause the same effect, but is most likely not the first culprit here. > EndpointResolver implementations do not verify endpoint state before using endpoint > ----------------------------------------------------------------------------------- > > Key: JBWS-3717 > URL: https://issues.jboss.org/browse/JBWS-3717 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > Currently the implementors of EndpointResolver (namely, WebAppResolver and PortComponentResolver do not check the state of an endpoint before trying using it. This is a problem as with JBWS-3643 the EndpointRegistry is now based on the AS service registry, so it's possible for the resolvers to see endpoints that are not started yet. The issue would likely affect scenarios with frequent and concurrent deploy/undeploy sequences or requests reaching the AS during boot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3717) EndpointResolver implementations do not verify endpoint state before using endpoint

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWS-3717: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1017550 > EndpointResolver implementations do not verify endpoint state before using endpoint > ----------------------------------------------------------------------------------- > > Key: JBWS-3717 > URL: https://issues.jboss.org/browse/JBWS-3717 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > Currently the implementors of EndpointResolver (namely, WebAppResolver and PortComponentResolver do not check the state of an endpoint before trying using it. This is a problem as with JBWS-3643 the EndpointRegistry is now based on the AS service registry, so it's possible for the resolvers to see endpoints that are not started yet. The issue would likely affect scenarios with frequent and concurrent deploy/undeploy sequences or requests reaching the AS during boot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3714) Fix test support classes for use with non compressed-zero format IPv6 addresses

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3714?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3714 at 10/18/13 12:46 PM: ------------------------------------------------------------------ Reopening for the littleproxy patch by Petr was (Author: asoldano): Reopening for the littleproxy path by Petr > Fix test support classes for use with non compressed-zero format IPv6 addresses > ------------------------------------------------------------------------------- > > Key: JBWS-3714 > URL: https://issues.jboss.org/browse/JBWS-3714 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3714) Fix test support classes for use with non compressed-zero format IPv6 addresses

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3714?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3714: ----------------------------------- Reopening for the littleproxy path by Petr > Fix test support classes for use with non compressed-zero format IPv6 addresses > ------------------------------------------------------------------------------- > > Key: JBWS-3714 > URL: https://issues.jboss.org/browse/JBWS-3714 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3722) jbossws-cxf-client is using 2.1 version of jaxb-impl

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3722?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated JBWS-3722: ------------------------------------ Assignee: Alessio Soldano > jbossws-cxf-client is using 2.1 version of jaxb-impl > ---------------------------------------------------- > > Key: JBWS-3722 > URL: https://issues.jboss.org/browse/JBWS-3722 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.1 > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > > Invoking dependency:tree on POM looking like this: > {code} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <name>JBoss Web Services - Client test</name> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client-test</artifactId> > <version>1.0.0.Final</version> > <properties> > <jbossws-cxf-client-version>4.2.1.Final</jbossws-cxf-client-version> > </properties> > <dependencies> > <dependency> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client</artifactId> > <version>${jbossws-cxf-client-version}</version> > </dependency> > </dependencies> > </project> > {code} > jaxb-impl dependency should be 2.2.x > {code} > ... > +- org.apache.cxf:cxf-rt-transports-jms:jar:2.7.6:compile > | +- org.apache.cxf:cxf-rt-management:jar:2.7.6:compile > | +- com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile > | \- com.sun.xml.bind:jaxb-xjc:jar:2.1.13:compile > ... > {code} > Info from IRC: > <asoldano> rsvoboda, I think the situation here is complicated by multiple dependency management block existing (both in cxf parent and jbossws-cxf parent) and missing explicit dependency to jaxb-impl in jbossws-cxf-client pom. I need to check the actual order of dependencyManagement processing in Maven impl, perhaps it's processed in a different order then we expect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3722) jbossws-cxf-client is using 2.1 version of jaxb-impl

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3722?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3722: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > jbossws-cxf-client is using 2.1 version of jaxb-impl > ---------------------------------------------------- > > Key: JBWS-3722 > URL: https://issues.jboss.org/browse/JBWS-3722 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.1 > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Invoking dependency:tree on POM looking like this: > {code} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <name>JBoss Web Services - Client test</name> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client-test</artifactId> > <version>1.0.0.Final</version> > <properties> > <jbossws-cxf-client-version>4.2.1.Final</jbossws-cxf-client-version> > </properties> > <dependencies> > <dependency> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client</artifactId> > <version>${jbossws-cxf-client-version}</version> > </dependency> > </dependencies> > </project> > {code} > jaxb-impl dependency should be 2.2.x > {code} > ... > +- org.apache.cxf:cxf-rt-transports-jms:jar:2.7.6:compile > | +- org.apache.cxf:cxf-rt-management:jar:2.7.6:compile > | +- com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile > | \- com.sun.xml.bind:jaxb-xjc:jar:2.1.13:compile > ... > {code} > Info from IRC: > <asoldano> rsvoboda, I think the situation here is complicated by multiple dependency management block existing (both in cxf parent and jbossws-cxf parent) and missing explicit dependency to jaxb-impl in jbossws-cxf-client pom. I need to check the actual order of dependencyManagement processing in Maven impl, perhaps it's processed in a different order then we expect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3722) jbossws-cxf-client is using 2.1 version of jaxb-impl

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBWS-3722: --------------------------------------- Summary: jbossws-cxf-client is using 2.1 version of jaxb-impl Key: JBWS-3722 URL: https://issues.jboss.org/browse/JBWS-3722 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.2.1 Reporter: Rostislav Svoboda Invoking dependency:tree on POM looking like this: {code} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <name>JBoss Web Services - Client test</name> <groupId>org.jboss.ws.cxf</groupId> <artifactId>jbossws-cxf-client-test</artifactId> <version>1.0.0.Final</version> <properties> <jbossws-cxf-client-version>4.2.1.Final</jbossws-cxf-client-version> </properties> <dependencies> <dependency> <groupId>org.jboss.ws.cxf</groupId> <artifactId>jbossws-cxf-client</artifactId> <version>${jbossws-cxf-client-version}</version> </dependency> </dependencies> </project> {code} jaxb-impl dependency should be 2.2.x {code} ... +- org.apache.cxf:cxf-rt-transports-jms:jar:2.7.6:compile | +- org.apache.cxf:cxf-rt-management:jar:2.7.6:compile | +- com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile | \- com.sun.xml.bind:jaxb-xjc:jar:2.1.13:compile ... {code} Info from IRC: <asoldano> rsvoboda, I think the situation here is complicated by multiple dependency management block existing (both in cxf parent and jbossws-cxf parent) and missing explicit dependency to jaxb-impl in jbossws-cxf-client pom. I need to check the actual order of dependencyManagement processing in Maven impl, perhaps it's processed in a different order then we expect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2013