1 Reply Latest reply on Feb 13, 2012 2:29 AM by Evelthon Patrickios

    EJB3 with a client using JVM 1.4 -- what are the risks?

    Evelthon Patrickios Newbie

      We have session EJBs implemented as EJB3, running on JBoss AS 4.2.1.GA

      Our client has to reside on Oracle 10g database, where the jvm is of version 1.4.2 (and this CANNOT change).
      [This is ONLY the client that will call the EJB3 -- The serrver will run on jvm 1.5 or higher]

      I have seen some posts, etc, saying the EJB3 and jvm 1.4 is not officially supported -- fair enough.

      We have managed to make the thing to work, [by translating the jbossall-client.jar] however, using the Retrotranslator tool [http://retrotranslator.sourceforge.net/]
      I saw from another post that someone used used JBossRetro (http://labs.jboss.com/jbossretro/ ) -- a tool for a similar purpose.

      My concern is that even if this works on a test environment, what are the potential problems/drawbacks if to implement it on a site?
      Why is it NOT a recommended approach, if so?
      Do these translator tools impose any risks, or should they be considered once the thing works?

      Also if someone has a preference of Jboss-Retro vs Restrotranslator and why.