March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2061) JSON wsdl generation

by Thomas Diesler (JIRA)

JSON wsdl generation -------------------- Key: JBWS-2061 URL: http://jira.jboss.com/jira/browse/JBWS-2061 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2065) JSON wsdl generation

by Thomas Diesler (JIRA)

JSON wsdl generation -------------------- Key: JBWS-2065 URL: http://jira.jboss.com/jira/browse/JBWS-2065 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2053) Client side transport abstraction

by Heiko Braun (JIRA)

Client side transport abstraction --------------------------------- Key: JBWS-2053 URL: http://jira.jboss.com/jira/browse/JBWS-2053 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2008) EJB3 WS API

by Heiko Braun (JIRA)

EJB3 WS API ----------- Key: JBWS-2008 URL: http://jira.jboss.com/jira/browse/JBWS-2008 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-3.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.1 Further decoupling from the EJB project. Actually there should only be a dependency on the ejb3-ws.jar (to be defined) and the EE5 API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2000) Chunked encoding transfer problem

by Heiko Braun (JIRA)

Chunked encoding transfer problem --------------------------------- Key: JBWS-2000 URL: http://jira.jboss.com/jira/browse/JBWS-2000 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-native-2.0.4 When transferring attachments with chunked encoding enabled you can see sporadic memory peaks and get 'Cannot close output stream' errors at the console log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
9
0 / 0

[JBoss JIRA] Created: (JBWS-1702) JAXWS type inheritance

by Thomas Diesler (JIRA)

JAXWS type inheritance ---------------------- Key: JBWS-1702 URL: http://jira.jboss.com/jira/browse/JBWS-1702 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-jbws Reporter: Thomas Diesler Fix For: jbossws-2.1.0 I have a problem with the new JBossWS-1.2.1.GA in JBoss 4.2.0.GA and inheritance. To describe this problem first I have to describe my code structure: For an example I have three classes (ClassA, ClassB and ClassC). ClassC inherits of ClassB and ClassB inherits of ClassA (ClassA --> ClassB --> ClassC). Now I have a webservice method that returns ClassB. In this method an instance of ClassC is being created and returned. This was not a problem in the former JBossWS version (and also in the other J2EE 4 styled webservices) but now in JBossWS 1.2 I only get returned an object of ClassB but I supposed to get an obejct of ClassC. Code: public class ClassA { private String propA; // here setter and getter for propA ...... } public class ClassB extends ClassA { private String propB; // here setter and getter for propB ...... } public class ClassC extends ClassC { private String propC; // here setter and getter for propC ...... } @WebService @SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SO APBinding.ParameterStyle.WRAPPED ) public class MyWebService { @WebMethod() public ClassB getClassB() { ClassC classC = new ClassC(); classC.setPropA("propA"); return classC; } /** * --> this method is only used to publish ClassC otherwise it is not known * in this webservice */ @WebMethod() public ClassC getClassC() { ClassC classC = new ClassC(); classC.setPropA("propA"); return classC; } } } Now I call getClassB() and the result that I got is an object of ClassB and not of ClassC. What can I do to get an object of ClassC. I also looked at the returned SOAP message and there you can see that only informations about the ClassB instance are submitted. In JBoss 4.0.5 (JBossWS1.0.3) the SOAP message contains the type of the returned object and all data are being submitted correctly. I also tried the SOAP parameter style BARE but nothing changed. And whenI use RPC/Literal then I get an error in the .NET Client that an instance of ClassB was expected but got an instance of ClassC. I also tried it with a JAVA client but there was the same occurance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

5
9
0 / 0

[JBoss JIRA] Created: (JBWS-1930) Remove dependency on stax-api.jar

by Heiko Braun (JIRA)

Remove dependency on stax-api.jar --------------------------------- Key: JBWS-1930 URL: http://jira.jboss.com/jira/browse/JBWS-1930 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.2 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 JBossWS should rely on jboss-javaee.jar instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1462) JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request.

by Darran Lofthouse (JIRA)

JMSTransportSupport should set JMSCorrelationID on response message if it is was set on the incomming request. -------------------------------------------------------------------------------------------------------------- Key: JBWS-1462 URL: http://jira.jboss.com/jira/browse/JBWS-1462 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 If an incomming request has the JMSCorrelationID set it should be set on the outgoing response message as this is a mechanism that can be used to track which responses correspond to which requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1652) ServiceEndpoint requirements for JBossESB

by Tom Fennelly (JIRA)

ServiceEndpoint requirements for JBossESB ----------------------------------------- Key: JBWS-1652 URL: http://jira.jboss.com/jira/browse/JBWS-1652 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Fennelly JBossESB implements what it calls a "JBossWSAdapter" (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). This class allows the ESB to expose JBossWS endpoints through the ESB i.e. over all transport protocols supported by the ESB. In order to do this, JBossWSAdapter currently relies on a number of non-public JBossWS classes (tested against jbossws-1.0.3.SP1 only). After talking with Thomas (at JavaOne), we established that JBossWS will have a public API that will fit our requirements. This JIRA is just to track the ESB requirements in this area. So the ESB needs the following: 1. The ability to "lookup" a JBossWS ServiceEndpoint (or its equivalent in the new API). We currently use the ServiceEndpointManagerFactory to do this. 2. The ability to invoke the ServiceEndpoint to process a SOAP payload (ala the "ServiceEndpoint.handleRequest" method in jbossws-1.0.3.SP1). 3. The ability to register/deploy endpoint implementations. Thomas showed me how this can be done, but I forget the exact code now without having the code in front of me :-) 4. The ability to get the endpoint WSDL from the ServiceEndpoint instance (ala the ServiceEndpoint.handleWSDLRequest method in jbossws-1.0.3.SP1). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1498) Hudson build fails under Windows

by Alejandro Guizar (JIRA)

Hudson build fails under Windows -------------------------------- Key: JBWS-1498 URL: http://jira.jboss.com/jira/browse/JBWS-1498 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-1.2.0, jbossws-2.0.0 Environment: Windows XP Pro Reporter: Alejandro Guizar In target hudson-setup: <exec executable="basename" outputproperty="svn.basename"> <arg value="${svn.url}"/> </exec> <exec executable="dirname" outputproperty="svn.basedir.local"> <arg value="${basedir}"/> </exec> Neither basename nor dirname are standard Windows commands. Targets hudson-start and hudson-stop invoke script catalina.sh to start/stop the web server. This is non portable as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2008