4 Replies Latest reply on Aug 1, 2006 9:34 AM by thomas.diesler

webservice runs on JBoss 4.0.3, throws exception on JBoss on

phlogistic Jun 14, 2006 2:50 PM

I have a web service that runs correctly on JBoss 4.0.3, but on JBoss 4.0.4 / JBossWS 1.0.1, throws a stack trace.

The web service's artifacts (port, service, etc.) are created using the wscompile tool of Sun's Java Web Services Developer Pack 1.6. The wscompile tool argument 'nodatabinding' is used as well. Message style endpoints & 'nodatabinding' are synonymous.

On JBoss 4.0.3, the web service functions as expected, without error.

On JBoss 4.0.4 / JBossWS 1.0.1, the web service throws the below exception & stack trace from JBossWS source code at container startup:

14:37:30,281 ERROR [MainDeployer] Could not create deployment: file:/C:/Java/jboss-4.0.4/server/default/deploy/MemberLoan.war
org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://www.somewhere.com/memberLoan}LoanDetailRequestType
 at org.jboss.ws.metadata.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:442)
 at org.jboss.ws.metadata.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:193)
 at org.jboss.ws.metadata.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:224)
 at org.jboss.ws.server.WebServiceDeployerJSE.createWebServicesMetaData(WebServiceDeployerJSE.java:189)
 at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:103)
 at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:66)
 at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
 at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy31.create(Unknown Source)
 at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
 at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy8.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:417)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy5.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
 at org.jboss.Main.boot(Main.java:200)
 at org.jboss.Main$1.run(Main.java:464)
 at java.lang.Thread.run(Thread.java:595)
14:37:30,359 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
14:37:30,671 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@cf823f9a { url=file:/C:/Java/jboss-4.0.4/server/default/deploy/MemberLoan.war }
 deployer: MBeanProxyExt[jboss.web:service=WebServer]
 status: Deployment FAILED reason: Cannot obtain java type mapping for: {http://www.somewhere.com/memberLoan}LoanDetailRequestType
 state: FAILED
 watch: file:/C:/Java/jboss-4.0.4/server/default/deploy/MemberLoan.war
 altDD: null
 lastDeployed: 1150310249593
 lastModified: 1150310249421
 mbeans:

Questions:

1. Does JBoss 4.0.4 / JBossWS 1.0.1 support the 'nodatabinding' option from Sun's wscompile tool?

2. If #1 is true, what need be done in order to make nodatabinding / message style endpoints function in JBoss 4.0.4 / JBossWS 1.0.1?

1. Re: webservice runs on JBoss 4.0.3, throws exception on JBos

phlogistic Jul 14, 2006 4:04 PM (in response to phlogistic)

Found out the answer - JBoss 4.0.4 / JBossWS 1.0.1 is NOT COMPLIANT, and DOES NOT SUPPORT the WS standard of 'nodatabinding'!!!
Actions
2. Re: webservice runs on JBoss 4.0.3, throws exception on JBos

heiko.braun Jul 17, 2006 4:23 PM (in response to phlogistic)

See http://labs.jboss.com/portal/jbossws/user-guide/en/html/getting-started.html#message-endpoints.

BTW, please don't yell in the forums.
Actions
3. Re: webservice runs on JBoss 4.0.3, throws exception on JBos

phlogistic Jul 24, 2006 4:22 PM (in response to phlogistic)

Heiko - thank you for the link. I did not see anything in the link to translate WSDL to Java using wstools for nodatabinding (message-endpoints). Additionally, using Java files generated from the Sun standard wscompile tool with no databinding will not run on JBoss 4.0.4 / JBossWS 1.0.1 - but it does run on JBoss 4.0.3. I hope the next stack of JBossWS supports this feature that was dropped until then I gotta find another container.
Actions
4. Re: webservice runs on JBoss 4.0.3, throws exception on JBos

thomas.diesler Aug 1, 2006 9:34 AM (in response to phlogistic)

Please monitor

http://jira.jboss.com/jira/browse/JBWS-1112

and attach a sample deployment + sources to the case
Actions

Go to original post