-
2. Re: Conflicting libraries
magiccreative Mar 29, 2010 6:38 AM (in response to jaikiran)thanks for the immediate answer,
I have seen those wiki entries, unfortunatelly I do not understand them without examples .
Could you give me some pointers, how can I group the jars so that they are loaded sepparatelly.
Should I have
<code>
<loader-repository>
com.example:archive=unique-archive-name
</loader-repository>
</code>
for each jar configured to 2 different unique-archive-names?
thanks again
-
3. Re: Conflicting libraries
jaikiran Mar 29, 2010 6:46 AM (in response to magiccreative)How are you packaging your applications? Are those .war files or .ear files?
-
4. Re: Conflicting libraries
magiccreative Mar 29, 2010 7:28 AM (in response to jaikiran)-ear/lib
--jar1
--jar2
--war/web-inf/lib
most of the libraries go into ear/lib, exactly there come Resteasy and Axis 2 libraries which ends up with a conflict
-
5. Re: Conflicting libraries
magiccreative Mar 30, 2010 4:17 AM (in response to magiccreative)I have been reading jboss ucl documentation. As far as I understand I could have grouped the jars in two different loader repositories. The problem is those jars are from external libraries and their dependencies (resteasy and axis 2). So editing META-INF/jboss.xml and repackaging them is not much of an option.
Is there other way to group the libraries in different classloader repositories without editing the jars themselves. For example an externalized meta information file that would sepparate the libraries.