March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2055) Make JBossWS v2.0.1.SP2 available for download

by Tom Fennelly (JIRA)

Make JBossWS v2.0.1.SP2 available for download ---------------------------------------------- Key: JBWS-2055 URL: http://jira.jboss.com/jira/browse/JBWS-2055 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Fennelly JBossESB v4.2.1.CP1 has a dependency on JBossWS v2.0.1.SP2 (because it's in line with SOA-P, which depends on v2.0.1.SP2). When deploying the JBossESB v4.2.1.CP1 on JBoss AS v4.2.1.GA , the AS needs to be patched with JBossWS v2.0.1.SP2, but there's no download available for this on JBossWS downloads. The SOA-P guys were building it from source. Can we make a distro for this version available for download? -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2050) Update docs/install.txt with details of the appropriate ant targets

by Tom Fennelly (JIRA)

Update docs/install.txt with details of the appropriate ant targets ------------------------------------------------------------------- Key: JBWS-2050 URL: http://jira.jboss.com/jira/browse/JBWS-2050 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Tom Fennelly Fix For: jbossws-native-2.0.4 The ant targets seem to have changed, but are not up to date in this text file. -- 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

1
3
0 / 0

[JBoss JIRA] Reopened: (JBWS-925) Add support for FastInfoset

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-925?page=all ] Thomas Diesler reopened JBWS-925: --------------------------------- Write wiki documentation > Add support for FastInfoset > --------------------------- > > Key: JBWS-925 > URL: http://jira.jboss.com/jira/browse/JBWS-925 > 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 > > > A standard way of doing binary WS is FastInfoset > http://java.sun.com/developer/technicalArticles/xml/fastinfoset/ > The Fast Infoset standard draft (currently being developed as joint work by ISO/IEC JTC 1 and ITU-T) specifies a binary format for XML infosets that is an efficient alternative to XML. An instance of this binary format is called a fast infoset document. Fast infoset documents are analogous to XML documents. Each has a physical form and an XML infoset. Fast infoset documents are, given the results presented, faster to serialize and parse, and smaller in size, than the equivalent XML documents. Thus, fast infoset documents may be used whenever the size and processing time of XML documents is an issue. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1296) Add support for digest + nonces

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1296?page=all ] Alessio Soldano updated JBWS-1296: ---------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.x) > Add support for digest + nonces > ------------------------------- > > Key: JBWS-1296 > URL: http://jira.jboss.com/jira/browse/JBWS-1296 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Thomas Diesler > Assigned To: Alessio Soldano > Fix For: jbossws-native-2.0.4 > > > Add support for nonces, as well as a configurable encoding type for them. -- 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

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1172) Support schema validation for incoming/outgoing messages

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1172?page=all ] Thomas Diesler reopened JBWS-1172: ---------------------------------- Write the wiki documentation > Support schema validation for incoming/outgoing messages > -------------------------------------------------------- > > Key: JBWS-1172 > URL: http://jira.jboss.com/jira/browse/JBWS-1172 > 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 > > > I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA > I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts > I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?). > Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML. > I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ? > Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ? > How does one turn on XML Schema validation in JBOSSWS ? -- 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

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: 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages

by Magesh Kumar B (JIRA)

JavatoWSDL Package to Namespace mapping does not support multiple packages -------------------------------------------------------------------------- Key: JBWS-2018 URL: http://jira.jboss.com/jira/browse/JBWS-2018 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Reporter: Magesh Kumar B Assigned To: Magesh Kumar B Priority: Minor Fix For: jbossws-native-2.0.4 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, 1 month

1
5
0 / 0

[JBoss JIRA] Updated: (JBWS-981) Virtual host configuration for EJB endpoints

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-981?page=all ] Darran Lofthouse updated JBWS-981: ---------------------------------- Fix Version/s: jbossws-native-2.0.5 (was: jbossws-native-2.0.4) Assignee: (was: Darran Lofthouse) Dependent task still not complete. > Virtual host configuration for EJB endpoints > -------------------------------------------- > > Key: JBWS-981 > URL: http://jira.jboss.com/jira/browse/JBWS-981 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-native-2.0.5 > > > I use JBoss 4.0.4 GA and want to deploy a EJB3 (JSR-181) webserivce. Nearly everything is fine. The problem is that the generated servlet of the webservice is deployed on the default virtual host, but I want to change this to another. How is this possible? I tried to add an jboss-web.xml in META-INF directory of the jar-file containing the webservice bean and interface, but with no success. -- 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

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Richard Opalka (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=comments#action_12402169 ] Richard Opalka commented on JBWS-515: ------------------------------------- This issue is almost closed. Issue http://jira.jboss.org/jira/browse/JBWS-2048 supersedes it. > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Assigned To: Richard Opalka > Fix For: jbossws-native-2.0.4 > > > The relevant spec is > http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html > To complete this task we need > #1 An initial implementation of WS-RM Version 1.1 > #2 A comprehensive sample test case that shows the usage of WS-RM with JBossWS > #3 Documentation about WS-RM with JBossWS on the Wiki -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1541) WS-Security 1.1 support

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1541?page=all ] Darran Lofthouse updated JBWS-1541: ----------------------------------- Assignee: (was: Darran Lofthouse) > WS-Security 1.1 support > ----------------------- > > Key: JBWS-1541 > URL: http://jira.jboss.com/jira/browse/JBWS-1541 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit requirement. Notes: > In JBossWS 1.2, WS-Security 1.0 is implemented and Username Token Profile 1.0 is partly implemented. WS-Security 1.1 is not implemented at all. > Username Token Profile 1.0 describes how to use WS-Security 1.x to send a username and password over an unprotected link whilst maintaining confidentiality and preventing tampering and replay. Currently JBossWS 1.2 does not fully support Username Token Profile 1.0. This is due to lack of support for nonces. The "<wsse:UsernameToken>" can be signed and verified by using the current digital signature features of the JBossWS 1.2 implementation of WS-Security. > However, transmitting digested passwords is not a suitable solution for Intuit as it requires that passwords be stored in plain text. This violates Intuit's company wide security policy. > As far as I can tell, the main differences between WS-Security 1.0 and WS- Security 1.1 are to do with the signing of headers and with the addition of a new feature for preventing some man-in-the-middle attacks. The WS-Security 1.0 specification stated that you cannot encrypt the soap header, where as the WS-Security 1.1 specification states that you can. Despite this, JBossWS 1.2 allows you to encrypt the header. The WS-Security 1.1 specification prevents some man-in-the-middle attacks by mandating extra acknowledgements. > Backward compatibility, e.g. security handler should recognize and consume WSS 1.0 and 1.1 respectively. -- 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

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 March 2008