July 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2630) Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar.

by Daniel Bevenius (JIRA)

Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar. --------------------------------------------------------------------------------------------------------- Key: JBWS-2630 URL: https://jira.jboss.org/jira/browse/JBWS-2630 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Priority: Minor I noticed this when working on getting examples for JBossESB running on JBoss AS 5. We have .esb archives (jar archives) that can contain a .war inside of them. For example, we have a quickstart that is named Quickstart_webservice_consumer1.esb which contains a Quickstart_webservice_consumer1.war. Deploying this on AS 5 will produce the following "Endpoint Address" in http://localhost:8080/jbossws/services: http://127.0.0.1:8080/Quickstart_webservice_consumer1-Quickstart_webservi... But if I try to access that the resource is not found. I was not sure about the component for this. The ContextServlet exists in the jbossws-framework project but I don't know if that maps to one of the components in the dropdown. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2712) Allign JBossWS Scout version with Scout version in AS

by Richard Opalka (JIRA)

Allign JBossWS Scout version with Scout version in AS ----------------------------------------------------- Key: JBWS-2712 URL: https://jira.jboss.org/jira/browse/JBWS-2712 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2402) Upgrade jUDDI to 2.0rc5

by Alessio Soldano (JIRA)

Upgrade jUDDI to 2.0rc5 ----------------------- Key: JBWS-2402 URL: https://jira.jboss.org/jira/browse/JBWS-2402 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5 We should upgrade jUDDI dependency to 2.0rc5 to satisfy the SOA-P requirements. See the forum thread for more details. -- 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, 4 months

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

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

16 years, 5 months

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

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

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

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

16 years, 5 months

5
18
0 / 0

[JBoss JIRA] Created: (JBWS-2508) WSProvide output is not correctly redirected

by Alessio Soldano (JIRA)

WSProvide output is not correctly redirected -------------------------------------------- Key: JBWS-2508 URL: https://jira.jboss.org/jira/browse/JBWS-2508 Project: JBoss Web Services Issue Type: Bug 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 The WSProvide output (more generally the cxf tool output) is not redirected to a given stream. We should make this possible (plus making the WSProviderTestCase less verbose...) -- 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
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2009