February 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2435) Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/

by Alessio Soldano (JIRA)

Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/ ----------------------------------------------------------------------------- Key: JBWS-2435 URL: https://jira.jboss.org/jira/browse/JBWS-2435 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-native-3.0.6, jbossws-metro-3.0.6, jbossws-cxf-3.0.6 -- 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

15 years

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2151) We have to distribute wsrunclient.sh(.bat) for Metro and CXF

by Richard Opalka (JIRA)

We have to distribute wsrunclient.sh(.bat) for Metro and CXF ------------------------------------------------------------ Key: JBWS-2151 URL: http://jira.jboss.com/jira/browse/JBWS-2151 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Richard Opalka -- 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

15 years

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode

by Chyi Pin Lim (JIRA)

MTOM/XOP Interoperability - cid href URLEncode/URLDecode -------------------------------------------------------- Key: JBWS-2405 URL: https://jira.jboss.org/jira/browse/JBWS-2405 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA Reporter: Chyi Pin Lim WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL Encoded. As such, JBossWS is unable to find the attachment. Example: <xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/> --uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1 Content-ID: <http://tempuri.org/1/633631227250468750> Since this is an interoperability issue, I don't know how to create a test case under the test suite to simulate this error. -- 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

15 years

4
5
0 / 0

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

by Alessio Soldano (JIRA)

FastInfoset interoperability ---------------------------- Key: JBWS-2538 URL: https://jira.jboss.org/jira/browse/JBWS-2538 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 We should do some tests using fastinfoset with jbossws-cxf like we did with jbossws-native. See linked issue. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2514) wsprovide.sh missing libraries

by Bryan Kearney (JIRA)

wsprovide.sh missing libraries ------------------------------ Key: JBWS-2514 URL: https://jira.jboss.org/jira/browse/JBWS-2514 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Environment: JBoss 5.0.0 GA, Metro 3.0.5GA, Sun jdk 1.6.11, Fedora 10 Reporter: Bryan Kearney The wsprovide.sh script fails when attempting to generate the artifacts. It failed to locate the following classes: org.jboss.ws.core.soap.SAAJMetaFactoryImpl com.sun.xml.ws.security.secext10.SecurityTokenReferenceType My solution was to edit the file with these lines: WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossws-native-core.jar" WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/xws-security.jar" Having copied the jar files from the default deployers directory. I believe this is related to https://jira.jboss.org/jira/browse/JBWS-2511 -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2259) Review MTOM Detection

by Darran Lofthouse (JIRA)

Review MTOM Detection --------------------- Key: JBWS-2259 URL: https://jira.jboss.org/jira/browse/JBWS-2259 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.3 Currently MTOM is only enabled if a type annotated with @XmlMimeType - the content-type headers from the incoming message should be sufficient to decide is MTOM is required. -- 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

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2533) Fix MTOM/XOP Content Type Testcase failure

by Magesh Kumar B (JIRA)

Fix MTOM/XOP Content Type Testcase failure ------------------------------------------ Key: JBWS-2533 URL: https://jira.jboss.org/jira/browse/JBWS-2533 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.0.5 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 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

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2015) Modify addressing handlers to work with the JAXWS-2.1 API

by Thomas Diesler (JIRA)

Modify addressing handlers to work with the JAXWS-2.1 API --------------------------------------------------------- Key: JBWS-2015 URL: http://jira.jboss.com/jira/browse/JBWS-2015 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-native-2.0.5 Currently we have two implementations of EndpointReference. This needs to be cleaned up to a single supported version. -- 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

15 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2166) WSA client handler throws exception when installing reference parameters

by Andrew Dinn (JIRA)

