June 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2234) SOAP 1.2 JAX-RPC Endpoint sends SOAP 1.1 messages

by Alessio Soldano (JIRA)

SOAP 1.2 JAX-RPC Endpoint sends SOAP 1.1 messages ------------------------------------------------- Key: JBWS-2234 URL: http://jira.jboss.com/jira/browse/JBWS-2234 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Alessio Soldano -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2187) Handler Chain Management Prevents Service Re-Use

by Darran Lofthouse (JIRA)

Handler Chain Management Prevents Service Re-Use ------------------------------------------------ Key: JBWS-2187 URL: http://jira.jboss.com/jira/browse/JBWS-2187 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-native-3.0.3 There are a couple of issues relating to how the handler configuration is managed by the javax.xml.ws.Service. 1 - Handlers Added Multiple Times Create new service. Create port setConfigName("Standard WSSecurity Client") Call endpoint. ** All works fine and WS-Security headers are added to outbound message. ** Create port setConfigName("Standard WSSecurity Client") Call endpoint. ** Now the WS-Security headers are added to the outgoing message twice ** The creation of the port initialises the handler chain but it does not clear the old handlers, as the list of handlers is referenced by the Service each port creation adds a new set of handlers. 2 - Thread safety. Due to the above behaviour is becomes apparent that even if each thread uses it's own Port there is still a common Service so setting the configuration on one Port will affect the other Port instances, in addition to this as the configuration uses a HandlerResolver also Collections local to the Service there is a possibility that these will be modified and accessed by different threads concurrently. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2221) FileNotFound when targetNamespace has parameters "?"

by Amancio D￭az (JIRA)

FileNotFound when targetNamespace has parameters "?" ---------------------------------------------------- Key: JBWS-2221 URL: http://jira.jboss.com/jira/browse/JBWS-2221 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Environment: Linux 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686 GNU/Linux Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) [org.jboss.wsf.stack.jbws.NativeServerConfig] JBoss Web Services - Native [org.jboss.wsf.stack.jbws.NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044) Java version: 1.5.0_15,Sun Microsystems Inc Java VM: Java HotSpot(TM) Server VM 1.5.0_15-b04,Sun Microsystems Inc. Reporter: Amancio D￭az Developing a client of a web service that has a target namespace defined as follows: targetNamespace="http://metropolis.caixagalicia.es/ConectorWS/services/SN555167?wsdl" When creating the Service an exception is thrown. 2008-06-11 14:09:06,706 DEBUG [org.jboss.ws.tools.JavaToXSD] Load schema: http://metropolis.caixagalicia.es/ConectorWS/services/SN555167?wsdl=file:... 2008-06-11 14:09:06,706 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=null,sysid=file:/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167?wsdl7760.xsd] 2008-06-11 14:09:06,709 TRACE [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveIDAsResourceURL, id=file:/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167?wsdl7760.xsd 2008-06-11 14:09:06,709 TRACE [org.jboss.ws.core.utils.JBossWSEntityResolver] Trying to resolve id as a URL 2008-06-11 14:09:06,710 TRACE [org.jboss.ws.core.utils.JBossWSEntityResolver] Failed to obtain URL.InputStream from id: file:/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167?wsdl7760.xsd java.io.FileNotFoundException: /opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167 at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:94) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:103) at java.net.URL.openStream(URL.java:1007) at org.jboss.ws.core.utils.ResourceURL.openStream(ResourceURL.java:57) at org.jboss.ws.core.utils.JBossWSEntityResolver.resolveSystemIDAsURL(JBossWSEntityResolver.java:98) at org.jboss.ws.core.utils.JBossWSEntityResolver.resolveEntity(JBossWSEntityResolver.java:68) at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:178) at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:401) at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128) at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:295) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:86) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:140) at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:64) at javax.xml.ws.Service.<init>(Service.java:81) .... 2008-06-11 14:09:06,713 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] Cannot resolve entity: [pub=null,sysid=file:/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167?wsdl7760.xsd] 2008-06-11 14:09:06,714 WARN [net.caixagaliciamoviles.pruebas.metropolis.PruebasServicioWebJMX] Error en URL java.lang.NullPointerException at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:179) at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:401) The file [/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167?wsdl7760.xsd] exists, but jboss searchs for [/opt/jboss/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metropolis.caixagalicia.es_ConectorWS_services_SN555167] which does not exists. If I hand copy the file to the new name then the service works ok. (this has to be done by hand after deploy in the JBOSS_HOME/server/default/tmp/jbossws/ directory. The class org.jboss.net.protocol.file.FileURLConnection cuts all the content after the "?". -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2182) Partial encryption not working

