Porting from JBoss to WebLogic
At work this week, I had to port our application from “JBoss 4.0.x”:http://labs.jboss.com/portal/jbossas to “WebLogic 9.2″:http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/products/weblogic. We had attempted to do a port from JBoss to the “Sun app server”:http://java.sun.com/javaee/downloads/index.jsp last year and met with total failure. Apparently, the Sun app server is incredibly picky about how certain parts of the J2EE specification is implemented, especially JMS. As a result of this, I expected the port to be fairly hard to do.
I was mostly wrong, which was a very nice surprise.
In total, I think I had to change 2 strings, 1 config file, and 1 class. The config file and the class were both related to “Hibernate”:http://www.hibernate.org. According to WebLogic, it is not possible to store the Hibernate SessionFactory in JNDI, it has to be cached locally in the HibernateUtil.java class. The 2 strings were related to calling WebLogic’s default JMS connection factory and remotely accessing an EJB from a stand alone client.
I personally found this to be very cool. It means that it is possible to develop a J2EE application and leave the decision of what app server to use until very near the end of development. It also means that you can develop one application and test deploy it to two servers.