WSA client handler throws exception when installing reference parameters ------------------------------------------------------------------------ Key: JBWS-2166 URL: http://jira.jboss.com/jira/browse/JBWS-2166 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Andrew Dinn WSAddressingClientHandler.handleOutbound in package org.jboss.ws.extensions.addressing.jaxws is throwing the following exception when inserting reference parameters into a reply: 10:52:44,104 ERROR [SOAPFaultHelperJAXWS] SOAP request exception javax.xml.ws.WebServiceException: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it. at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155) at org.jboss.ws.core.jaxws.client.ClientImpl.callRequestHandlerChain(ClientImpl.java:191) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:298) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) at $Proxy93.soapFault(Unknown Source) at com.arjuna.webservices11.wsaddr.client.SoapFaultClient.sendSoapFault(SoapFaultClient.java:72) at com.arjuna.webservices11.wsat.client.ParticipantClient.sendSoapFault(ParticipantClient.java:150) at com.arjuna.wst11.messaging.CoordinatorProcessorImpl.sendInvalidState(CoordinatorProcessorImpl.java:272) at com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(CoordinatorProcessorImpl.java:176) at com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl$1.executeTask(CoordinatorPortTypeImpl.java:61) at com.arjuna.services.framework.task.TaskWorker.run(TaskWorker.java:65) at java.lang.Thread.run(Thread.java:595) Caused by: 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:477) at org.jboss.ws.core.soap.SOAPHeaderImpl.appendChild(SOAPHeaderImpl.java:198) at org.jboss.ws.core.soap.SOAPElementImpl.addChildElement(SOAPElementImpl.java:274) at org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement(SOAPHeaderImpl.java:70) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendElement(SOAPAddressingPropertiesImpl.java:374) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendElements(SOAPAddressingPropertiesImpl.java:352) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:306) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler.handleOutbound(WSAddressingClientHandler.java:113) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) ... 13 more The situation which manifests this problem is as follows: Client A attaches WS AddressingProperties to a port for server B, It installs a ReplyTo epr whose address identifies server A. It attaches a reference parameter wsarj:identifier to the epr. Client A then invokes service B. The implementation method of service B retrieves the request AddressingProperties from its message context and sets up a reply AddressingProperties instance by calling AddressingProperties.initializeAsReply. It obtains a port for service A, installs the reply properties on the port then invokes service A. The client handler under this invocation gets the error. The problem is that the SOAP implementation does not copy the reference parameter Element instance when it tries to insert them into the outgoing message. intiializeAsReply retrieves these elements from the incoming context ReplyTo/FaultTo and adds them to the element extension list of the reply addressing context. The client handler calls SOAPAddressingHandlerImpl.writeHeaders to add these elements as headers in the outbound message. writeHeaders eventually calls SOAPHeaderImpl.addChildElement to add each reference parameter Element to the outgoing message header. addChildElement tests whether the Element is a SOAP element and, if so, assumes that it can be inserted directly into the outgoing message by calling appendElement. Unfortunately, the incoming reference parameters are associated with a dom node whose document is non-null and this barfs,claiming that someone is attempting a switcheroo on the document. -- 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

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2532) Fix MTOM/XOP Content Type Testcase failure

by Magesh Kumar B (JIRA)

Fix MTOM/XOP Content Type Testcase failure ------------------------------------------ Key: JBWS-2532 URL: https://jira.jboss.org/jira/browse/JBWS-2532 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.5 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: jbossws-metro-3.1.1 org.jboss.test.ws.jaxws.jbws2419.JBWS2419TestCase.testSOAP11ClientAccess Failing for the past 1 build (since Unstable#67) Took 0 seconds. javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:8080/jaxws-jbws2419/soap11?wsdl. It failed with: http://localhost:8080/jaxws-jbws2419/soap11?wsdl. at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:162) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:144) at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:264) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:227) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:175) at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104) at javax.xml.ws.Service.<init>(Service.java:56) at javax.xml.ws.Service.create(Service.java:680) at org.jboss.test.ws.jaxws.jbws2419.JBWS2419TestCase.testSOAP11ClientAccess(JBWS2419TestCase.java:85) Caused by: java.io.FileNotFoundException: http://localhost:8080/jaxws-jbws2419/soap11?wsdl at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1168) at java.net.URL.openStream(URL.java:1007) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:805) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:262) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:129) ... 36 more org.jboss.test.ws.jaxws.jbws2419.JBWS2419TestCase.testSOAP12ClientAccess Failing for the past 1 build (since Unstable#67) Took 0 seconds. javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:8080/jaxws-jbws2419/soap12?wsdl. It failed with: http://localhost:8080/jaxws-jbws2419/soap12?wsdl. at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:162) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:144) at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:264) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:227) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:175) at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104) at javax.xml.ws.Service.<init>(Service.java:56) at javax.xml.ws.Service.create(Service.java:680) at org.jboss.test.ws.jaxws.jbws2419.JBWS2419TestCase.testSOAP12ClientAccess(JBWS2419TestCase.java:66) Caused by: java.io.FileNotFoundException: http://localhost:8080/jaxws-jbws2419/soap12?wsdl at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1168) at java.net.URL.openStream(URL.java:1007) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:805) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:262) at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:129) ... 36 more -- 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

15 years, 1 month

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2009