July 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2891) JAX-WS Detect and report duplicate wrapper classes

by Darran Lofthouse (JIRA)

JAX-WS Detect and report duplicate wrapper classes -------------------------------------------------- Key: JBWS-2891 URL: https://jira.jboss.org/jira/browse/JBWS-2891 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 >From the JAX-WS specification section 3.6.2.1 regarding Document Wrapped: - Conformance (Default wrapper bean names): In the absence of customizations, the wrapper request bean class MUST be named the same as the method and the wrapper response bean class MUST be named the same as the method with a "Response" suffix. The first letter of each bean name is capitalized to follow Java class naming conventions. Conformance (Wrapper bean name clash): Generated bean classes must have unique names within a pack- age and MUST NOT clash with other classes in that package. Clashes during generation MUST be reported as an error and require user intervention via name customization to correct. Note that some platforms do not distiguish filenames based on case so comparisons MUST ignore case. However if two services in the same package have the same operation there is an overlap of the generated wrappers which then causes the schemas between the two WSDLS to overlap. Using the @RequestWrapper and @ResponseWrapper annotations does separate the wrappers which also corrects the WSDLs, from the JAX-WS spec 'Conformance' paragraphs above this conflict should have been identified and reported as an error during deployment. -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2768) Make sure SOAP stack test suite passes also when no internet connection is available

by Richard Opalka (JIRA)

Make sure SOAP stack test suite passes also when no internet connection is available ------------------------------------------------------------------------------------ Key: JBWS-2768 URL: https://jira.jboss.org/jira/browse/JBWS-2768 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-metro-3.2.0, jbossws-cxf-3.2.0, jbossws-native-3.2.0 Reporter: Richard Opalka Assignee: Jim Ma Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 Our test suites are running on http://jbossws.jboss.org:8180/hudson/ with internet connection available. Make sure our test suites run without failures also in case no internet connection is available. (I noticed that e.g. CXF stack test suite is failing when there's no internet connection available). Suggested way of running the test suite is to unplug the internet cable from the PC and run the test suite. -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2815) Change the ObjectName for jms endpoint

by Jim Ma (JIRA)

Change the ObjectName for jms endpoint -------------------------------------- Key: JBWS-2815 URL: https://jira.jboss.org/jira/browse/JBWS-2815 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Fix For: jbossws-cxf-3.3 -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2791) Investigate to register the jms endpoint into endpoint registry in cxf stack

by Jim Ma (JIRA)

Investigate to register the jms endpoint into endpoint registry in cxf stack ----------------------------------------------------------------------------- Key: JBWS-2791 URL: https://jira.jboss.org/jira/browse/JBWS-2791 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jim Ma Fix For: jbossws-cxf-3.3 -- 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

14 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (JBWS-2861) Remove classes with STAX support that are not used at all

by Richard Opalka (JIRA)

Remove classes with STAX support that are not used at all --------------------------------------------------------- Key: JBWS-2861 URL: https://jira.jboss.org/jira/browse/JBWS-2861 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3 -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3095) WRONG_DOCUMENT_ERR when accessing SOAPMessage DOM using WebServiceProvider and Provider<SOAPMessage>

by Ray Cardillo (JIRA)

WRONG_DOCUMENT_ERR when accessing SOAPMessage DOM using WebServiceProvider and Provider<SOAPMessage> ---------------------------------------------------------------------------------------------------- Key: JBWS-3095 URL: https://jira.jboss.org/browse/JBWS-3095 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.1 Environment: JBossAS Community 5.1, JBossWS-Native 3.3.1, upgraded Xalan-Java 2.7.1 Reporter: Ray Cardillo While converting some code from JBossWS-Metro to JBossWS-Native, we have been working through a bug that seems to be related to XML parsing inconsistencies due to the different DOM implementations that are used by the two technologies. We have a web service that is using the @WebServiceProvider feature of JAX-WS to create a custom Provider<SOAPMessage> so we can parse the XML directly. However, any time we try to extract the XML, in any number of ways, it causes an internal "expandToDOM" to be called that ends up failing due to a WRONG_DOCUMENT_ERR. At first we thought we were doing something incorrectly, but after careful analysis, and experimenting with many different ways of getting elements from the incoming SOAPMessage, we see this same stack trace in each case. So it looks like there is a bug in the internal expansion. org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it. at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown Source) at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source) at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source) at org.jboss.ws.core.soap.NodeImpl.appendChild(NodeImpl.java:481) at org.jboss.ws.core.soap.SOAPContentElement.appendChild(SOAPContentElement.java:467) at org.jboss.ws.core.soap.SOAPElementImpl.addChildElement(SOAPElementImpl.java:264) at org.jboss.ws.core.soap.SOAPContentElement.addChildElement(SOAPContentElement.java:192) at org.jboss.ws.core.soap.XMLContent.expandContainerChildren(XMLContent.java:355) at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:105) at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:143) at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:85) at org.jboss.ws.core.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:532) at org.jboss.ws.core.soap.SOAPContentElement.getFirstChild(SOAPContentElement.java:488) ... This same stack trace occurs if trying to do anything that requires extracting Nodes or Elements from the SOAPMessage. Example 1: Node node = msg.getBody(); or Node node = msg.getBody().getFirstChild(); or Node node = iterate over msg.getBody().getChildNodes(); or Node node = iterate over msg.getBody().getChildElements(); ... StringWriter sw = new StringWriter(); tr.transform(new DOMSource(node), new StreamResult(sw)); ... Example 2: msg.getBody().getChildElements(); ... SAAJResult sr = new SAAJResult(element); sr.getResult(); ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2936) Remove dependency of jbossws-native-core.jar on xerces implementation classes

by Richard Opalka (JIRA)

Remove dependency of jbossws-native-core.jar on xerces implementation classes ----------------------------------------------------------------------------- Key: JBWS-2936 URL: https://jira.jboss.org/jira/browse/JBWS-2936 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-3.3.1 -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2436) Look for eventual optimizations when scanning classes

by Alessio Soldano (JIRA)

Look for eventual optimizations when scanning classes ----------------------------------------------------- Key: JBWS-2436 URL: https://jira.jboss.org/jira/browse/JBWS-2436 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146807 -- 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

14 years, 1 month

2
11
0 / 0

[JBoss JIRA] Created: (JBWS-2510) Error messages internationalization

by Alessio Soldano (JIRA)

Error messages internationalization ----------------------------------- Key: JBWS-2510 URL: https://jira.jboss.org/jira/browse/JBWS-2510 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-native-3.1.1, jbossws-metro-3.1.1, jbossws-cxf-3.1.1 -- 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

14 years, 1 month

2
11
0 / 0

[JBoss JIRA] Created: (JBWS-3077) SchemaLocation of imported schemas rewritten in WSDL do not support https

by David Boeren (JIRA)

SchemaLocation of imported schemas rewritten in WSDL do not support https ------------------------------------------------------------------------- Key: JBWS-3077 URL: https://jira.jboss.org/browse/JBWS-3077 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-2.0.1.SP2 Environment: We are using a pre-defined WSDL using the wsdlLocation annotation. However, on deployment the schema locations are rewritten as absolute URLs over http. Since we only allow https access to external clients, the concern is that they may not be able to access these xsds. We have tried transport guarantee of CONFIDENTIAL but it still does not work. Reporter: David Boeren -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2010