October 2008 - jbossws-issues - Jboss List Archives

[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, 9 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, 9 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, 9 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, 9 months

5
18
0 / 0

[JBoss JIRA] Created: (JBWS-2370) Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap

by Richard Opalka (JIRA)

Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap ------------------------------------------------------------------------------------------------------------ Key: JBWS-2370 URL: https://jira.jboss.org/jira/browse/JBWS-2370 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 During deployment of the endpoints declared in my wars a call is made to AbstractServerConfig.getConnectorPort(). This fetches the WS Server MBean and tries to lookup objects of type "jboss.web:type=Connector,*". At the point where the lookup fails the jboss.web MBean has only one entry for the WebServer. In the run that I managed to debug the type=Connector entries were added at a later point. So, some of the subsequent calls to getConnectorPort() succeeded and also the AS bootstrap did not hang. I was unable to debug a case where the bootstrap did hang. -- 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-2346) Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive

by David Boeren (JIRA)

Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive ---------------------------------------------------------------------------- Key: JBWS-2346 URL: https://jira.jboss.org/jira/browse/JBWS-2346 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: David Boeren We are trying to migrate our application into JBOSS 4.3EAP, perviously my webservice application was using Sun's saaj api. During the migration, we have been decided to use JBoss SAAJ api and we are seeing some weird problem with an API in SOAPBody class. Here is the sample code: NodeList list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0", "AdhocQueryResponse"); System.out.println(list.getLength()); list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0", "ExtrinsicObject"); System.out.println(list.getLength()); The first call to getElementsByTagNameNS() was returning the element list, but the subsequent call was returning an empty nodelist. I am attaching a sample java project created to reproduce the problem. -- 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-2284) Using WSConsume on JBOSS 4.2.3.GA and JDK 1.6.0_07 leads to java.lang.NoClassDefFoundError: com/sun/tools/ws/wscompile/WsimportTool

by Hemant Satam (JIRA)

Using WSConsume on JBOSS 4.2.3.GA and JDK 1.6.0_07 leads to java.lang.NoClassDefFoundError: com/sun/tools/ws/wscompile/WsimportTool ----------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2284 URL: https://jira.jboss.org/jira/browse/JBWS-2284 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBOSS 4.2.3.GA JDK 1.6.0_07 Windows Reporter: Hemant Satam I have all the required files in jboss-4.2.3.GA\lib\endorsed. The classpath also ensures that jboss libraries are before jdk1.6 lib file. However on access of wsconsume the error produced is; JBossWS-Native stack deployed Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/tools/ws/wscompile/WsimportTool at org.jboss.ws.tools.jaxws.impl.SunRIConsumerFactoryImpl.createConsumer(SunRIConsumerFact oryImpl.java:36) at org.jboss.wsf.spi.tools.WSContractConsumer.newInstance(WSContractConsumer.java:73) at org.jboss.wsf.spi.tools.WSContractConsumer.newInstance(WSContractConsumer.java:56) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:195) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81) Caused by: java.lang.ClassNotFoundException: com.sun.tools.ws.wscompile.WsimportTool at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 5 more Is this a bug or something wrong that I am doing? -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2106) javax.xml.ws.addressing package not available in JBossWS-CXF

by Andrew Dinn (JIRA)

javax.xml.ws.addressing package not available in JBossWS-CXF ------------------------------------------------------------- Key: JBWS-2106 URL: http://jira.jboss.com/jira/browse/JBWS-2106 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-1.0.1 Reporter: Andrew Dinn The AddressingProperties and related API classes in the javax.xml.ws.addressing package are not available in JBossWS-CXF. These are needed for the Web Services Transactions 1.1 implementation to operate over the CXF stack. -- 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, 11 months

3
19
0 / 0

[JBoss JIRA] Created: (JBWS-1878) ConcurrentModificationException in JAXWS Handler when requests hit JBoss during application deployment

by Wojciech Kudla (JIRA)

ConcurrentModificationException in JAXWS Handler when requests hit JBoss during application deployment ------------------------------------------------------------------------------------------------------ Key: JBWS-1878 URL: http://jira.jboss.com/jira/browse/JBWS-1878 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1 Environment: AIX 5.3 ppc64, IBM JVM 9 (1.5.0), JBoss 4.2.1.GA with JBossWS 2.0.1.GA Reporter: Wojciech Kudla Priority: Critical When SOAP requests hit JBoss during application deployment they are somewhat queued and get processed just after the application starts. Everything works fine if the are only several requests. If there are more (like 30 or above) before the application starts, HandlerResolverImpl causes ConcurrentModificationException at line 22 (getHandlerChain()). This exception does not cause the application to stop working, but results in a very strange behaviour, namely: every request goes only through JAXWS Handler twice (on inbound and outbound traffic) but does not hit service implementation (in my case - EJB3 SLSB). The only clue for me to resolve this problem was to stick to the ConcurrentModificationException and its stacktrace. Going down this path I decided to modify some code in class org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS. I synchronized a block of code responsible for initiating handler chains, so the modified method looks like this: public boolean callRequestHandlerChain(ServerEndpointMetaData sepMetaData, HandlerType type) { log.debug("callRequestHandlerChain: " + type); // Initialize the handler chain if (isInitialized() == false) { synchronized(resolver) { resolver.initHandlerChain(sepMetaData, HandlerType.PRE, true); resolver.initHandlerChain(sepMetaData, HandlerType.ENDPOINT, true); resolver.initHandlerChain(sepMetaData, HandlerType.POST, true); setInitialized(true); } } HandlerChainExecutor executor = createExecutor(sepMetaData, type); MessageContext msgContext = (MessageContext)MessageContextAssociation.peekMessageContext(); return executor.handleMessage(msgContext); } I tried to do synchronized(this) at the beginning but it very quickly resulted in unstable AS behaviour and stopping JVM with a core dump in the end (SIC!). Since we are talking about serious production deployment in 5 days (servicing ca. 5000 SOAP requests per hour) , I decided to incorporate my fix into the environment, but I am not completely sure wheter my fix imposes any performance pitfalls. If you find a better idea to solve this problem, please be quick to publish a solution :) -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2074) Resource injection in WS Handler doesn't work

by Richard Opalka (JIRA)

Resource injection in WS Handler doesn't work --------------------------------------------- Key: JBWS-2074 URL: http://jira.jboss.com/jira/browse/JBWS-2074 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Richard Opalka Fix For: jbossws-native-2.0.5 -- 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

3
24
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2008