0 Replies Latest reply on Aug 28, 2003 4:26 AM by jwijgerd

    Jetty JNDI change between 3.2.2RC1 and 3.2.2RC2/3

    jwijgerd

      What gives?

      my deployments that call beans from servlets (using direct jndi lookup) appears to have stopped working for jetty in the RC2 and RC3 releases.. My beans work fine (this is actually running on 3.2.1 in a production environment).

      This fact, and the fact that tomcat is now the default container added to the fact that some of the core jetty developers moved to coredevelopers.net makes me wonder if this is a political move..

      Anyways, if anybody could help me on this i would highly appreciate it..

      cheers,

      Joost