0 Replies Latest reply on Mar 28, 2013 11:52 PM by LosLobo

    Reality, J2EE and WebLogic versus JBOSS - Long Term Value

      I'm currently on a project where we are using an older version of JBOSS 4 from about 8 years ago and recently given the task to upgrade it to the latest version. When I discovered all the myriad details necessary to update the code base, it made me question whether java is even an ideal programming environment.
      Here's a short list of necessary upgrades.
      JMS - originally written in JBOSS proprietary JBossMQ, no longer supported must be rewritten in HornetQ.
      Web Services - originally JAX-RPC, no longer supported need new WS conventions
      EBJ 2.0 - no longer supported, rewrite to EBJ3
      JNDI - to EJB3
      XML files - a bazillion to port both JBOSS proprietary and EJB3, etc., etc.
      When going over this list it represented a very large significant effort that could last a year.
      I found it so frustrating that there wasn't a straightforward migration method, I came to the conclusion that the best method is to get up and running on the new server with the code as it should be represented(WS, EJB3, Messaging) then try to port all the old crap.

      If my recollection is right, I remember Weblogic being much more forgiving, or is it?
      This project has kind of crushed my rah rah feelings about java being an ideal long haul programming environment when you nearly have to scrap and rewrite your code after only 8 years because of the myriad J2EE changes! Makes me wonder if we wouldn't have better value on something cheap and simply like PHP.
      Please weigh in. : )