August 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Publishing my own wsdl which imports an xsd file.

by john.franklin

I am using jboss 4.2.1 and jbossws 2.0.0 I am trying to publish the wsdl I have created by setting the wsdLocation correctly in the @WebService implementation file of the web service. The wsdl and the xsd files are located in the META-INF directory in the war file. It located the wsdl file, but cannot locate the xsd file which is in the same place. However JBoss throws an exception and fails to deploy. Is this a bug or am I doing something wrong? 2007-08-24 07:35:39,200 ERROR [ServiceEndpointDeployer] Cannot start service endpoint | org.jboss.ws.WSException: Cannot publish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappsccv1.war/Syna | ppsSessionService.wsdl | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:126) | at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:134) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy47.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor19.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 $Proxy10.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/SynappsSession.xsd | at org.jboss.ws.integration.ResourceLoaderAdapter.findChild(ResourceLoaderAdapter.java:105) | at org.jboss.ws.core.server.UnifiedDeploymentInfo.getMetaDataFileURL(UnifiedDeploymentInfo.java:106) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:202) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) | ... 31 more | 2007-08-24 07:35:39,207 ERROR [MainDeployer] Could not start deployment: file:/opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/de | ploy/synappsccv1.war | org.jboss.deployment.DeploymentException: Cannot start service endpoint; - nested throwable: (org.jboss.ws.WSException: Cannot pu | blish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappsccv1.war/SynappsSessionService.wsdl) | at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:101) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy47.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor19.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 $Proxy10.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: org.jboss.ws.WSException: Cannot publish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappscc | v1.war/SynappsSessionService.wsdl | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:126) | at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:134) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) | ... 28 more | Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/SynappsSession.xsd | at org.jboss.ws.integration.ResourceLoaderAdapter.findChild(ResourceLoaderAdapter.java:105) | at org.jboss.ws.core.server.UnifiedDeploymentInfo.getMetaDataFileURL(UnifiedDeploymentInfo.java:106) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:202) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) | ... 31 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077860#4077860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077860

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Is there a workaround for the UsernameToken security hea

by kimbaltrue

Thanks this helped though I did have to do a lot of snooping in the deploy directory. Apparently, all I had to do was add the following annotation: @EndpointConfig(configName="Standard WSSecurity Endpoint") The endpoint configuration file already exists in the webservices sar directory under deploy. Since the file and entry exist, all you need is the endpoint config statement with the name of the config. The next problem I have to solve has to do with this being JBoss specific rather than JEE 5. The JEE 5 has a @Handler annotation that should be used instead of the EndpointConfig annontation, but I haven't figured out how to work with that yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077795#4077795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077795

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by M_schumpa

you can see which version of JBossWS is loaded at startup of JBoss. I should look something like this: INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756) That's the message from JBoss-4.2.0.GA/ distribution, so I think you are also using this one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077760#4077760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077760

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by thomas.diesler＠jboss.com

please try jbossws-2.0.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077758#4077758 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077758

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Null pointer exception with jbossws 2.0.1

by thomas.diesler＠jboss.com

test mail threading from forum posts View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077756#4077756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077756

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by vashistvishal

Hi Thomas, Thanks for replying. I'm not sure what version JBossWS it is. I'm using JBoss-4.2.0.GA/ distribution, what version is shipped with it is not clear to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077720#4077720 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077720

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by ambika

Hi, I wanted to know whether i can run MedRec application (which is built with to jboss ws4ee) in this New version of the apps server? Previously there was a disscusion about the same with jboss version 4.0.5.GA. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97276 Regards, Ambika View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077717#4077717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077717

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by thomas.diesler＠jboss.com

Please talk to http://www.jboss.com/services/index View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077700#4077700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077700

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by mdaguete

"thomas.diesler(a)jboss.com" wrote : The manifest classpath is not the problem becasue the unified classloader can see/load the ServerConfigFactory | | The implementation of that factory however tries to load the ServerConfig from the microkernel with the bean name: WSServerConfig | | Is that bean there? | There are no WSServerConfig bean in the jmx-console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077686#4077686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077686

17 years, 4 months

1
0
0 / 0

[JBossWS] - Re: JBossAS_4.0.5 does not clean up the temp files

by BossDenny

Yes, passivate file are not deleted by server!!!....and I have an exception when PostActivate metod occur on an ejb3 with PersistentContext(EXTENDED) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077683#4077683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077683

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users August 2007