Server Migration from JBoss-4.0.5 to JBoss-4.2.3.GA
As the subject line says, this write-up covers a small note on JBoss Server migration. Hopefully it may not be a tough task migrating from JBoss-4.0.5 to JBoss-4.2.3 server, but I rather had a different experience while doing this. The reason behind this was the pre-compilation of the JSPs* in my project, which was performed using the jar files present in jbossweb-tomcat55.sar folder.
* If I say compile/compiling in this write-up, please read it as ‘pre-compiling JSPs’
I was supposed to do the same compiling as it was done earlier when we used JBoss-4.0.5. The jar files used to compile are jasper-compiler.jar, jasper-runtime.jar, commons-el.jar and as I said earlier these files resided in the jbossweb-tomcat55.sar folder. Now where can I find jbossweb-tomcat55.sar folder in JBoss-4.2.3.?
After some time, with the help of google, I was able to find out that this directory is been replaced by a new Tomcat servlet engine which is been named as jboss-web.deployer. This resides in JBoss-4.2.3.GA/ server/default/deploy/ folder.
Well I got the folder which is an alternative for jbossweb-tomcat55.sar, but the jar files present in jboss-web.deployer [jbossweb.jar,jasper-jdt.jar,jstl.jar] didn’t help me in making a successful compilation . I used to get one or the other build error. I posted the same in JBoss Forums, unfortunately I was pressed for time that I was unable to work on the suggestions given to me by the JBoss Community.
I believe in completing things accurately rather than a quick finish. But probably that doesn’t work always.
All that I was able to do that day was to copy the 3 jar files jasper-compiler.jar, jasper-runtime.jar, commons-el.jar present in JBoss-4.0.5 into my project as third part libraries and compile my JSPs. Then copy the resulting war file into JBoss-4.2.3. I added the path of these three jar files in my ant buld.xml file with a comment to future developers of my project, saying that , use a better way to compile, as it may not make sense compiling JSPs using 4.0.5 JBoss jars and adding the resulting war file into JBoss-4.2.3 server.
5 months down the line, “ALL izz Well ” so far and No issues are been reported yet. So I thought of sharing this here in my blog, though I still believe I would have used a better way for my JSP compilation.
There are few more changes that I noticed while migrating, but I hardly remember those things now.as of today my brain remembers only the following things, ….
javax.servlet.jar in 4.0.5 is changed to servlet-api.jar in JBoss-4.2.3
javax.servlet.jsp.jar in 4.0.5 is changed to jsp-api.jar in JBoss-4.2.3
log4j.xml in 4.0.5 is changed to jboss-log4j.xml in JBoss-4.2.3
If I start working on JBoss again or if I remember something, that I had done earlier, sure I will be updating this write-up.
* If I say compile/compiling in this write-up, please read it as ‘pre-compiling JSPs’
I was supposed to do the same compiling as it was done earlier when we used JBoss-4.0.5. The jar files used to compile are jasper-compiler.jar, jasper-runtime.jar, commons-el.jar and as I said earlier these files resided in the jbossweb-tomcat55.sar folder. Now where can I find jbossweb-tomcat55.sar folder in JBoss-4.2.3.?
After some time, with the help of google, I was able to find out that this directory is been replaced by a new Tomcat servlet engine which is been named as jboss-web.deployer. This resides in JBoss-4.2.3.GA/ server/default
Well I got the folder which is an alternative for jbossweb-tomcat55.sar, but the jar files present in jboss-web.deployer [jbossweb.jar,jasper-jdt.jar,jstl.jar] didn’t help me in making a successful compilation . I used to get one or the other build error. I posted the same in JBoss Forums, unfortunately I was pressed for time that I was unable to work on the suggestions given to me by the JBoss Community.
I believe in completing things accurately rather than a quick finish. But probably that doesn’t work always.
All that I was able to do that day was to copy the 3 jar files jasper-compiler.jar, jasper-runtime.jar, commons-el.jar present in JBoss-4.0.5 into my project as third part libraries and compile my JSPs. Then copy the resulting war file into JBoss-4.2.3. I added the path of these three jar files in my ant buld.xml file with a comment to future developers of my project, saying that , use a better way to compile, as it may not make sense compiling JSPs using 4.0.5 JBoss jars and adding the resulting war file into JBoss-4.2.3 server.
There are few more changes that I noticed while migrating, but I hardly remember those things now.
javax.servlet.jar in 4.0.5 is changed to servlet-api.jar in JBoss-4.2.3
javax.servlet.jsp.jar in 4.0.5 is changed to jsp-api.jar in JBoss-4.2.3
log4j.xml in 4.0.5 is changed to jboss-log4j.xml in JBoss-4.2.3
If I start working on JBoss again or if I remember something, that I had done earlier, sure I will be updating this write-up.
It is very useful information about JBoss for all and it is very simple to understand. Thanks for sharing it.
ReplyDeleteJBPM developers who are proficient in this domain can provide you with such services and benefit you a lot.