September 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3707) AbstractCommonConfig is not thread safe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3707?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3707: ---------------------------------- Description: The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe and is possibly accessed / modified concurrently (at least during boot on WFLY as a consequence of WFLY-1759). The members should likely be final (and the collection ones should be initialized to concurrent collections). Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. was: The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe. The members should likely be final (and the collection ones should be initialized to concurrent collections). Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. > AbstractCommonConfig is not thread safe > --------------------------------------- > > Key: JBWS-3707 > URL: https://issues.jboss.org/browse/JBWS-3707 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe and is possibly accessed / modified concurrently (at least during boot on WFLY as a consequence of WFLY-1759). The members should likely be final (and the collection ones should be initialized to concurrent collections). > Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3708) Enforce client/endpoint config immutability

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3708: ------------------------------------- Summary: Enforce client/endpoint config immutability Key: JBWS-3708 URL: https://issues.jboss.org/browse/JBWS-3708 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 The client and endpoint predefined configs should be considered immutable after the server has booted. Unless we decide to explicitly support on-the-fly user modification of configs (e.g. for adding handlers, changing props, etc.) we need to return immutable versions / deep copy of them from the ServerConfig (AbstractServerConfig). -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3707) AbstractCommonConfig is not thread safe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3707?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3707: ---------------------------------- Description: The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe. The members should likely be final (and the collection ones should be initialized to concurrent collections). Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. was:The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe. The members should likely be final (and the collection ones should be initialized to concurrent collections). > AbstractCommonConfig is not thread safe > --------------------------------------- > > Key: JBWS-3707 > URL: https://issues.jboss.org/browse/JBWS-3707 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe. The members should likely be final (and the collection ones should be initialized to concurrent collections). > Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3707) AbstractCommonConfig is not thread safe

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3707: ------------------------------------- Summary: AbstractCommonConfig is not thread safe Key: JBWS-3707 URL: https://issues.jboss.org/browse/JBWS-3707 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe. The members should likely be final (and the collection ones should be initialized to concurrent collections). -- 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

10 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3690: ----------------------------------------------- Alessio Soldano <asoldano(a)redhat.com> made a comment on [bug 999893|https://bugzilla.redhat.com/show_bug.cgi?id=999893] Rostislav, JBossWS 4.2.1.Final was released without Apache CXF upgrade to 2.7.7. > 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.3 > > 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

10 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3690: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 999893|https://bugzilla.redhat.com/show_bug.cgi?id=999893] Should be fixed in CXF 2.7.7 / JBossWS CXF 4.2.1 > 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.3 > > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from ON_QA to VERIFIED > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] Verified on EAP 620 ER2, issue simulated on EAP 610 GA and verified on EAP 620 ER2 with custom war archive. Latest Modeshape 3.5.0 is not possible to deploy on EAP 6.2.0. > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from MODIFIED to ON_QA > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3706) JBossWS 4.2.1.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3706?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3706 at 9/17/13 8:51 AM: ---------------------------------------------------------------- JBoss AS 7.1.2.Final and JBoss AS 7.1.3.Final * [CXF-1519] Explicitly set the namespace of a WebFault * [CXF-2006] RespectBinding feature and not understood required extensibility elements * [JBWS-2561] XOP request not properly inlined * [JBWS-2480] Soap attachments are dropped on server response * [JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater * [JBWS-3441] Support CDI interceptors for POJO JAX-WS services * [AS7-537] Fixed on AS 8 or greater * [JBWS-3560] fastinfoset module is required in as712 * [JBWS-3679] @WebServiceRef injection of co-located client with no specified wsdlLocation is not working * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader * FIXME: [JBWS-3680] SOAP 1.2 fault reason xml:lang attribute not properly parsed on client side * [JBWS-3079] FIXME: Add support for https protocol was (Author: asoldano): JBoss AS 7.1.2.Final * [CXF-1519] Explicitly set the namespace of a WebFault * [CXF-2006] RespectBinding feature and not understood required extensibility elements * [JBWS-2561] XOP request not properly inlined * [JBWS-2480] Soap attachments are dropped on server response * [JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater * [JBWS-3441] Support CDI interceptors for POJO JAX-WS services * [AS7-537] Fixed on AS 8 or greater * [JBWS-3560] fastinfoset module is required in as712 * [JBWS-3679] @WebServiceRef injection of co-located client with no specified wsdlLocation is not working * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader * FIXME: [JBWS-3680] SOAP 1.2 fault reason xml:lang attribute not properly parsed on client side * [JBWS-3079] FIXME: Add support for https protocol > JBossWS 4.2.1.Final errata > --------------------------- > > Key: JBWS-3706 > URL: https://issues.jboss.org/browse/JBWS-3706 > 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.1 > > -- 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

10 years, 8 months

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 September 2013