Re: Giving up! Cocoon too big, slow and confusing

Absolutely! BUT, the point isn't that everyone's dissing Cocoon, it's that a weakness has been identified, and is being discussed. No need to be defensive about it - that's what will drive people to amend the situation. Regards Anthony Aldridge Application Development Mana

RE: Giving up! Cocoon too big, slow and confusing

bout its friends! I reckon the time has past when we can be choosy - otherwise .NET rubbish will start becoming another cross we all have to bear (as developers), when properly presented, Cocoon could provide a real way forwards to the web-app community! Regards Anthony Aldridge Application Develo

Re: The woes of Weblogic 6.0sp2 and Cocoon - found the problem at last:)

Removing the packages fron the jars was how I got round my WL issues - a bit of a pain - but it did the trick. Tony Konstantin Piroumian <[EMAIL PROTECTED]> on 04/26/2002 02:49:06 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: The woes of Weblogic 6.0sp2 an

Re: The woes of Weblogic 6.0sp2 and Cocoon - found the problem at last :)

v6.1 is out now - and BEA are not the quickest. You could always remove WLs version of avalon and replace it, or remove it form the system classpath and leave only in the webapp classpath (if that's still how WL 6.0 works - see my previous email). Good luck, Tony PS What's wrong with tomcat?

Re: I cannae dae it (the woes of Weblogic 6.0sp2 and Cocoon) :(

Not sure if WL 6.0 is different, but on previous versions of WL there is a lot of confusion surrounding where jars are kept. It basically has 2 separate classpaths - 1 for WL itself, and 1 for the webapps. If the jars are in the wrong classpath you can get the kind of messages you see below - ev