It�s in. Could you please check that it works now (at least the part of the testsuite that does not depend On DefaultDS to be bound, there seems to be something broken with JCA right now).
CGJ -----Urspr�ngliche Nachricht----- Von: Martin Maisey [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 8. April 2002 00:32 An: [EMAIL PROTECTED] Betreff: [JBoss-dev] JBoss.net class not found and deployer registration problems Christoph/whoever, I have been trying to get JBoss.net up and running to have a play about with, and have hit a few problems. Before going too much further, I just wanted to check that I'm not doing something stupid, as I'm a relative novice with both JBoss and Axis. I'm using the head revision of jboss-all from earlier this evening, with Sun JDK 1.3.1-b24 on SuSE Linux w/ hotspot client VM in mixed mode. I built using "./build.sh all", then "./build.sh -Dgroups=optional". Firstly, I got a NoClassDefFoundError trying on starting JBoss.net trying to find some of the techtrader classes. I temporarily fixed this by copying thirdparty/techtrader/lib/tt-bytecode.jar to build/output/jboss-3.0.0beta2/lib, but it should really be fixed in the jboss.net build.xml as far as I can see (looks simple enough, I will submit a patch if someone can integrate it for me). This got rid of the initial error, but I now get an exception as follows: 21:50:09,318 ERROR [AxisService] Could not register with MainDeployer ReflectionException: Exception when calling method for 'addDeployer(,org.jboss.deployment.SubDeployer)' Cause: java.lang.IllegalArgumentException: argument type mismatch at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:312) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.net.axis.server.AxisService.startService(AxisService.java:329) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:805) at $Proxy1.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:309) at org.jboss.system.ServiceController.start(ServiceController.java:327) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:278) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:672) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:517) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:480) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:329) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymen tScanner.java:516) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:389) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract DeploymentScanner.java:237) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:805) at $Proxy1.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:309) at org.jboss.system.ServiceController.start(ServiceController.java:327) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:213) at org.jboss.Main.boot(Main.java:138) at org.jboss.Main$1.run(Main.java:371) at java.lang.Thread.run(Thread.java:484) I had a quick look and it appears that AxisService is attempting to register itself with the main deployer, but doesn't seem to implement the SubDeployer interface, instead implementing (via AxisServiceMBean) SubDeployerMBean from the server project. From a cursory glance, it looks like it should probably extend SubDeployerSupport instead of ServiceMBeanSupport, but there appear to be 2 slightly different versions of this in server and in system, so I'm confused! My questions are: - is this meant to work at the moment or is it in flux? - is there a quick fix to get things going? - is anyone else working on/looking at fixing this? - is there anything I can do to help? Thanks, Martin Maisey _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
