Thanks jaikiran.
This is helpful documentation.
However, it doesn't appear to fully explain my situation. My situation is
basically that which is labelled "Case 2":
Case 2. The Utility.class is present both in the application's archive AND
server/default/lib. The deployment is non-scoped.
The short story: The version of the class available in
server/default/lib/utility.jar will be used by the new deployment. The version
of the class packed with the deployment will be ignored.
That is in fact what is happening. But the result of this loading is that I
get an IncompatibleClassChangeError.
Now, my situation possibly differs from case 2 in one respect. My deployment
archive is a WAR file, not an application (ear) file. The document goes on to
list WAR file deployment as a TODO.
I am thinking I could possibly solve this by using scoped class loading. Is
that what you are thinking?
If so, would this be the correct syntax?
<jboss-web>
<class-loading>
<loader-repository>
org.apache.commons.httpclient:loader=my.war
</loader-repository>
</class-loading>
</jboss-web>
In this example "my.war" is the war file for which this fragment is the jboss
descriptor. If this is not correct, what is the correct way to do this?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897734#3897734
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897734
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
