Jetty is not a Java EE product, that's why it doesn't work as you would
expect it to.
Werner Keil wrote on 06/18/11 12:16 AM:
> Thanks Bill.
> I just got a concern by one of our Test Automation guys the other day who wanted
> to use Jetty instead of WebLogic in one of several "test" stages. And he said,
> JNDI works totally different there than on WebLogic which represents our
> "production" stage.
>
> So it looks like always present it isn't used in such a unified way that you can
> just switch from one environment to the other without special precautions.
>
> On Sat, Jun 18, 2011 at 12:34 PM, Bill Shannon <bill.shannon_at_oracle.com
> <mailto:bill.shannon_at_oracle.com>> wrote:
>
> Werner Keil wrote on 06/17/2011 11:55 PM:
>
> I don't know, if JNDI can be assumed to be available in every stage
>
>
> JNDI is there in every Java EE product, "stage" shouldn't change that.
>
>