Configuring Jetty 7 standalone for JNDI

Configuring Jetty 7 for JNDI can be a bit tricky. If you miss any of these points, you may end up passing JNDI parameters, but they will not be available in your webapp.

1. Ensure the plus libraries are loaded. You can to this by adding the option plus in Jetty's start.ini
2. Ensure jetty is configured to use the plus configuration classes. You can do this by adding the following inside the context, or the jetty-env.xml:

   ---

     <Set name="ConfigurationClasses">
       <Array id="plusConfig" type="java.lang.String">
         <Item>org.eclipse.jetty.webapp.WebInfConfiguration</Item>
         <Item>org.eclipse.jetty.webapp.WebXmlConfiguration</Item>
         <Item>org.eclipse.jetty.webapp.MetaInfConfiguration</Item>
         <Item>org.eclipse.jetty.webapp.FragmentConfiguration</Item>
         <Item>org.eclipse.jetty.plus.webapp.EnvConfiguration</Item>
         <Item>org.eclipse.jetty.plus.webapp.Configuration</Item>
         <Item>org.eclipse.jetty.webapp.JettyWebXmlConfiguration</Item>
         <Item>org.eclipse.jetty.webapp.TagLibConfiguration</Item>
       </Array>
     </Set>
   

   ---

   The documentation suggests adding etc/jetty-plus.xml to the startup, which would make this configuration available as plusConfig to refer to. This did not work on my machine.

You can now continue with Passing parameters to Jetty 7 via JNDI.