Re[4]: xmlc and tomcat4.1.1.12 compatibility problem

Hello David,

Sure, it's fine to put xmlc, jtidy, and gnu-regexp in WEB-INF/lib
because no outside library in a parent classloader requires access to
them.  Parent classloaders can't see jars in WEB-INF/lib but the child
classloaders can see the parent classloaders (other than server/lib).

I put those jars all in shared/lib because all my xmlc apps use those
jars so why not just share the wealth?

You are right that putting xerces in common/endorsed will be the
absolute safest option, but I've not seen any problems putting it in
shared/lib.  Let me know what comes of your discussion with Richard.

Jake

Monday, November 25, 2002, 2:27:15 PM, you wrote:

DL> I can't find that in source but I will check with Richard.

DL> Regarding to this, XMLC actually works for me with Tomcat by putting 
DL> all the jar in WEB-INF/lib.

DL> I think this has to do with the loading order with the Tomcat's class 
DL> loader hierarchy. I discovered the problem when trying to get deferred 
DL> parsing to pass all the unit tests. Just as a precaution, it's best to 
DL> put the xerces.jar from XMLC in the common/endorsed and make sure the 
DL> DOM interface from it is used by the system.

DL> On Tuesday, Nov 26, 2002, at 03:08 Asia/Shanghai, Jacob Kjome wrote:

>> Hello David,
>>
>> Yes, but I believe that Richard accounted for this (search the
>> archives) which is why it
>> works in shared/lib even with Xerces-2.x.x in common/endorsed.
>>
>> Works for me completely.  You should ask Richard about this.  I think
>> he uses reflection to determine what is supported.
>>
>> Jake

DL> _______________________________________________
DL> XMLC mailing list
DL> XMLC@xxxxxxxxxxx
DL> http://www.enhydra.org/mailman/listinfo.cgi/xmlc



-- 
Best regards,
 Jacob                            mailto:hoju@xxxxxxxx