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_1_WAR (www.website1.com)
-> project_2_WAR (www.website2.com)
Also, we want to avoid Hessian because we want to access the ejbs with
some simple imports/injections.
My idea of using a WAR as an EJB3-JAR was coming from the fact that WAR
and EJB3-JAR are quite similar but as Jeff says
classes in a WAR are out of scope for other WARs. Not a good idea then.
So in the end we will make some WARs directly deployed in the webapps
dir (not in a EAR) and tune the ant script so that the same ejbs are put
in the WAR at deployment.
Looking forward resin 4 !
Email : vincent.laug...@helmet.fr
Téléphone : 01 75 43 92 52
Fax : 01 79 75 01 12 (www.monfax.com)
Scott Ferguson a écrit :
> 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
> ..war file in an .ear just to get EJB support is silly. The JavaEE 6
> specs have finally caught up to this concept.
> I have no idea why you would want to package your session beans in a
> different .war file from the rest of your application.
> -- Scott
>>> This is only available in Resin 4. I don't believe there is a separate
>>> example, however there is a detailed draft of spec published on the blog:
>>> resin-interest mailing list
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list