*
The moose likes JBoss/WildFly and the fly likes Migration of jboss 4.0.0 to 5.0.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Migration of jboss 4.0.0 to 5.0.1" Watch "Migration of jboss 4.0.0 to 5.0.1" New topic
Author

Migration of jboss 4.0.0 to 5.0.1

sarvan kumar
Ranch Hand

Joined: Jul 28, 2010
Posts: 66
Hi,
How to migrate jboss 4.0.0 to jboss 5.0.1 can anyone explain

Thanks,
K.Saravanan
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5811
    
    7

Here are some guidelines.

Use 5.1.0.GA, do not use 5.0.1.GA.

If you have made any changes to the JBoss AS configuration files, you will have to track down the exact changes you made. You did place the config files under version control so that you could track this, right? If not, download the exact same version of JBoss AS you are using and use a diff utility to tell you what you changed. For each change that you made, you need to determine how to make a similar change in 5.1.0. This usually means reading up about how 5.1.0 is configured. The biggest issue you will run into here is that many of the services that were configured using MBeans are now configured using POJOs in the microcontainer.

Any *-ds.xml files you have will probably work as-is in 5.1.0. There were no significant changes to *-ds.xml files. Unless you have declared various MBeans within them, in which case see the prior paragraph.

If you use messaging, you need to change how your destinations are declared. Look at the examples in docs/examples/jms/example-destinations-service.xml.

If you have any web services, you will need to regenerate the stubs and recompile the web service server and client code.

For your app itself, recompile it with the JARs from 5.1.0 and then deploy it and see what errors you get and then track them down and fix them.

If you have standalone apps, they will have to be recompiled with the JARs in the 5.1.0 client directory.

I probably forgot something, but for most apps this should be reasonably complete.


JBoss In Action
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Migration of jboss 4.0.0 to 5.0.1
 
Similar Threads
whats wrong with this client ?
Jboss clustering
Jboss - Axis2 - Log4j : log4j.properties file placement
JBoss 4.0.0
Jboss deployment error - help for a beginner