November 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2368) JAX-WS Deployments Fail For AOP Instrumented Endpoints

by Darran Lofthouse (JIRA)

JAX-WS Deployments Fail For AOP Instrumented Endpoints ------------------------------------------------------ Key: JBWS-2368 URL: https://jira.jboss.org/jira/browse/JBWS-2368 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-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

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2407) HandlerChain is not set on client side when specified via WebServiceRefs

by Richard Opalka (JIRA)

HandlerChain is not set on client side when specified via WebServiceRefs ------------------------------------------------------------------------ Key: JBWS-2407 URL: https://jira.jboss.org/jira/browse/JBWS-2407 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-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

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2300) Run TCK5 jaxws test suite and detect issues

by Richard Opalka (JIRA)

Run TCK5 jaxws test suite and detect issues ------------------------------------------- Key: JBWS-2300 URL: https://jira.jboss.org/jira/browse/JBWS-2300 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
15
0 / 0

[JBoss JIRA] Created: (JBWS-2367) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) does not seem to work

by David Boeren (JIRA)

@BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) does not seem to work ------------------------------------------------------------------------------------ Key: JBWS-2367 URL: https://jira.jboss.org/jira/browse/JBWS-2367 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: David Boeren Fix For: jbossws-native-3.0.5 Attachments: jaxws_jboss_CI.zip The issue contains details about the environment. The WSDL generated for the SEI/Implementation with annotation @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) is not does not have SOAP12 Port. I tried using the annotation at SEI/implementation/both with the result being no different. -- 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
3
0 / 0

[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-2393) Update JAXWS-RI dependency to 2.1.5

by Alessio Soldano (JIRA)

Update JAXWS-RI dependency to 2.1.5 ----------------------------------- Key: JBWS-2393 URL: https://jira.jboss.org/jira/browse/JBWS-2393 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano JAXWS-Ri 2.1.5 is out, as a good number of bug fixes and is completely woodstox based (sjsxp not used anymore). We should be able to switch to 2.1.5, but this currently cause a streambuffer issue running the org.jboss.test.ws.jaxws.samples.wsse.SignTestCase and org.jboss.test.ws.jaxws.samples.wsse.SignEncryptTestCase. -- 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-2404) Efficient string handling

by Anthony Whitford (JIRA)

Efficient string handling ------------------------- Key: JBWS-2404 URL: https://jira.jboss.org/jira/browse/JBWS-2404 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Anthony Whitford Browsing the code, I came across some low hanging fruit around string usage. For example: native\modules\core\src\main\java\org\jboss\ws\metadata\wsdl\WSDLUtils.java 445 Use equals() to compare strings instead of '==' or '!=' native\modules\core\src\main\java\org\jboss\ws\metadata\wsdl\WSDLUtils.java 549 String.indexOf(char) is faster than String.indexOf(String). native\modules\core\src\main\java\org\jboss\ws\metadata\wsdl\WSDLUtils.java 648 Use equals() to compare strings instead of '==' or '!=' native\modules\core\src\main\java\org\jboss\ws\metadata\wsdl\WSDLUtils.java 664 String.indexOf(char) is faster than String.indexOf(String). Also noticed that there was the odd "bug", like: public String firstLetterUpperCase(String fname) { if (fname == "" || fname == null) throw new WSException("String passed is null"); ... The null check should be first, and comparing to an empty string literal isn't exactly the same thing as detecting an empty string. -- 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-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-2401) Drop port from URL for endpoint where default port for the protocol is being used.

by Darran Lofthouse (JIRA)

Drop port from URL for endpoint where default port for the protocol is being used. ---------------------------------------------------------------------------------- Key: JBWS-2401 URL: https://jira.jboss.org/jira/browse/JBWS-2401 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.5 Where the protocol is http and the port is 80 the :80 can be omitted from the URL. Where the protocol is https and the port is 443 :443 can be omitted from the URL. -- 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 November 2008