my way have been to bundle all in an EAR
containing the war, the ejb jar,
the tools library jar (tidy in my case),
the application.xml
I've added a class-path directive in the manifest of the EJB jar (not the
EAR it does not works)
Created-By: ${ant.project.name}
Class-Path: . Tidy.jar
but note that the Tidy.jar is stored in the .ear archive (not the ejb jar!)
note also that I've included the client EJB jar (interfaces, passed by value
objects, exceptions)
in the WEB-INF/lib/ in the .war archive...
this way seems quite clean to me... I've found no better way ...
Am I right ?
> -----Message d'origine-----
> De: Tim Sheridan [mailto:[EMAIL PROTECTED]]
> Date: mardi 15 janvier 2002 22:45
> �: '[EMAIL PROTECTED]'
> Objet: [JBoss-user] JBoss Deployment Strategy
>
>
> Where is an appropriate place to put shared or common code
> (in the form of
> JAR files) that are utilized by session/entity/message beans in JBoss?
>
> Should I deploy all business objects and supporting code in the
> <JBOSS_HOME>/deploy folder or just business logic beans?
>
> What's the best strategy?
>
> Thanks,
> Tim Sheridan
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
