October 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2196) FastInfoset interoperability

by Thomas Diesler (JIRA)

FastInfoset interoperability ---------------------------- Key: JBWS-2196 URL: http://jira.jboss.com/jira/browse/JBWS-2196 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Thomas Diesler Alexander Philippou sais MSFT doesn't offer a Fast Infoset implementation. For WCF, Fast Infoset is provided by Noemax's WCF-Xtensions. I assume that general JBossWS<->WCF interop is given so we just need to focus on trying Fast Infoset as message encoding. This will also test content negotiation, which again is provided only by WCF-Xtensions. We have raised a test service, its wsdl is at http://www.noemax.com:8080/BenchmarkService?wsdl. It will be great if you can run a client to test it. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-1862) RPC DII Calls Assume child element of soap:body is called 'result' in the response message.

by Darran Lofthouse (JIRA)

RPC DII Calls Assume child element of soap:body is called 'result' in the response message. ------------------------------------------------------------------------------------------- Key: JBWS-1862 URL: http://jira.jboss.com/jira/browse/JBWS-1862 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.3 RPC DII Calls Assume child element of soap:body is called 'result' in the response message. For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported. java.rmi.RemoteException: Call invocation failed; nested exception is: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526) at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276) ... Caused by: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356) at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507) ... 2 more -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-2323) Allow the Xerces defer-node-expansion optimisation to be diabled.

by Darran Lofthouse (JIRA)

Allow the Xerces defer-node-expansion optimisation to be diabled. ----------------------------------------------------------------- Key: JBWS-2323 URL: https://jira.jboss.org/jira/browse/JBWS-2323 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.4 Add a system property to allow the Xerces defer-node-expansion feature to be disabled. The feature is documented here: - http://xerces.apache.org/xerces2-j/features.html A down side if this feature is the additional memory overhead that this feature requires. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2328) Provide wsrunclient shell scripts for metro integration

by Richard Opalka (JIRA)

Provide wsrunclient shell scripts for metro integration ------------------------------------------------------- Key: JBWS-2328 URL: https://jira.jboss.org/jira/browse/JBWS-2328 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Richard Opalka Fix For: jbossws-metro-3.0.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2296) Run TCK5 saaj test suite and detect issues

by Richard Opalka (JIRA)

Run TCK5 saaj test suite and detect issues ------------------------------------------ Key: JBWS-2296 URL: https://jira.jboss.org/jira/browse/JBWS-2296 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2165) Fix xop tests with maven build

by Thomas Diesler (JIRA)

Fix xop tests with maven build ------------------------------ Key: JBWS-2165 URL: http://jira.jboss.com/jira/browse/JBWS-2165 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Thomas Diesler Fix For: jbossws-metro-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
10
0 / 0

[JBoss JIRA] Created: (JBWS-2334) Use Woodstox on client side when running tests

by Alessio Soldano (JIRA)

Use Woodstox on client side when running tests ---------------------------------------------- Key: JBWS-2334 URL: https://jira.jboss.org/jira/browse/JBWS-2334 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Assignee: Alessio Soldano Since AS5 uses woodstox as default StAX implementation, we should evaluate actually using it as StAX implementation on client side when running tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2376) Fix deployment macros

by Richard Opalka (JIRA)

Fix deployment macros --------------------- Key: JBWS-2376 URL: https://jira.jboss.org/jira/browse/JBWS-2376 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 Currently we use the following form of include in patternsets: <patternset id="jbossws.client.patternset"> <include name="**/FastInfoset.jar"/> ... </patternset> This approach is error prone. We should include more specific artifacts, e.g.: <patternset id="jbossws.client.patternset"> <include name="**/maven/group/id//FastInfoset.jar"/> ... </patternset> This applies mainly to JBossAS thirdparty directory (where stack specific macro is reused). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2344) Provide different exclude files for JDK5/JDK6 hudson jobs

by Alessio Soldano (JIRA)

Provide different exclude files for JDK5/JDK6 hudson jobs --------------------------------------------------------- Key: JBWS-2344 URL: https://jira.jboss.org/jira/browse/JBWS-2344 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
7
0 / 0

[JBoss JIRA] Created: (JBWS-2343) Enable tests requiring atp/wsgen on client side

by Alessio Soldano (JIRA)

Enable tests requiring atp/wsgen on client side ----------------------------------------------- Key: JBWS-2343 URL: https://jira.jboss.org/jira/browse/JBWS-2343 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Assignee: Alessio Soldano The testsuite has excluded tests because of the missing wrapper generator. Once this is available, we can deploy the same testsuite jars on Native and Metro, without requiring users to run an external tool when developing endpoints with bottom-up (java first) strategy. However Metro still need to generate wrapper beans on client side to invoke the service. In a real world scenario, where client and server do not share classes, users would run wsimport and obtain the required classes from the service contract. Thus no wrapper generation required on client side. We should anyway be able to run our full testsuite with Metro stack, so we need to somehow enhance our test framework to automatically call wsgen when requiring a give artifact to be deployed before running some tests. This would provide the missing piece on client side for running those tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

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