February 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1909) The native RequestHandler exposes implementation details

by Heiko Braun (JIRA)

The native RequestHandler exposes implementation details --------------------------------------------------------- Key: JBWS-1909 URL: http://jira.jboss.com/jira/browse/JBWS-1909 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Reporter: Heiko Braun The RequestHandler implementation that's being used with native carries an implementation error: It does cast the InvocationContext to a concrete implementation instead of relying on the interface. This forces clients like the ESB to work with that particular implementation, ServletRequestHandler in this case. Here's the code: public class RequestHandlerImpl implements RequestHandler { [...] public void handleWSDLRequest(Endpoint endpoint, OutputStream outputStream, InvocationContext context) { [...] ServletRequestContext reqContext = (ServletRequestContext)context; HttpServletRequest req = reqContext.getHttpServletRequest(); [...] -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1850) Documentation support for WSDL->Java and Java->WSDL

by jkario_78 (JIRA)

Documentation support for WSDL->Java and Java->WSDL --------------------------------------------------- Key: JBWS-1850 URL: http://jira.jboss.com/jira/browse/JBWS-1850 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: jkario_78 Priority: Minor Apparently there is no standard jax-ws way for doing this. However this could be accomplished using some JBoss specific annotation. Adding this annotation would generate the associated wsdl:documentation element into the generated WSDL document. See. http://jira.codehaus.org/browse/XFIRE-507 -- 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, 9 months

4
10
0 / 0

[JBoss JIRA] Commented: (JBWS-1165) Support JSON data binding

