August 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2720) Endpoints implementing javax.xml.rpc.server.ServiceLifecycle lifecycle methods are called per invocation

by Richard Opalka (JIRA)

Endpoints implementing javax.xml.rpc.server.ServiceLifecycle lifecycle methods are called per invocation -------------------------------------------------------------------------------------------------------- Key: JBWS-2720 URL: https://jira.jboss.org/jira/browse/JBWS-2720 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-native-3.1.2 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0 These methods have to be called only when JAX-RPC beans are constructed and destroyed. -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2661) Remove proprietary CXF API usage from our samples/tests and update CXF documentation

by Richard Opalka (JIRA)

Remove proprietary CXF API usage from our samples/tests and update CXF documentation ------------------------------------------------------------------------------------ Key: JBWS-2661 URL: https://jira.jboss.org/jira/browse/JBWS-2661 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.1.2 Don't use the following classes directly: - org.apache.cxf.Bus - org.apache.cxf.BusFactory - org.apache.cxf.bus.spring.SpringBusFactory Replace it with providing META-INF/cxf.xml files in client jars to show our users how to do it properly (so their code can be migrated cross JAX-WS providers). -- 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

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2662) WebServiceContext injection into WS Provider leads to memory leaks

by Sergey Graschenko (JIRA)

WebServiceContext injection into WS Provider leads to memory leaks ------------------------------------------------------------------ Key: JBWS-2662 URL: https://jira.jboss.org/jira/browse/JBWS-2662 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Environment: Debian Linux 2.6.18-4-686, Java HotSpot(TM) Server VM (build 14.0-b13, mixed mode), JBoss AS 5.0.1.GA Reporter: Sergey Graschenko JBoss AS going out of memory after a few hrs of mild load (~100 request/minute) having the following code @WebServiceProvider(serviceName = "SampleService", portName = "SamplePort", wsdlLocation = "WEB-INF/wsdl/sample.wsdl") @BindingType(value = HTTPBinding.HTTP_BINDING) @ServiceMode(value = Service.Mode.PAYLOAD) public class SampleProvider extends AbstractServiceProvider implements Provider<Source> { @Resource(type = Object.class) protected WebServiceContext wsContext; public Source invoke(Source req) { MessageContext mc = wsContext.getMessageContext(); String path = ((String) mc.get(MessageContext.PATH_INFO)).substring(1); JAXBSource result; // // whatever // return result; } } As I mentioned in referenced forum thread, if I set wsContext to null after use, memory leak goes away. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2719) Allow jconsole to be attached to testsuite

by Alessio Soldano (JIRA)

