November 2010 - jbossws-issues - Jboss List Archives

[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] Updated: (JBWS-751) Multiple schema imports with the same namespace

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/browse/JBWS-751?page=com.atlassian.jira.plugin.sys... ] Alessio Soldano updated JBWS-751: --------------------------------- Fix Version/s: (was: jbossws-native-3.4.1) > Multiple schema imports with the same namespace > ----------------------------------------------- > > Key: JBWS-751 > URL: https://jira.jboss.org/browse/JBWS-751 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Thomas Diesler > > <types> > <xs:schema> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRq.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRs.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="StatusRs.xsd"/> > </xs:schema> > </types> > Current handling of schema imports is incorrect, since it does not allow for multiple imports with the same namespace. > private void handleSchemaImports(Element schemaEl, URL wsdlLoc) throws MalformedURLException > { > if (wsdlLoc == null) > throw new IllegalArgumentException("Cannot process import, parent location not set"); > > Iterator it = DOMUtils.getChildElements(schemaEl, new QName(Constants.NS_SCHEMA_XSD, "import")); > while (it.hasNext()) > { > Element includeEl = (Element)it.next(); > String schemaLocation = includeEl.getAttribute("schemaLocation"); > String namespace = includeEl.getAttribute("namespace"); > > log.trace("handleSchemaImport: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > > // Skip, let the entity resolver resolve these > if (namespace.length() > 0 && schemaLocation.length() > 0) > { > URL currLoc = this.getLocationURL(wsdlLoc, schemaLocation); > schemaLocationsMap.put(namespace, currLoc); > } > else > { > log.warn("Skip invalid schema import: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > } > } > } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
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-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-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-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

[JBoss JIRA] Created: (JBWS-2461) Request / Response Resource Optimisation

by Darran Lofthouse (JIRA)

Request / Response Resource Optimisation ---------------------------------------- Key: JBWS-2461 URL: https://jira.jboss.org/jira/browse/JBWS-2461 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.6 There are a few points where the management of resources can be optimised, in these places we are relying on a few techniques that are leading to potential leaks. The first area to optimise is the use of ThreadLocals for DocumentBuilders etc - these should be optimised to be better related to the request / response. A second area relates to SwapableMemoryDataSource - something is needed to clean up files not automatically deleted from killed / crashed JVMs. Secondly relying on finalize to delete the files can lead to a large number of files on disk before GC especially with large heaps. Ideally these will be better associated with the current request to be cleaned up at the end of processing. Although these are two different problems I have grouped them together as the common problem is tracking resources with the request they really belong to. -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2696) Better logging for messages that can not be parsed

by Darran Lofthouse (JIRA)

Better logging for messages that can not be parsed -------------------------------------------------- Key: JBWS-2696 URL: https://jira.jboss.org/jira/browse/JBWS-2696 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 The MessageFactoryImpl class uses for the following check for the content type of the incoming message: - if (isSoapContent(contentType) == false) { throw new SOAPException("Unsupported content type: " + contentType); } For various servers even though the incoming message is not a SOAP message the message may still contain useful information that could help diagnose the failure. Consider adding an option to still log the payload of the incoming message. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2857) Validation for Document/Literal Bare Endpoints

by Darran Lofthouse (JIRA)

Validation for Document/Literal Bare Endpoints ---------------------------------------------- Key: JBWS-2857 URL: https://jira.jboss.org/jira/browse/JBWS-2857 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3 Section 3.6.2.2 of the JAX-WS specification describes the requirements for Document/Literal Bare deployments. JBossWS Native does not verify the requirement has been met and generates a WSDL inconsistent with the endpoint itself causing subsequent failures when the endpoint is called. The methods should be verified at deploy time. -- 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
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2010