by Richard Opalka (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1165?page=comments#action_12400438 ] Richard Opalka commented on JBWS-1165: -------------------------------------- http://jettison.codehaus.org/ > Support JSON data binding > ------------------------- > > Key: JBWS-1165 > URL: http://jira.jboss.com/jira/browse/JBWS-1165 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-native-2.0.4 > > > Does anyone know how I could make a web service that had the option to return json instead of xml? Yahoo is doing just that. It would streamline a few client side things I have. > http://en.wikipedia.org/wiki/JSON -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1986) The deploy targets miss stax API installation

by Heiko Braun (JIRA)

The deploy targets miss stax API installation --------------------------------------------- Key: JBWS-1986 URL: http://jira.jboss.com/jira/browse/JBWS-1986 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-2.0.3 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-native-2.0.4 -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1727) Create test cases that verify scoped classloading (i.e. in web apps)

by Heiko Braun (JIRA)

Create test cases that verify scoped classloading (i.e. in web apps) -------------------------------------------------------------------- Key: JBWS-1727 URL: http://jira.jboss.com/jira/browse/JBWS-1727 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1990) Support SOAP 1.2 in wsconsume

by Alessio Soldano (JIRA)

Support SOAP 1.2 in wsconsume ----------------------------- Key: JBWS-1990 URL: http://jira.jboss.com/jira/browse/JBWS-1990 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Affects Versions: jbossws-native-2.0.3 Reporter: Alessio Soldano Currently our jaws tool wsconsume doesn't support soap-1.2 bindings. The JAXWS RI allows this using the -extension option. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Updated: (JBWS-1217) WSDLtoJava Namespace to package mapping does not support multiple namespaces

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1217?page=all ] Magesh Kumar B updated JBWS-1217: --------------------------------- Comment: was deleted > WSDLtoJava Namespace to package mapping does not support multiple namespaces > ---------------------------------------------------------------------------- > > Key: JBWS-1217 > URL: http://jira.jboss.com/jira/browse/JBWS-1217 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Affects Versions: jbossws-1.0.3 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Priority: Minor > Fix For: jbossws-native-2.0.4 > > Time Spent: 2 days, 7 hours > Remaining Estimate: 0 minutes > > Consider the following WSDL: > <?xml version="1.0" encoding="UTF-8"?> > <definitions name='MySEIService' targetNamespace='http://javatype.mycompany.com' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://javatype.mycompany.com' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <schema targetNamespace='http://other.com' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://other.com' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> > <complexType name='TestException'> > <sequence/> > </complexType> > <element name='TestException' type='tns:TestException'/> > </schema> > </types> > <message name='MySEI_testException'/> > <message name='MySEI_testExceptionResponse'/> > <message name='TestException'> > <part element='ns1:TestException' name='TestException'/> > </message> > <portType name='MySEI'> > <operation name='testException'> > <input message='tns:MySEI_testException'/> > <output message='tns:MySEI_testExceptionResponse'/> > <fault message='tns:TestException' name='TestException'/> > </operation> > </portType> > <binding name='MySEIBinding' type='tns:MySEI'> > <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> > <operation name='testException'> > <soap:operation soapAction=''/> > <input> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </input> > <output> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </output> > <fault name='TestException'> > <soap:fault name='TestException' use='literal'/> > </fault> > </operation> > </binding> > <service name='MySEIService'> > <port binding='tns:MySEIBinding' name='MySEIPort'> > <soap:address location='REPLACE_WITH_ACTUAL_URL'/> > </port> > </service> > </definitions> > Using the following wstools config: > <configuration xmlns="http://www.jboss.org/jbossws-tools"> > <global> > <package-namespace package="com.other" namespace="http://other.com"/> > <package-namespace package="com.mycompany.javatype" namespace="http://javatype.mycompany.com"/> > </global> > <wsdl-java file="MySEIService.wsdl"> > <mapping file="jaxrpc-mapping.xml" /> > </wsdl-java> > </configuration> > The TestException class is not generated in the com.other package. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1217) WSDLtoJava Namespace to package mapping does not support multiple namespaces

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1217?page=all ] Magesh Kumar B updated JBWS-1217: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-native-2.0.3) When derived types are generated, base types are also generated in the same package. > WSDLtoJava Namespace to package mapping does not support multiple namespaces > ---------------------------------------------------------------------------- > > Key: JBWS-1217 > URL: http://jira.jboss.com/jira/browse/JBWS-1217 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Affects Versions: jbossws-1.0.3 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Priority: Minor > Fix For: jbossws-native-2.0.4 > > Time Spent: 2 days, 7 hours > Remaining Estimate: 0 minutes > > Consider the following WSDL: > <?xml version="1.0" encoding="UTF-8"?> > <definitions name='MySEIService' targetNamespace='http://javatype.mycompany.com' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://javatype.mycompany.com' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <schema targetNamespace='http://other.com' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://other.com' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> > <complexType name='TestException'> > <sequence/> > </complexType> > <element name='TestException' type='tns:TestException'/> > </schema> > </types> > <message name='MySEI_testException'/> > <message name='MySEI_testExceptionResponse'/> > <message name='TestException'> > <part element='ns1:TestException' name='TestException'/> > </message> > <portType name='MySEI'> > <operation name='testException'> > <input message='tns:MySEI_testException'/> > <output message='tns:MySEI_testExceptionResponse'/> > <fault message='tns:TestException' name='TestException'/> > </operation> > </portType> > <binding name='MySEIBinding' type='tns:MySEI'> > <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> > <operation name='testException'> > <soap:operation soapAction=''/> > <input> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </input> > <output> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </output> > <fault name='TestException'> > <soap:fault name='TestException' use='literal'/> > </fault> > </operation> > </binding> > <service name='MySEIService'> > <port binding='tns:MySEIBinding' name='MySEIPort'> > <soap:address location='REPLACE_WITH_ACTUAL_URL'/> > </port> > </service> > </definitions> > Using the following wstools config: > <configuration xmlns="http://www.jboss.org/jbossws-tools"> > <global> > <package-namespace package="com.other" namespace="http://other.com"/> > <package-namespace package="com.mycompany.javatype" namespace="http://javatype.mycompany.com"/> > </global> > <wsdl-java file="MySEIService.wsdl"> > <mapping file="jaxrpc-mapping.xml" /> > </wsdl-java> > </configuration> > The TestException class is not generated in the com.other package. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1217) WSDLtoJava Namespace to package mapping does not support multiple namespaces

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1217?page=all ] Magesh Kumar B reopened JBWS-1217: ---------------------------------- Derived types are not generated with proper package. > WSDLtoJava Namespace to package mapping does not support multiple namespaces > ---------------------------------------------------------------------------- > > Key: JBWS-1217 > URL: http://jira.jboss.com/jira/browse/JBWS-1217 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Affects Versions: jbossws-1.0.3 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Priority: Minor > Fix For: jbossws-native-2.0.3 > > Time Spent: 2 days, 7 hours > Remaining Estimate: 0 minutes > > Consider the following WSDL: > <?xml version="1.0" encoding="UTF-8"?> > <definitions name='MySEIService' targetNamespace='http://javatype.mycompany.com' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://javatype.mycompany.com' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <schema targetNamespace='http://other.com' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://other.com' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> > <complexType name='TestException'> > <sequence/> > </complexType> > <element name='TestException' type='tns:TestException'/> > </schema> > </types> > <message name='MySEI_testException'/> > <message name='MySEI_testExceptionResponse'/> > <message name='TestException'> > <part element='ns1:TestException' name='TestException'/> > </message> > <portType name='MySEI'> > <operation name='testException'> > <input message='tns:MySEI_testException'/> > <output message='tns:MySEI_testExceptionResponse'/> > <fault message='tns:TestException' name='TestException'/> > </operation> > </portType> > <binding name='MySEIBinding' type='tns:MySEI'> > <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> > <operation name='testException'> > <soap:operation soapAction=''/> > <input> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </input> > <output> > <soap:body namespace='http://javatype.mycompany.com' use='literal'/> > </output> > <fault name='TestException'> > <soap:fault name='TestException' use='literal'/> > </fault> > </operation> > </binding> > <service name='MySEIService'> > <port binding='tns:MySEIBinding' name='MySEIPort'> > <soap:address location='REPLACE_WITH_ACTUAL_URL'/> > </port> > </service> > </definitions> > Using the following wstools config: > <configuration xmlns="http://www.jboss.org/jbossws-tools"> > <global> > <package-namespace package="com.other" namespace="http://other.com"/> > <package-namespace package="com.mycompany.javatype" namespace="http://javatype.mycompany.com"/> > </global> > <wsdl-java file="MySEIService.wsdl"> > <mapping file="jaxrpc-mapping.xml" /> > </wsdl-java> > </configuration> > The TestException class is not generated in the com.other package. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1161) Interop endpoints for MTOM

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1161?page=all ] Heiko Braun updated JBWS-1161: ------------------------------ Fix Version/s: jbossws-native-2.0.5 (was: jbossws-native-2.0.4) > Interop endpoints for MTOM > -------------------------- > > Key: JBWS-1161 > URL: http://jira.jboss.com/jira/browse/JBWS-1161 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-native-2.0.5 > > > http://131.107.72.15/ilab/Messaging/WCFInteropPlugFest_Messaging.doc -- 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, 9 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 February 2008