You have at least two choices:
1) Place the hibernate jars under the axis2 war WEB-INF/lib. Place all
your code under WEB-INF/lib or WEB-INF/classes . Use the aar only for
services.xml .
2) Get fancy with the AAR classloader. Place your hibernate jar under
the aar lib directory and keep your classes in the AAR too. We've
tested this with spring wrapping around the hibernate transactions. I
would imagine you could do something similar for a pure hibernate
solution but I personally haven't tested that.
There are some docs using the spring option with hibernate, and even
without spring some of the same concepts apply:
http://ws.apache.org/axis2/1_1_1/spring.html
HTH,
Robert
On 3/5/07, pat <[EMAIL PROTECTED]> wrote:
Hello,
I want to ask you about architecture of the application which uses hibernate
as DB handler, JSPs as front end and Axis2 as WS. All running on Tomcat web
container. What is the best practice to build this application?
E.g.:
if "build two separated application which will use the hibernate core from the
Tomcat's shared lib" or "take Axis2 WAR and push into it JSPs and hibernate
core" or ...?
Any ide?
Thanks a lot
Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