by Alessio Soldano (JIRA)

Partial encryption not working ------------------------------ Key: JBWS-2182 URL: http://jira.jboss.com/jira/browse/JBWS-2182 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-native-3.0.3 Partial encryption of messages is not working since the operation config is always set to null -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2229) Provide jbossws-metro-resources.zip maven artifact

by Richard Opalka (JIRA)

Provide jbossws-metro-resources.zip maven artifact -------------------------------------------------- Key: JBWS-2229 URL: http://jira.jboss.com/jira/browse/JBWS-2229 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.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, 6 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2231) Provide jbossws-cxf-resources maven artifact

by Richard Opalka (JIRA)

Provide jbossws-cxf-resources maven artifact -------------------------------------------- Key: JBWS-2231 URL: http://jira.jboss.com/jira/browse/JBWS-2231 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-cxf-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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2228) Provide jbossws-native-resources.zip maven artifact

by Richard Opalka (JIRA)

Provide jbossws-native-resources.zip maven artifact --------------------------------------------------- Key: JBWS-2228 URL: http://jira.jboss.com/jira/browse/JBWS-2228 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-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, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2237) Upgrade to JBoss JAXR 1.2.0.SP1

by Darran Lofthouse (JIRA)

Upgrade to JBoss JAXR 1.2.0.SP1 ------------------------------- Key: JBWS-2237 URL: http://jira.jboss.com/jira/browse/JBWS-2237 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Affects Versions: jbossws-native-3.0.2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-native-3.0.3 The JBoss JAXR 1.2.0.SP1 release contains fixes to cope with the whitespace handling introduced in JBossWS. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1673) Fix JAXR samples for SunRI

by Thomas Diesler (JIRA)

Fix JAXR samples for SunRI -------------------------- Key: JBWS-1673 URL: http://jira.jboss.com/jira/browse/JBWS-1673 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 2007-06-01 06:12:43,257 ERROR [org.jboss.jaxr.juddi.transport.SaajTransport:94] Exception:: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2409) at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:150) at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:111) at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2012) at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createAttributeNS(SOAPDocumentImpl.java:161) at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:684) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.setAttributeNS(ElementImpl.java:1241) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:499) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:471) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttribute(ElementImpl.java:454) at org.jboss.jaxr.juddi.transport.SaajTransport.appendAttributes(SaajTransport.java:156) at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:180) at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:181) at org.jboss.jaxr.juddi.transport.SaajTransport.createSOAPMessage(SaajTransport.java:136) at org.jboss.jaxr.juddi.transport.SaajTransport.send(SaajTransport.java:77) at org.apache.juddi.proxy.RegistryProxy.execute(RegistryProxy.java:368) at org.apache.juddi.AbstractRegistry.saveBusiness(AbstractRegistry.java:582) at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.executeOperation(BusinessLifeCycleManagerImpl.java:532) at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.saveOrganizations(BusinessLifeCycleManagerImpl.java:389) at org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase.setUp(JaxrBusinessQueryTestCase.java:58) -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2133) Failed to access the WSDL

by Thomas Diesler (JIRA)

Failed to access the WSDL ------------------------- Key: JBWS-2133 URL: http://jira.jboss.com/jira/browse/JBWS-2133 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-1.0.1 Reporter: Thomas Diesler tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.68 sec [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED BUILD SUCCESSFUL Total time: 5 seconds [tdiesler@tdvaio trunk]$ cat output/tests/reports/TEST-org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase.txt Testsuite: org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.68 sec Testcase: testPositive took 1.368 sec Caused an ERROR Failed to access the WSDL at: http://localhost:8080/test-context?wsdl. It failed with: http://localhost:8080/test-context?wsdl. javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:8080/test-context?wsdl. It failed with: http://localhost:8080/test-context?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:263) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:226) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:174) 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.jbws1813.JBWS1813TestCase.testPositive(JBWS1813TestCase.java:61) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.io.FileNotFoundException: http://localhost:8080/test-context?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) -- 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, 6 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2008