July 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1813) context-root in jboss.xml is ignored

by Thomas Diesler (JIRA)

context-root in jboss.xml is ignored ------------------------------------ Key: JBWS-1813 URL: http://jira.jboss.com/jira/browse/JBWS-1813 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Affects Versions: jbossws-2.0.1 Reporter: Thomas Diesler Fix For: jbossws-2.0.2 I want to override the default context root for my Web Services. So in my jboss.xml for (myEjb.jar) I have [QUOTE] <context-root>/webservices</context-root> [/QUOTE] inside the jboss->webservices node. But this doesn't seem to be working, the WSDLs are published at http://host/myApp-myEjb/ -- 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, 4 months

6
20
0 / 0

[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

16 years, 5 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

16 years, 5 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

16 years, 5 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

16 years, 5 months

3
5
0 / 0

Problem with PolicyMetaDataBuilder in client side

by Wanignon F

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2216) Soap address incorrect for https

by Joan Pujol Espinar (JIRA)

Soap address incorrect for https --------------------------------- Key: JBWS-2216 URL: http://jira.jboss.com/jira/browse/JBWS-2216 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Joan Pujol Espinar Priority: Critical The soap address is incorrect for https. There's no way to change the soap address to https. Althouth I've in jboss-beans.xml <property name="webServiceHost">localhost</property> <property name="modifySOAPAddress">true</property> <property name="webServiceSecurePort">8545</property> <property name="webServicePort">8080</property> And I've the CONFIDENTIAL transport-guarantee in the webapp that has the ws. <user-data-constraint> <description>SSL</description> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> The generated WDSL always has soap:address with http <port binding="ns1:repositoriDocumentsBinding" name="RepositoriDocumentsWSPort"> <soap:address location="http://localhost:8080/xcpwsserver/RepositoriDocuments" /> </port> -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2243) Web Service not being deployed as service endpoint on server restart

by Jeff Rhodes (JIRA)

Web Service not being deployed as service endpoint on server restart -------------------------------------------------------------------- Key: JBWS-2243 URL: http://jira.jboss.com/jira/browse/JBWS-2243 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.2 Environment: JBoss AS 4.2.2, JBossWS Metro 3.0.2, Win XP Pro SP2, JDK1.5.0_06 Reporter: Jeff Rhodes >From comparing behavior between JBossWS Metro 3.0.1 and 3.0.2, I think I've identified the problem. When JBossWS Metro deploys a Web Service, it saves a copy of the original web.xml file in a file named "web.xml.org", then modifies the web.xml and adds some JBossWS-specific entries. It also creates a sun-jaxws.xml file in the server's "tmp/jbossws" directory. In JBossWS Metro 3.0.1, when the container is undeploying a Web service, it deletes the modified web.xml file and then restores the original web.xml file by renaming the "web.xml.org" file to "web.xml". It also deletes the sun-jaxws.xml file in the tmp directory. However, in JBossWS Metro 3.0.2, the modified web.xml is not deleted, and the "web.xml.org" file is not renamed back to "web.xml". (It does delete the sun-jaxws.xml file from the tmp directory). This causes the Web service to be deployed as a regular servlet on subsequent server starts. In order to get the service to deploy again as a Web service endpoint, one must manually go into the war directory and delete the "web.xml" file, then rename the "web.xml.org" file back to "web.xml" before starting the server. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Commented: (JBWS-2186) Transforming from SAAJ SOAPBody to StreamResult throws IndexOutOfBoundsException

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2186?page=com.atlassian.jira.plug... ] Alessio Soldano commented on JBWS-2186: --------------------------------------- I've added your test to the native testsuite. Our implementation of Node, NodeImpl, holds the actual w3c node along with its children and our implementation of soapChildren. The exception you were having was due to the latter being null while it should have not. That's happen because of the transformation you use to append your document content to the SOAPBody. I've put a check there to prevent throwing the exception, but I know that's not the solution of your issue, as you don't get the soap message you would expect. I'm writing more on the forum. > Transforming from SAAJ SOAPBody to StreamResult throws IndexOutOfBoundsException > -------------------------------------------------------------------------------- > > Key: JBWS-2186 > URL: https://jira.jboss.org/jira/browse/JBWS-2186 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: OS X, JDK 1.5, JBoss AS 4.2.2 > Reporter: Arjen Poutsma > Assignee: Alessio Soldano > Fix For: jbossws-native-3.0.3 > > Attachments: saaj-test.zip > > > When running the following program within JBoss: > MessageFactory messageFactory = MessageFactory.newInstance(); > Transformer transformer = TransformerFactory.newInstance().newTransformer(); > SOAPMessage message = messageFactory.createMessage(); > Document document = createDocument(); > SOAPBody body = message.getSOAPBody(); > transformer.transform(new DOMSource(document), new DOMResult(body)); > body = message.getSOAPBody(); > transformer.transform(new DOMSource(body), new StreamResult(System.out)); > a IndexOutOfBoundsException is thrown on the last line. The attached zip file contains a simple Servlet which can be used to reproduce this. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2258) Fix testcase org.jboss.test.ws.tools.enums.EnumTestCase

by Alessio Soldano (JIRA)

Fix testcase org.jboss.test.ws.tools.enums.EnumTestCase ------------------------------------------------------- Key: JBWS-2258 URL: https://jira.jboss.org/jira/browse/JBWS-2258 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2, jbossws-native-3.0.1 Reporter: Alessio Soldano Assignee: Darran Lofthouse The test case 'org.jboss.test.ws.tools.enums.EnumTestCase' is making an invalid assumption on how a decimal value should be marshalled. This test case is failing since the most recent JBossXB upgrade (1.0.0.SP3). -- 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

16 years, 5 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 July 2008