June 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2687) JBossWS commandline tools requires Sun JDK to work. This dependency must be removed

by Richard Opalka (JIRA)

JBossWS commandline tools requires Sun JDK to work. This dependency must be removed ----------------------------------------------------------------------------------- Key: JBWS-2687 URL: https://jira.jboss.org/jira/browse/JBWS-2687 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Richard Opalka Assignee: Alessio Soldano Priority: Critical Fix For: jbossws-native-3.2.0 One of the goals for the next SOA-P CP is to see the whole platform certified with OpenJDK 1.6 I tried to run JBossWS on OpenJDK 1.6 and found the following dependency in our code: --- [ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter. compilation failed, errors should have been reported Failed to invoke WsImport java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80) --- This dependency causes our command line tools (at least wsconsume) doesn't work on Open JDK :( -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2457) Update WS-Addressing tutorials to use JAXWS 2.1 AddressingFeature

by Alessio Soldano (JIRA)

Update WS-Addressing tutorials to use JAXWS 2.1 AddressingFeature ----------------------------------------------------------------- Key: JBWS-2457 URL: https://jira.jboss.org/jira/browse/JBWS-2457 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano Assignee: Richard Opalka -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2320) Check JBossWS Maven Support on Windows OS

by Richard Opalka (JIRA)

Check JBossWS Maven Support on Windows OS ----------------------------------------- Key: JBWS-2320 URL: https://jira.jboss.org/jira/browse/JBWS-2320 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 It will make our community happy -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2672) Make the JBoss Remoting property 'socketFactoryClassName' available to allow clients to specify the SocketFactory

by Darran Lofthouse (JIRA)

Make the JBoss Remoting property 'socketFactoryClassName' available to allow clients to specify the SocketFactory ----------------------------------------------------------------------------------------------------------------- Key: JBWS-2672 URL: https://jira.jboss.org/jira/browse/JBWS-2672 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2587) Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite

by Richard Opalka (JIRA)

Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite ------------------------------------------------------------------------------------------ Key: JBWS-2587 URL: https://jira.jboss.org/jira/browse/JBWS-2587 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.0 Reporter: Richard Opalka Assignee: Alessio Soldano Priority: Optional Fix For: jbossws-native-3.1.1 Results : Failed tests: testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleUsernameTestCase) testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleDispatchTestCase) Tests run: 1438, Failures: 2, Errors: 0, Skipped: 0 I'd like to see that fixed. Feel free to reschedule to next release Alessio (since code freeze is away already) but if you have some time could you have a look now? The strange thing for me is we can't reproduce it on hudson. -- 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, 9 months

2
7
0 / 0

[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

14 years, 9 months

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

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

14 years, 10 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, 10 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

14 years, 10 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2009