August 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3698) Fix regressions in SOAP-over-JMS testcases on WildFly 8.0.0.Alpha3

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3698: ------------------------------------- Summary: Fix regressions in SOAP-over-JMS testcases on WildFly 8.0.0.Alpha3 Key: JBWS-3698 URL: https://issues.jboss.org/browse/JBWS-3698 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2.1 Starting from WildFly 8.0.0.Alpha3 we have some regressions in SOAP-over-JMS testcases. We need to update the JNDI url to be used for resolving the remote connection factory, given WFLY now uses HTTP Upgrade. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3697) WSConsume fails on OpenJDK 6

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3697: ------------------------------------- Summary: WSConsume fails on OpenJDK 6 Key: JBWS-3697 URL: https://issues.jboss.org/browse/JBWS-3697 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, productization, tools-jaxws Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2.1 WSConsume seems to be failing with the OpenJDK 1.6.0.0.x86_64 that's installed on (some?) RHEL distributions. The reason is in a different (compare to Oracle and IBM JDK) implementation choice of the javax.tool.FileObject#getName() method: OpenJDK returns objName strings like "/usr/java/java-1.6.0-openjdk-1.6.0.0.x86_64/lib/ct.sym(META-INF/sym/rt.jar/java/lang/AbstractMethodError.class)" while Oracle & IBM JDK return objName strings like: "AbstractMethodError.class" This is currently basically disabling the mechanism we implemented in JBWS-3589, so WSConsume become again dependent on the current (endorsed) java versions. So while by default JAXWS 2.2 sources are produced, the a JDK 6 compiler won't be able to compile them. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3696) Make AppclientHelper timeout configurable

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3696: ------------------------------------- Summary: Make AppclientHelper timeout configurable Key: JBWS-3696 URL: https://issues.jboss.org/browse/JBWS-3696 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3695) Fix transient failures in ContinuationsTestCase

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3695: ------------------------------------- Summary: Fix transient failures in ContinuationsTestCase Key: JBWS-3695 URL: https://issues.jboss.org/browse/JBWS-3695 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, productization 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3694) CopyJob fix & improvement

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3694?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3694: ---------------------------------- Summary: CopyJob fix & improvement (was: CopyJob improvements) > CopyJob fix & improvement > ------------------------- > > Key: JBWS-3694 > URL: https://issues.jboss.org/browse/JBWS-3694 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.1 > > > The CopyJob used in the testsuite has a possible concurrency / visibility issue and should allow automatically closing the passed in output stream. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3694) CopyJob improvements

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3694: ------------------------------------- Summary: CopyJob improvements Key: JBWS-3694 URL: https://issues.jboss.org/browse/JBWS-3694 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2.1 The CopyJob used in the testsuite has a possible concurrency / visibility issue and should allow automatically closing the passed in output stream. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3693) libaprutil-1.so.0.3.9 needed for Apache EWS 2.0.1 installation

by Ken Simms (JIRA)

[ https://issues.jboss.org/browse/JBWS-3693?page=com.atlassian.jira.plugin.... ] Ken Simms commented on JBWS-3693: --------------------------------- I have found out since posting this that libaprutil-1.so.0.3.9 is only available over the x64 channel for RHEL 6. We are trying to install Apache EWS 2.0.1 on a RHEL 5 server. Even RHEL 5 install is looking for RHEL 6 binaries. Redhat case is open and they are investigating. > libaprutil-1.so.0.3.9 needed for Apache EWS 2.0.1 installation > -------------------------------------------------------------- > > Key: JBWS-3693 > URL: https://issues.jboss.org/browse/JBWS-3693 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ken Simms > Labels: 2.0.1, apache, ews, jboss > > Trying to install RH EWS 2.0.1 Apache. Per install guide, did yum installs/updates for krb5-workstation, mod_auth_kerb, elinks, apr-devel and/or apr-utildevel. After installing all pre-reqs, the file libaprutil-1.so.0.3.9 (and related) are not loaded in /usr/lib64. So when the zip file is extracted, no symlinks are created. > What package contains file libaprutil-1.so.0.3.9 so I can update my system and get Apache working? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3679) @WebServiceRef injection of co-located client with no specified wsdlLocation is not working

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3679?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3679: ---------------------------------- Assignee: Jim Ma > @WebServiceRef injection of co-located client with no specified wsdlLocation is not working > ------------------------------------------------------------------------------------------- > > Key: JBWS-3679 > URL: https://issues.jboss.org/browse/JBWS-3679 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2.1 > > > JSR-109 section 4.2.2: > "For co-located clients (where the client and the server are in the same Java EE application unit) with generated Service class, the location of the final WSDL document is resolved by comparing the Service name on the @WebServiceClient annotation on the the generated Service to the Service names of all the deployed port components in the Java EE application unit." > This does not seem to work currently. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3693) libaprutil-1.so.0.3.9 needed for Apache EWS 2.0.1 installation

by Ken Simms (JIRA)

Ken Simms created JBWS-3693: ------------------------------- Summary: libaprutil-1.so.0.3.9 needed for Apache EWS 2.0.1 installation Key: JBWS-3693 URL: https://issues.jboss.org/browse/JBWS-3693 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ken Simms Trying to install RH EWS 2.0.1 Apache. Per install guide, did yum installs/updates for krb5-workstation, mod_auth_kerb, elinks, apr-devel and/or apr-utildevel. After installing all pre-reqs, the file libaprutil-1.so.0.3.9 (and related) are not loaded in /usr/lib64. So when the zip file is extracted, no symlinks are created. What package contains file libaprutil-1.so.0.3.9 so I can update my system and get Apache working? -- 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, 11 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: ----------------------------------------------- Mustafa Musaji <mmusaji(a)redhat.com> made a comment on [bug 999893|https://bugzilla.redhat.com/show_bug.cgi?id=999893] Platform BZ for https://issues.jboss.org/browse/JBWS-3690 Given the interface: @javax.jws.WebService public interface WsIntfc { public void test() throws MyException; } And exception class: public class MyException extends Exception { private MyClass1 adapted = null; @XmlJavaTypeAdapter(Cl1ToCl2Adapter.class) public MyClass1 getAdapted() { return this.adapted; } public void setAdapted(MyClass1 adapted) { this.adapted = adapted; } } Along with: public class Cl1ToCl2Adapter extends XmlAdapter<MyClass2, MyClass1> { @Override public MyClass1 unmarshal(MyClass2 v) throws Exception { MyClass1 mc1 = new MyClass1(); mc1.setName(v.getFile()); return mc1; } @Override public MyClass2 marshal(MyClass1 v) throws Exception { MyClass2 mc2 = new MyClass2(); mc2.setFile(v.getName()); return mc2; } } public class MyClass1 { private String name = null; public String getName() { return this.name; } public void setName(String name) { this.name = name; } } public class MyClass2 { private String file = null; public String getFile() { return this.file; } public void setFile(String file) { this.file = file; } } I get the following schema output: <xs:complexType name="myClass1"> <xs:sequence> <xs:element minOccurs="0" name="name" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:complexType name="MyException"> <xs:sequence/> </xs:complexType> I should expect myClass2 defined in the schema and referenced by MyException. > 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 > Attachments: 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, 11 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 August 2013