Hi,
an easy way to test it is to include tomee in your war (i think the easiest
is to do an overlay of tomee war) and declare in your web.xml:
<servlet>
<servlet-name>LoaderServlet</servlet-name>
<servlet-class>org.apache.tomee.loader.LoaderServlet</servlet-class>
</servlet>
btw this was an old solution, i didn't check it recently
the drop in war approach alone you'll hit startup order issues, if you can
add the OpenEJBListener in server.xml it is pretty much the same as a
default tomee.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/8/6 Bernard <[email protected]>
> Hi,
>
> Can TomEE provide JavaEE functionality without the modification of the
> server as described at
>
> http://tomee.apache.org/installation-drop-in-war.html ?
>
> The old OpenEJB document at
>
> http://openejb.codehaus.org/tomcat.html
>
> describes this as follows:
>
> "OpenEJB per webapp - deployed EJBs are visible only to the web apps
> that declared to load OpenEJB"
>
> I would be useful for me because my production environment has high
> resistance to any changes of the server environment which cannot be
> justified for my EJB3 web application alone.
>
> My EJBs don't need to be visible to other applications.
>
> Otherwise, if this is not possible, where can I learn about the impact
> and risks of the standard drop-in .war approach?
>
> Many thanks
>
> Bernard
>
