I wanted to know if there are any implications of deploying my application jar file in the server\default\lib directory as opposed to the deploy directory. I had to do this to be able to get my application to deploy properly when migrating from jboss3.0.0 to jboss3.2.1.
My application consists of one jar file only. Currently everything is jarred up in one jar file. The application consists of Session beans, entity beans, several MBeans and some plain java classes. I am deploying the MBeans by placing the corresponding xml files in the deploy directory.
When I had the jar file in the deploy directory, I started getting LinkageError and Duplicate class definition messages, on JBOSS 3.2.1. Everything worked fine on JBOSS3.0.0.
So to get the application to deploy properly in JBOSS3.2.1 I did the following:
1) Put MBean related xml files in the deploy directory
2) Put application specific jar file in the server\default\lib directory.
Please let me know if there are any implications of doing such a deployment in JBOSS3.2.1. I did not see this problem in JBOSS3.0.0.
Thanks for your help.