[JBossWS] - ClassLoader not available in meta data
by kc7bfi
I'm trying to deploy a web service in JBoss 4.0.4GA. When I start up JBoss, I get the following error:
org.jboss.ws.WSException: ClassLoader not available in meta data
| at org.jboss.ws.metadata.ServiceMetaData.eagerInitialize(ServiceMetaData.java:370)
| at org.jboss.ws.metadata.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:147)
| at org.jboss.ws.server.ServiceEndpoint.start(ServiceEndpoint.java:106)
| at org.jboss.ws.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:529)
| at org.jboss.ws.deployment.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:144)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:104)
|
Any idea what the problem might be? I have deployed other web services with out any problem. Thanks in advance,
David Robison
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002823#4002823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002823
19 years, 2 months
[JBossWS] - jbossws 1.0.4 kills my MBean
by Doug.Palmer
I guess something has changed that you weren't expecting to affect users. I have written a Deployer MBean that reads an xml file; builds a war file based on the xml file and then deploys the war file as a JSR109 web service. This MBean works with all previous versions of JBossWS from 1.0.0 to 1.0.3. Unfortunately, upgrading to JBossWS breaks the MBean.
When my MBean has built the new war file it calls:
| mainDeployer.deploy(new DeploymentInfo(warFile.toURL(), di, server));
|
mainDeployer is inherited from org.jboss.deployment.SubDeployerSupport.
warFile is a java.io.File created in the tempDeployDir (which is also inherited from org.jboss.deployment.SubDeployerSupport).
di is the DeploymentInfo passed by the main deployer to my MBeans create method.
server is the javax.management.MBeanServer inherited from org.jboss.system.ServiceMBeanSupport.
In all previous versions of JBossWS this would result in the war file being deployed as a web service by the appropriate deployer. However, in 1.0.4, the main deployer hands the war to the tomcat deployer and skips the web service deployment.
Does anyone know what has change to cause this problem? Is there a workaround that I can use?
Regards
Doug
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002730#4002730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002730
19 years, 2 months