August 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1644) Process wsdl extensibility elements

by Alessio Soldano (JIRA)

Process wsdl extensibility elements ----------------------------------- Key: JBWS-1644 URL: http://jira.jboss.com/jira/browse/JBWS-1644 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-2.0.1 Wsdl extensibility elements/attributes have to be dealt in both marshalling and unmarshalling of wsdl to the unified wsdl structure. This is required to collect eventual policy attachment in wsdl or wsdl fragments. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1735) wstx.jar is missing from release, causes wsconsume to fail

by Reid Hartenbower (JIRA)

wstx.jar is missing from release, causes wsconsume to fail ---------------------------------------------------------- Key: JBWS-1735 URL: http://jira.jboss.com/jira/browse/JBWS-1735 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Reid Hartenbower Priority: Trivial result of invoking wsconsume.sh on a wsdl file: Failed to invoke WsImport javax.xml.stream.FactoryFinder$ConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found . . . -- 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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1645) Modify WSDLGenerator to deal with policies

by Alessio Soldano (JIRA)

Modify WSDLGenerator to deal with policies ------------------------------------------ Key: JBWS-1645 URL: http://jira.jboss.com/jira/browse/JBWS-1645 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-policy Reporter: Alessio Soldano Fix For: jbossws-2.0.1 Given the unified metadata model containing the supported policies, the WSDLGenerator has to be modified to deal with them and produce the corresponding extensibility elements in the unified wsdl structure. Endpoint policy subjects only will be supported for now. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests

by Darran Lofthouse (JIRA)

The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests ---------------------------------------------------------------------------------------- Key: JBWS-1704 URL: http://jira.jboss.com/jira/browse/JBWS-1704 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Fix For: jbossws-2.1.0 The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing requests, this parameter is not required by the server and can cause problems as some loadbalancers reject the message. The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to register the marshaller. See the createRemotingClient method: - http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core... It is possible to check the Remoting version using the following method: - public static int getDefaultVersion() >From 'org.jboss.remoting.Version', a possible solution will be to check the version to decide if we need to register the marshaller in this way. -- 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

17 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1792) init-param for handler defined in jaxrpc-config not processed

by Darran Lofthouse (JIRA)

init-param for handler defined in jaxrpc-config not processed ------------------------------------------------------------- Key: JBWS-1792 URL: http://jira.jboss.com/jira/browse/JBWS-1792 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.2 When handlers are defined in the JBossWS specific jaxrpc-config descriptor the init-param values specified are not processed so are not made available to the init method of the handler. -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1748) Improve the documentation that explains proprietary DD options

by Heiko Braun (JIRA)

Improve the documentation that explains proprietary DD options -------------------------------------------------------------- Key: JBWS-1748 URL: http://jira.jboss.com/jira/browse/JBWS-1748 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun jboss.xml overrides and configuration options are not very well documented. See the attached forum ref for an example question. -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1795) Type Substitution doesn't work with Schema2Java Client approach

by Markus Schumpa (JIRA)

Type Substitution doesn't work with Schema2Java Client approach --------------------------------------------------------------- Key: JBWS-1795 URL: http://jira.jboss.com/jira/browse/JBWS-1795 Project: JBoss Web Services Issue Type: CTS Challenge Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws, tools-jaxrpc, tools-jaxws Affects Versions: jbossws-2.0.1, jbossws-2.0.0 Environment: WindowsXP, JDK5U11, JBoss4.2.1 Reporter: Markus Schumpa I have written a web service with a parameter and a return value. the method is like: ListLocation calculate (ListLocation){...} The parameter is something like: class ListLocation { private List<LocationImpl> list; } class LocationImpl{...} class Cabin extends LocationImpl{...} class TechCabin extends LocationImpl{...} so I added the @XmlSeeAlso ({Cabin.class, TechCabin.class}) annotation to the LocationImpl class. I can now deploy the web service and the wsdl gets generated in a proper way. The first thing I did to test the service was writting a simple client which creates a Cabin and a TechCabin instance and adds these two instances to the ListLoaction list and passes it to the web service. For this I used the classes I coded. With this setup everything worked fine and the service was able to cast the list members to the proper type. So the type substitution worked well. But I need the test the Schema2Java approach, too. So I consumed the WSDL with wsconsume and the -t 2.1 switch. (wsconsume -k -p com.titan.domain.generated -w http://127.0.0.1:8080/OR19.1TC/TravelAgentBean?wsdl -s d:\TC\source1\ -o d:\TC\output1\ -t 2.1 http://127.0.0.1:8080/OR19.1TC/TravelAgentBean?wsdl) I addopted the client to use the generated classes. But here the type substitution doesn't work. The list only contains LocationImpl instances. -- 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

17 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-1796) deploy-jboss40-no-ejb3 build fails

by Magesh Kumar B (JIRA)

deploy-jboss40-no-ejb3 build fails ---------------------------------- Key: JBWS-1796 URL: http://jira.jboss.com/jira/browse/JBWS-1796 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-2.0.1 Environment: JBoss4.0.5 non ejb3 and jbossws-native2.0.1 Reporter: Magesh Kumar B Assigned To: Thomas Diesler Fix For: jbossws-2.0.2 When we do ant deploy-jboss40-no-ejb3 build fails with the following error: Warning: Could not find file ..\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml to copy. Looks like the jbossws-native40.sar bundled with the download is not updated. However the direct link here is updated http://repository.jboss.org/jboss/jbossws-native40/2.0.1.GA/lib/ -- 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

17 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-1330) Fix jaxrpc wsse tests for jbossws-5.0

by Thomas Diesler (JIRA)

Fix jaxrpc wsse tests for jbossws-5.0 ------------------------------------- Key: JBWS-1330 URL: http://jira.jboss.com/jira/browse/JBWS-1330 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0.CR2 [tdiesler@tdvaio test]$ ant -Dtest=jaxrpc/wsse test tests-main: [junit] Running org.jboss.test.ws.jaxrpc.wsse.MicrosoftInteropTestCase [junit] FIXME: [JBWS-1130] Consolidate namespace declarations [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.863 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.536 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.RoundTripTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.289 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.RpcTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.722 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.RpcTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 7.19 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 5.947 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 6.581 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.452 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.SunInteropTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.382 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 0.431 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.wsse.WebClientTestCase [junit] [JBAS-3824] Fix ENC for EJB2.1 and Servlets [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.524 sec [junit] Running org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 4.64 sec [junit] Test org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase FAILED -- 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

17 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1794) init-param for handler defined in jaxrpc-config not processed

by Darran Lofthouse (JIRA)

init-param for handler defined in jaxrpc-config not processed ------------------------------------------------------------- Key: JBWS-1794 URL: http://jira.jboss.com/jira/browse/JBWS-1794 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.2 When handlers are defined in the JBossWS specific jaxrpc-config descriptor the init-param values specified are not processed so are not made available to the init method of the handler. -- 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

17 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2007