Allow jconsole to be attached to testsuite ------------------------------------------ Key: JBWS-2719 URL: https://jira.jboss.org/jira/browse/JBWS-2719 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 JConsole (http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html) is an useful tool to look for memory leaks and generally for monitoring the use of resources. We should allow uses to attach jconsole to the testsuite (thus client side), as providing the -Dcom.sun.management.jmxremote sysprop on command line mvn is not enough. (please note I've already added the prop inadvertently in jbws native, this need to be configurable though) -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBWS-2716) WS-I: SOAPAction header does not contain the correct string value

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2716?page=com.atlassian.jira.plug... ] Kevin Conner commented on JBWS-2716: ------------------------------------ I suspect this is an ESB issue and not a JBossWS issue, why was this changed? As for the ESB issue, presumably this was using org.jboss.soa.esb.actions.soap.SOAPClient, can you confirm this? > WS-I: SOAPAction header does not contain the correct string value > ----------------------------------------------------------------- > > Key: JBWS-2716 > URL: https://jira.jboss.org/jira/browse/JBWS-2716 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-2.0.1.SP2 > Reporter: Boris Belovic > > We were performing webservice interoperability tests using WS-I test tools. There is a non-empty header SOAPAction in HTTP request message. This header contains "modifyQName" string as a value. According to the Basic Profile, there must be a non-empty soapAction attribute in binding element and this soapAction attribute must contain the same value as SOAPAction header in HTTP request. We find out that is not happening. There is SOAPAction header in HTTP request, but the corresponding soapAction attribute is empty. > This is a result from WS-I test tool we use for testing. This output shows non-empty SOAPAction header and an empty soapAction attribute: > HTTP headers: > POST /WS-I/HelloWorldWS HTTP/1.1 > Content-Type: text/xml;charset=UTF-8 > SOAPAction: "modifyQName" > User-Agent: Jakarta Commons-HttpClient/3.0.1 > Host: localhost:65432 > Content-Length: 299 > soapAction: > > Element Location: > lineNumber=154 > And here are two WSDL documents: > <definitions name='HelloWorldWSService' targetNamespace='http://ws_i.quickstart.samples.esb.soa.jboss.org/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://wsi/helloworld' xmlns:ns2='http://wsi/helloworld/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://ws_i.quickstart.samples.esb.soa.jboss.org/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <import location='http://localhost:8080/WS-I/imported.jsp' namespace='http://wsi/helloworld'></import> > <service name='HelloWorldWSService'> > <port binding='ns1:HelloWorldBinding' name='HelloWorldWSPort'> > <soap:address location='http://localhost:8080/WS-I/HelloWorldWS'/> > </port> > </service> > </definitions > In this WSDL document, down there is operation element with empty soapAction attribute. This attribute must contain the same value as SOAPAction header in a request. > <definitions name='HelloWorldWSService' targetNamespace='http://wsi/helloworld' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://wsi/helloworld' xmlns:ns2='http://wsi/helloworld/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://ws_i.quickstart.samples.esb.soa.jboss.org/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> > <types> > <xs:schema targetNamespace='http://wsi/helloworld' version='1.0' xmlns:ns1='http://wsi/helloworld/' xmlns:xs='http://www.w3.org/2001/XMLSchema'> > <xs:import namespace='http://wsi/helloworld/'/> > <xs:element name='modifyQName' nillable='true' type='ns1:modifyQName'/> > <xs:element name='modifyQNameResponse' nillable='true' type='ns1:modifyQNameResponse'/> > </xs:schema> > <xs:schema targetNamespace='http://wsi/helloworld/' version='1.0' xmlns:xs='http://www.w3.org/2001/XMLSchema'> > <xs:complexType name='modifyQName'> > <xs:sequence> > <xs:element minOccurs='0' name='value' type='xs:QName'/> > </xs:sequence> > </xs:complexType> > <xs:complexType name='modifyQNameResponse'> > <xs:sequence> > <xs:element minOccurs='0' name='return' type='xs:QName'/> > </xs:sequence> > </xs:complexType> > </xs:schema> > </types> > <message name='HelloWorld_modifyQName'> > <part element='ns1:modifyQName' name='modifyQName'></part> > </message> > <message name='HelloWorld_modifyQNameResponse'> > <part element='ns1:modifyQNameResponse' name='modifyQNameResponse'></part> > </message> > <portType name='HelloWorld'> > <operation name='modifyQName' parameterOrder='modifyQName'> > <input message='ns1:HelloWorld_modifyQName'></input> > <output message='ns1:HelloWorld_modifyQNameResponse'></output> > </operation> > </portType> > <binding name='HelloWorldBinding' type='ns1:HelloWorld'> > <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/> > <operation name='modifyQName'> > <soap:operation soapAction=''/> > <input> > <soap:body use='literal'/> > </input> > <output> > <soap:body use='literal'/> > </output> > </operation> > </binding> > </definitions> > Here are two SOAP message, which are parts of the communication: > Request: > <?xml version="1.0" encoding="UTF-8" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hel="http://wsi/helloworld"> > <soapenv:Header/> > <soapenv:Body> > <hel:modifyQName> >  > <value>qname_value</value> > </hel:modifyQName> > </soapenv:Body> > </soapenv:Envelope> > Response: > <?xml version="1.0" encoding="UTF-8" ?><env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns1:modifyQNameResponse xmlns:ns1="http://wsi/helloworld"><return>qname_value_modified</return></ns1:modifyQNameResponse></env:Body></env:Envelope> > Here is a link to Test Assertion Document with specified requirement: > http://www.ws-i.org/Testing/Tools/2005/01/SSBP10_BP11_TAD_1-0.htm#BP1116 > If there are any comments or request for any details please ask us. -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2247) Write test for JBWS-1190 from scratch using MessageContext properties

by Alessio Soldano (JIRA)

Write test for JBWS-1190 from scratch using MessageContext properties --------------------------------------------------------------------- Key: JBWS-2247 URL: http://jira.jboss.com/jira/browse/JBWS-2247 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Alessio Soldano The JBWS-1190 test currently should be re-written using the message context properties (looking at the data dir is not a valid solution for metro and cxf). Also please note that the information coming from the jbossws/services console might be misleading. -- 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

14 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2203) Implement standard message context properties

by Thomas Diesler (JIRA)

Implement standard message context properties --------------------------------------------- Key: JBWS-2203 URL: http://jira.jboss.com/jira/browse/JBWS-2203 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-native-3.0.2 Implement properties public static final String WSDL_DESCRIPTION = "javax.xml.ws.wsdl.description"; public static final String WSDL_SERVICE = "javax.xml.ws.wsdl.service"; public static final String WSDL_PORT = "javax.xml.ws.wsdl.port"; public static final String WSDL_INTERFACE = "javax.xml.ws.wsdl.interface"; public static final String WSDL_OPERATION = "javax.xml.ws.wsdl.operation"; -- 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2227) Investigate why multiple virtual hosts test fails on CXF

by Richard Opalka (JIRA)

Investigate why multiple virtual hosts test fails on CXF -------------------------------------------------------- Key: JBWS-2227 URL: http://jira.jboss.com/jira/browse/JBWS-2227 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.0.3 See jaxws/jbws1178 test -- 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

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1655) Add support for endpoint address rewriting

by Thomas Diesler (JIRA)

Add support for endpoint address rewriting ------------------------------------------ Key: JBWS-1655 URL: http://jira.jboss.com/jira/browse/JBWS-1655 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Affects Versions: xfire-1.2.6 Reporter: Thomas Diesler A jaxws endpoint that uses @WebService.wsdlLocation need to have the SOAP address rewriten to correspond to the actual address of the endpoint -- 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

14 years, 8 months

5
18
0 / 0

[JBoss JIRA] Created: (JBWS-2507) Support generics in wrapper classes

by Alessio Soldano (JIRA)

Support generics in wrapper classes ----------------------------------- Key: JBWS-2507 URL: https://jira.jboss.org/jira/browse/JBWS-2507 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, tools-jaxws Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 This is basically the same as JBWS-2477 except it's with JBossWS-CXF stack. -- 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

14 years, 8 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2009