Comments are inline.
Our default optimization of ejb calls through the remote interface
is not working with the servlet 2.3 container class loading model
[...]
We can deal with this by either
1. ignore the servlet 2.3 class loading model, which is what
Jetty does by default
Sounds good,
Our default optimization of ejb calls through the remote interface
is not working with the servlet 2.3 container class loading model
that advocates:
servlet-2.3-spec
SRV.9.7.2 Web Application Classloader
The classloader that a container uses to load a servlet in a WAR must allow
the
developer to
