March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1188) Relax requirement for wsu:id for UsernameToken

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1188?page=all ] Darran Lofthouse updated JBWS-1188: ----------------------------------- Fix Version/s: jbossws-native-2.0.5 (was: jbossws-native-2.0.4) Assignee: (was: Darran Lofthouse) > Relax requirement for wsu:id for UsernameToken > ---------------------------------------------- > > Key: JBWS-1188 > URL: http://jira.jboss.com/jira/browse/JBWS-1188 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Fix For: jbossws-native-2.0.5 > > > The JBossWS UsernameToken implementation is mandating that the wsu:id attribute is present on incomming requests. > Some thirdparty web services stacks being used as clients to JBossWS do not send the ID so we are rejecting the request. Additionally we do not actually use the id anywhere anyway. > The requirement for the id should be relaxed. -- 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-844) Add support for a fully defined schema with a message endpoint

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-844?page=all ] Darran Lofthouse updated JBWS-844: ---------------------------------- Fix Version/s: jbossws-native-2.0.5 (was: jbossws-native-2.0.4) Assignee: (was: Darran Lofthouse) > Add support for a fully defined schema with a message endpoint > -------------------------------------------------------------- > > Key: JBWS-844 > URL: http://jira.jboss.com/jira/browse/JBWS-844 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Jason T. Greene > Fix For: jbossws-native-2.0.5 > > > Currently a SOAPElement can only be mapped to a xsd:any type. We should add support for mapping SOAPElement to a message that has been fully specified. This would allow for the WSDL to represent a fully defined contract, and yet still allow the endpoint to have flexible parsing. > -Jason -- 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] Commented: (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=comments#action_12401917 ] Magesh Kumar B commented on JBWS-1217: -------------------------------------- Modified to generate base types and variable mappings that were missed earlier. > 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: 4 days, 3 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: ---------------------------------- > 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: 3 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] Created: (JBWS-1888) Simple Ant build file for user WS-enabled projects

by Alessio Soldano (JIRA)

Simple Ant build file for user WS-enabled projects -------------------------------------------------- Key: JBWS-1888 URL: http://jira.jboss.com/jira/browse/JBWS-1888 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-2025) Review Since tags

by Alessio Soldano (JIRA)

Review Since tags ----------------- Key: JBWS-2025 URL: http://jira.jboss.com/jira/browse/JBWS-2025 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-3.0.1 The "Since" tag contents in the wiki need to be reviewed according to the new naming convention. We should use something like "Since 3.0.1" or "Since Native 2.0.4" depending on the kind of feature (cross-stack or native only) -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-2022) Provide interface for WSSecurityDispatcher

by Alessio Soldano (JIRA)

Provide interface for WSSecurityDispatcher ------------------------------------------ Key: JBWS-2022 URL: http://jira.jboss.com/jira/browse/JBWS-2022 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.4 We should have a API for calling the security stuff not only from the wsse handlers and specifying the wsse conf that has to be used. This is required for the RM implementation. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2019) WSDL To Java - Case of service-interface and service-endpoint-interface in JAX-RPC mapping does not match generated interface when WSDL type begins with lower case.

by Darran Lofthouse (JIRA)

WSDL To Java - Case of service-interface and service-endpoint-interface in JAX-RPC mapping does not match generated interface when WSDL type begins with lower case. --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2019 URL: http://jira.jboss.com/jira/browse/JBWS-2019 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-native-2.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse 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, 10 months

1
1
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