5 Replies Latest reply on Jan 19, 2011 8:01 PM by honeychen03

Is there a method to use ear's jars which have conflict with those in JBoss itself?

honeychen03 Jan 18, 2011 3:39 AM

I am using JBoss 6.0 final version, and I found there are a lot of conflict errors from the jars between my ear's project and JBoss itself.

Such as hibernate jars and xml parser jars. What I am asking to confirm is if we can disable these jars from JBoss itself and just use them from my ear's project?

Thanks in advance for your suggestions.

1. Is there a method to use ear's jars which have conflict with those in JBoss itself?

wdfink Jan 18, 2011 5:26 AM (in response to honeychen03)

You should configure the classloading, good starting points to understand
JBoss class loading from the Wiki pages
http://community.jboss.org/docs/DOC-9289
http://community.jboss.org/docs/DOC-9288
http://community.jboss.org/docs/DOC-10290
Actions
2. Re: Is there a method to use ear's jars which have conflict with those in JBoss itself?

honeychen03 Jan 18, 2011 10:10 PM (in response to wdfink)

Thanks for your reply, wolf. But I tried some configuration and it did not work. Can you suggest?

My ear directory:
    -- cxe-ejb.jar
         -- META-INF
              -- ejb-jar.xml (configured the MDB)
              -- jboss.xml (configured the MDB)
              -- MANIFEST.MF
    -- globalsight-web.war
          -- WEB-INF
             -- classes
             -- lib
              -- web.xml
              -- jboss-web.xml
    -- lib (put all the jars for my ear project)
     -- META-INF
        -- application.xml (configured the cxe-ejb.jar module and globalsight-web.war module - web - web-uri)
         -- jboss-app.xml

I configured the jboss-app.xml and jboss-web.xml for the class loading but it seems no luck.
jboss-app.xml:
<jboss-app>
    <loader-repository>
        com.example:loader=globalsight.ear
        <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
</jboss-app>

jboss-web.xml:
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
         com.example:loader=globalsight-web.war
         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
      </loader-repository>
</class-loading>
</jboss-web>

Still conflict errors reported. The first conflict error is
java.lang.ClassCastException: org.hibernate.hql.ast.HqlToken cannot be cast to antlr.Token.

Any suggestion on any further configuration or is there anything I did wrongly?
Actions
3. Is there a method to use ear's jars which have conflict with those in JBoss itself?

wdfink Jan 19, 2011 2:18 AM (in response to honeychen03)

The classcast exception look for me like a hard cast from an interface to an implementation which has changed.
For web-app I avoid explicit class-loading (standard is that web app prefer the own classes)
Actions
4. Is there a method to use ear's jars which have conflict with those in JBoss itself?

honeychen03 Jan 19, 2011 2:29 AM (in response to wdfink)

But the problem is I donot have such error in JBoss 4.0.3 version. Thoughts?
Actions
5. Is there a method to use ear's jars which have conflict with those in JBoss itself?

honeychen03 Jan 19, 2011 8:01 PM (in response to honeychen03)

No more comments? Does that mean JBoss 6 can not avoid such jar conflict errors for the jar version difference? Or is there any other place that can be configured to resolve this problem?
Actions

Go to original post