Re: [ebxmlms-develop] msh won't load in tomcat, used to work fine before the holidays

[Ng C. Y. [Cyng] <cy...@cs...>]

Hello,

> I reloaded the jar's from 17-12-2002, while retaining the msh.jar from
> yesterday. This appears to work just fine, so I must conclude the error
> is in the update of xerces (all other jars are untouched betweeen those
> versions).

> Note that filenames for Xerces have changed: older version was just
> xerces.jar, newer is xercesImpl.jar and xmlParserAPIs.jar.

>   ----- Original Message -----
>   From: Gait Boxman
>   To: ebx...@li...
>   Sent: Thursday, January 02, 2003 2:28 PM
>   Subject: [ebxmlms-develop] msh won't load in tomcat, used to work
>            fine before the holidays
>
>   Hi,
>
>   running j2sdk1.4.1. and jakarta-tomcat-4.1.10, I found out the msh
> pulled from CVS this morning no longer loads. I attached the log file.
> Any idea what is going wrong? Could it be related to the update of
> Xerces? If so, should I update something additional?

        I suppose you must be using tomcat-4.1.10 full version which
includes more .jar files in directory "common\lib" and "common\endorsed".
The is the root of the problem.

        xerces.jar is 1.4.4 while xercesImpl.jar and xmlParserAPIs.jar are
2.2.1 and you may notice that there are also xercesImpl.jar and
xmlParserAPIs.jar in "common/endorsed". These two files would conflict
with those in your "webapps". So, you may simply delete these two files
in your "webapps".

        However, you may then notice another problem. There are also
activation.jar and mail.jar in "common/lib" bundled with the tomcat
full version while you also have them in "webapps". When you send
messages, tomcat may complain something like:

java.lang.Error: DataContentHandlerFactory already defined
        at javax.activation.DataHandler.setDataContentHandlerFactory(DataHandler
.java:628)

because a static factory in activation.jar is somehow loaded twice
by tomcat accidentally. It doesn't help if you delete activation.jar and
mail.jar in your "webapps". If you delete activation.jar in "common/lib",
mail.jar in "common/lib" would complain NoClassDefError for activation.jar.
So, you have to delete both files while keeping activation.jar and mail.jar
in your "webapps" to make things work. The above "features" have long been
observed in tomcat's class loading mechanism.

        To me, I would simply use jakarta-tomcat-4.1.18-LE-jdk14.tar.gz,
the light-weight version being run under JDK1.4. All those files are not
bundled in "common/lib" or "common/endorsed".

Regards,
CY

----------------------------------------------------------------------------
Ng Chi Yuen, CY.       cy...@ce...       http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------