May 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2194) request requires HTTP authentication: Unauthorized

by Richard Opalka (JIRA)

request requires HTTP authentication: Unauthorized -------------------------------------------------- Key: JBWS-2194 URL: http://jira.jboss.com/jira/browse/JBWS-2194 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.2 Reporter: Richard Opalka Assigned To: Alessio Soldano com.sun.xml.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:212) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:149) at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:118) at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436) at com.sun.xml.ws.client.Stub.process(Stub.java:248) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy59.testIsUserInRole(Unknown Source) at org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase.testIsUserInRole(WebServiceContextEJBTestCase.java:82) -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2193) Namespace issue for SEIs extending common interface

by Yogesh B (JIRA)

Namespace issue for SEIs extending common interface --------------------------------------------------- Key: JBWS-2193 URL: http://jira.jboss.com/jira/browse/JBWS-2193 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1, jbossws-native-2.0.3, jbossws-2.0.2, jbossws-2.0.1.SP2 Environment: WinXP,JBOSS4.2.2 and JBOSSWS 2.0.1 or JBOSSWS2.0.3 Reporter: Yogesh B HI Team, I have two webservices with separate SEIs (say A in targetNamespace X and B in targetNamespace Y) each one extending a common interface (say C) When I generated the WSDLs using the wsprovide tool, I can see the two wsdl files each containing the schema for the operations of common interface C getting generated as part of the SEI A's namespace and SEI B's namespace individually which is expected as per the standards.. I deployed these webservices in JBoss4.2.2 with JBossWS2.0.3. When I tried to open the wsdls from the JBoss server, the wsdls generated from the jboss server seems to have the operations of common interface C available as part of the SEI A. But for the SEI B, the operations of common interface C are imported from SEI A's namespace. I was expecting the operations of common interface C to be available in each individual webservice's namespace as unique operations. I also tried to explicitly specify the XmlType annotation in the common interface class C to have a common namespace but even this attempt got failed. Pls let me know how to workaround this problem. -- 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, 8 months

3
5
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

15 years, 9 months

2
3
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

15 years, 9 months

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

15 years, 9 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2088) Relax matching requirements in decodeMultipartRelatedMessage()

by David Boeren (JIRA)

Relax matching requirements in decodeMultipartRelatedMessage() -------------------------------------------------------------- Key: JBWS-2088 URL: http://jira.jboss.com/jira/browse/JBWS-2088 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.4 Reporter: David Boeren Apache Axis sends a slightly non-standard value in the Content-Type which many WS implementations accept but JBossWS does not, and this is interfering with multipart related service calls. The "start" tag in the Content-Type has an incorrect format. It is this: start="0.urn:uuid:278C3ADFCFF3AF170A1206560191992@apache.org"; but it should be this: start="<0.urn:uuid:278C3ADFCFF3AF170A1206560191992@apache.org>"; To work around that problem, change this method: org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage Change this: public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException { String boundaryParameter = contentType.getParameter("boundary"); String start = contentType.getParameter("start"); to this: public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException { String boundaryParameter = contentType.getParameter("boundary"); String start = 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

15 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBWS-2171) JBossClientMetaData.class not found

by Thomas Diesler (JIRA)

JBossClientMetaData.class not found ----------------------------------- Key: JBWS-2171 URL: http://jira.jboss.com/jira/browse/JBWS-2171 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2125) Unifiy JAXB deployment

by Thomas Diesler (JIRA)

Unifiy JAXB deployment ---------------------- Key: JBWS-2125 URL: http://jira.jboss.com/jira/browse/JBWS-2125 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2160) Upgrade CXF to 2.1

by Richard Opalka (JIRA)

Upgrade CXF to 2.1 ------------------ Key: JBWS-2160 URL: http://jira.jboss.com/jira/browse/JBWS-2160 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.0.1 Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-3.0.2 CXF 2.1 is already available and supports JAX-WS 2.1-1 -- 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, 10 months

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 May 2008