jbossws-issues August 2008

jbossws-issues@lists.jboss.org

1 participants
124 discussions

[JBoss JIRA] Created: (JBWS-2183) SOAP 1.2 Endpoint Deployed as SOAP 1.1

by Darran Lofthouse (JIRA)

SOAP 1.2 Endpoint Deployed as SOAP 1.1 -------------------------------------- Key: JBWS-2183 URL: http://jira.jboss.com/jira/browse/JBWS-2183 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.1.SP2 A SEI annotated as: - @WebService(targetNamespace = "http://www.jboss.org/support/phonebook") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) public interface PhoneBook extends Remote The binding in the generated WSDL is still SOAP 1.1 based: - <binding name='PhoneBookBinding' type='tns:PhoneBook'> <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/> <operation name='lookup'> <soap:operation soapAction=''/> <input> <soap:body use='literal'/> </input> <output> <soap:body use='literal'/> </output> </operation> </binding> Where - xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' -- 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-2137) @WebWservice does not work with class isolation

by Thomas Diesler (JIRA)

@WebWservice does not work with class isolation ------------------------------------------------ Key: JBWS-2137 URL: http://jira.jboss.com/jira/browse/JBWS-2137 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 It seems that Web Services do not work when the EAR that contains the @WebService class has an isolated classloader. Here is my take on what happens: You deploy the ear and JBoss creates a war, that contains a web.xml, that points to the org.jboss.ws.server.ServiceEndpointServlet. You can send a request to the web service bean no problem, but any objects that get returned from it will throw a NoClassDefFoundError because this ServiceEndpointServlet is deployed outside of the EAR and, since it has an isolated classloader, can't reference the returned class. My application works absolutely fine when I turn off all isolation of the classloader. I don't think this can be fixed. Any ideas? -- 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
3
0 / 0

[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

← Newer
1
...
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2008