Whew,
I found the problem and the solution is easy! But, JBoss should watch for this.

The manifest file had the following line:
Class-path: jmxri.jar xalan_2_0_0.jar xerces_1_2_3.jar .

That last little "." is the cause of all the problems. I presume what happens is that when JBoss doesn't find xalan_2_0_0.jar and xerces_1_2_3.jar it starts searching the current directory. It then finds it hasn't loaded jpos1.4.0.jar, and we're off again on the merry go round.

The temporary solution is easy: just remove the scurillous little dot, and repackage the jar.

However, I think this should be a low priority bug to be fixed in the deployer. What say you all?
Ciao,
Jonathan O'Connor
Ph: +353 1 872 3305
Mob: +353 86 824 9736
Fax: +353 1 873 3612

Reply via email to