Thanks, btw I tried to remove hibernate-validator.jar from common/lib to see my app correctly deployed...at least it starts but there's one more issue. My Jboss distribution is bundled inside Liferay CMS; I can't touch common/lib anymore and my web app is using Struts 1.3. Integrating into a liferay portlet Struts is no more recognized obtaining a 500 error and this stack trace:
javax.servlet.ServletException: Cannot find catalog 'struts'
I suspect for this error I should check liferay community even if I'm using the classloading descriptor above to give precedence to my web-inf/lib.
It's a real nightmare!
Thanks for your help
1 of 1 people found this helpful
even if I'm using the classloading descriptor above to give precedence to my web-inf/lib.
Servlet spec already forces precedence of .war resources.
What you're seeing is that integration code gets mingled with app's resources,
which is, as you can read, a hard problem to avoid.
Btw the exception above is due to a load-on-startup tag inside the web.xml. Jboss does not like the give priority; removing this tag the deploy runs fine. It maybe caused by several servlet loaded by Struts and Birt together in the same application. If you don't have special needs, best practice is to not specify load-on-startup, leaving the loading order to the servlet container. Hope I'm right.
Thanks for your help.
Jboss does not like the give priority; removing this tag the deploy runs fine.
Hmm, I doubt that's the issue.
Afaik, this is per spec, hence order def should be allowed.
e.g. JBoss is not GAE where you wanna have all lazy behavior :-)