Upgrade to JBoss 5.0.0Beta4

[arulasha]

Presently we are using JBoss 4.2 and want to evaluate JBoss 5.0.0Beta

It seems to me there are lot of changes interms of xml file placements and found some files were missing ( Example : cluster-service.xml, ear-deployer.xml ). This makes me difficult map the 4.2 configurations to 5.0.

I am also finding difficulty in configuring EJB and JMS and could not find specific custom configuration documents for JBoss 5.0.0 .

After trying lot , here is the last error I got from server log

*** CONTEXTS IN ERROR: Name -> Error

jboss.messaging:service=SecurityStore -> ** NOT FOUND **

jboss.jca:name=InMemoryDS,service=DataSourceBinding -> ** NOT FOUND **

Any help is appreciated.

Thanks
Arul Kumar

[peterj]

The necessary files to configure JBoss Messaging to use other databases are not present in JBoss 5.0.0.Beta4, you will need to download JBoss Messaging 1.4.1.beta1, it has the necessary files.

I have some resources on 5.0, but they are not free. I can provide a URL if you are interested.

[arulasha]

No Thanks

I have resolved issues by modifying the jms configurations.

Again I got couples of issues related to ClassNotFoundExeception.

Here are Exceptions
WSServerConfig -> java.lang.ClassNotFoundException: org.jboss.wsf.common.management.AbstractServerConfigMBean

vfsfile:/D:/Projects/JBoss5/SVN/jboss/server/lms1/deploy/jsr88-service.xml -> java.lang.ClassNotFoundException: org.jboss.ejb3.Ejb3Deployment

WSMemoryBufferRecorder -> java.lang.ClassNotFoundException: org.jboss.wsf.framework.management.recording.MemoryBufferRecorder

WSNativeDeploymentAspectInstallerEJB -> java.lang.ClassNotFoundException: org.jboss.wsf.framework.deployment.DeploymentAspectInstaller

WSNativeDeploymentAspectInstallerEndpointAPI -> java.lang.ClassNotFoundException: org.jboss.wsf.framework.deployment.DeploymentAspectInstaller

WSEndpointRegistry -> java.lang.ClassNotFoundException: org.jboss.wsf.framework.management.ManagedEndpointRegistry


It seems to me the jars inside deployer directories are not in classpath.

Should we need to explicitly set the class path to those jars ?