I can appreciate that, Anil. Speaking of stack traces... Using a default jboss configuration, I have an issue currently that a web service which we used before (JBoss 4.0.1sp1) will now puke an exception as follows:
| org.jboss.axis.ConfigurationException: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.webservice.client.ClientLoginHandler | java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.webservice.client.ClientLoginHandler | at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:292) | at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:475) | at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:377) | at java.lang.ClassLoader.loadClass(ClassLoader.java:235) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:141) | at org.jboss.axis.utils.ClassUtils$2.run(ClassUtils.java:216) | at java.security.AccessController.doPrivileged(Native Method) | at org.jboss.axis.utils.ClassUtils.loadClass(ClassUtils.java:179) | at org.jboss.axis.utils.ClassUtils.forName(ClassUtils.java:120) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:418) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:347) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:322) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:307) | at org.jboss.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:167) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:322) | at org.jboss.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:307) | at org.jboss.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:583) | at org.jboss.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:326) | at org.jboss.axis.AxisEngine.getGlobalRequest(AxisEngine.java:291) | at org.jboss.axis.client.AxisClient.invoke(AxisClient.java:175) | at org.jboss.axis.client.Call.invokeEngine(Call.java:3054) | at org.jboss.axis.client.Call.invoke(Call.java:3039) | at org.jboss.axis.client.Call.invoke(Call.java:2629) | at org.jboss.axis.client.Call.invoke(Call.java:2538) | at org.jboss.axis.client.Call.invokeInternal(Call.java:1976) | at org.jboss.axis.client.Call.invoke(Call.java:1914) | I see in jboss-ws4ee.sar/META-INF/axis-client-config.xml the following handler definition <handler name="ClientLoginHandler" type="java:org.jboss.webservice.handler.ClientLoginHandler"/> What is trying to call org.jboss.webservice.client.ClientLoginHandler? I can't find this class anywhere, so I'm not surprised that there's a ClassLoader error. Any help? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877713#3877713 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877713 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
