Hello,
thank you for your answers
My previous post might be confusing.
We have several webapps (several virtual hosts) that share the same
ejbs. This is why we wanted to achieve this kind of packaging :
Project_EAR
-> project_EJB-JAR
-> project_1_WAR (www.website1.com)
-> project_2_WAR (www.we
Vincent LAUGIER wrote:
> What do you mean by "defining ejbs in resin-web.xml" ? Could this be a
> workaround to package the project in differents WARs (one WAR for the
> entity beans, another for the session beans...) ?
>
Many/most applications only need a single .war file. Packaging a single
> Hello Alex,
>
> then we are waiting for the resin 4 stable release (we need to stick to
> resin 3 for the moment because of problem with the persistence context
> injection, see http://forum.caucho.com/showthread.php?t=1927).
>
>
>> Resin supports the ear layout as well as defining ejbs in r
As a longtime J2EE developer, let me suggest that life is far more
pleasant if you abandon the atrocious EAR packaging morass and build
your applications in one or more WARs. Just put all your classes in
WEB-INF/classes (ejbs, servlets, etc), make sure you have
WEB-INF/classes/META-INF/beans.xml a
Hello Alex,
then we are waiting for the resin 4 stable release (we need to stick to
resin 3 for the moment because of problem with the persistence context
injection, see http://forum.caucho.com/showthread.php?t=1927).
> Resin supports the ear layout as well as defining ejbs in resin-web.xml
>
On 2009-11-16, at 8:09 AM, Vincent LAUGIER wrote:
> Hello,
>
> I am trying to package an EAR application in Resin.
>
> So far, I have achieved this kind of package : a WAR project embedded in
> a EAR project (specifying the 'ear-deploy' tag in the resin.conf).
>
> Project_EAR
> -> project_WAR
