Ok I figured out a way to make it all work ...
The solution ended up being to put all the commons jar files in the root of
the ear, and add them to application.xml as java modules. Looks like it was
indeed a classloader issue then ... which would lead me to think that this
is a bug. No reason why
oops ...
I'm running the Struts 1.1 binary release on jboss-3.2.1_tomcat-4.1.24 and
the war file resides in an ear file. I've tried sticking jars in the ear's
root and referencing them from the war file's manifest, but this gave
exactly the same results.
cheers
Rob
-Original Message-
2 matches
Mail list logo
