Hi Bruno, thanks for your answers. In the meantime I did what you suggested and it seems to work with our own instances of ExcaliburComponentManager and DefaultRoleManager.
Regards, Francis -----Original Message----- From: Bruno Dumon [mailto:[EMAIL PROTECTED]] Sent: dinsdag 3 december 2002 11:38 To: [EMAIL PROTECTED] Subject: Re: Cocoon not compatible with latest Avalon/Excalibur version? On Mon, 2002-12-02 at 17:25, Vermeulen, Francis wrote: > Hi folks, > > we are trying to invoke an application framework from within Cocoon by means > of a custom transformer. This framework itself uses Avalon/Excalibur > components through a separate component and role manager, instantiated from > within the framework. The framework is developed using the version 4.1.2 of > Avalon and 4.1 of Excalibur and works fine in "stand-alone"mode when invoked > from our own servlet. However when invoked from the custom transformer in > Cocoon version 2.0.3, the Avalon/Excalibur part doesn't work because we are > then using the version supplied with Cocoon as libraries. What exactly do you mean with "doesn't work"? Do you get any exceptions or just strange behaviour? > So to me it looks > as if Cocoon comes bundled with its own version of Avalon/Excalibur that is > not compatible with the latest release of these. Wouldn't it help to simply recompile your own framework against the avalon libraries that ship with cocoon? -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
