> Ok, that's bizarre. Can anyone else confirm this? There are very few > logical places where any interaction between the jms and portal block > should be happening. You're saying that the portal block works as long > as you remove the openJMS library?
I did another test to pin down the problem a little bit more. I exluded the portal and portal-fw blocks from the blocks.properties file and tested again. This time I had another NoClassFoundException requesting a openJMS util package. I found this in the exolabcore.jar file and included that in the lib directory. After this Cocoon ran fine again. Soooooo, I added the portal and portal-fw blocks again and recompiled (phew). Using both the openjms-0.7.6.jar and exolabcore-0.3.7.jar files got rid of all problems. Cocoon runs fine now with everything enabled. So it seems one error was covering up for another one. :-/ Anyways, problem solved. Bert > > Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
