September 2013 - jbossws-issues - Jboss List Archives

[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 commented on JBWS-3706: --------------------------------------- JBoss AS 7.2.0.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 * [PLFED-390] PicketLink STS chokes on WS-Policy 1.5 tags * [AS7-537] Fixed on AS 8 or greater * [JBWS-3560] fastinfoset module is required in as720 * [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, 7 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:47 AM: ---------------------------------------------------------------- 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 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, 7 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 commented on JBWS-3706: --------------------------------------- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3642) Replace gnu-getopt:getopt with gnu.getopt:java-getopt

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3642?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3642: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1007527|https://bugzilla.redhat.com/show_bug.cgi?id=1007527] from POST to MODIFIED > Replace gnu-getopt:getopt with gnu.getopt:java-getopt > ----------------------------------------------------- > > Key: JBWS-3642 > URL: https://issues.jboss.org/browse/JBWS-3642 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We're including gnu getopt (for jaxws tooling) from the jboss thirdparty repository; we should replace that with the gnu.getopt:java-getopt from maven central. That would help for building jbossws using the maven central repo only. -- 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, 7 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3706: ------------------------------------- Summary: 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, 7 months

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.3 (was: jbossws-cxf-4.2.1) > 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.3 > > -- 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, 7 months

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.3 (was: 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, 7 months

1
0
0 / 0

[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.3 (was: jbossws-cxf-4.2.1) > 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.3 > > > 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] from VERIFIED to CLOSED > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3705) Fix JBWS1807TestCase

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3705: ------------------------------------- Summary: Fix JBWS1807TestCase Key: JBWS-3705 URL: https://issues.jboss.org/browse/JBWS-3705 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 The JBWS1807TestCase and the ProviderImpl that's tested by it currently send messages that do not comply with the endpoint wsdl contract. They should be fixed. This has been revealed by the upgrade to Apache CXF 2.7.7, which is possibly more strict in message validation on Provider based endpoints using XML/HTTP binding. -- 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, 7 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