Re: [jboss-as7-dev] deploying a war - jboss-classloading.xml
On Wed, Apr 13, 2011 at 8:59 PM, Jason T. Greene wrote:
On 4/13/11 9:40 PM, denstar wrote:
...
> At any rate, it's basically the same list of jars I have to
delete
> now, that I had to delete when I first got things going with AS5
> (before I found out about jboss-classloading.xml). I'm pretty sure
> AS6 worked like 5 as far as having jboss-classloading.xml work it's
> magic.
:6,8 s/it's/its
What was likely happening is that the default domain was preferring
the JDK
API classes from the JVM vs the ones in your war. WARs are effectively child
first so if you include JDK API classes, they will be proffered to the JVM,
which will lead to clashes.
For this reason, in the past we filtered some (but not all API classes) to
prevent the common error. In 7 we have been planning to automatically filter
all spec classes by default. Although there are legitimate cases to not
filter (e.g. a war includes its own NEWER version of JSF). Although at the
moment we don't filter anything.
Cool. I looked at the ticket, and it seems like a Good Idea. I think
I mostly understand what's going on.
Thanks for the info guys! I'll roll with this for now, feeling all
warm and fuzzy knowing y'all are on the job.
:Den*
--
The Bible is literature, not dogma.
George Santayana