cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <>
Subject Re: Cocoon not compatible with latest Avalon/Excalibur version?
Date Tue, 03 Dec 2002 10:37:44 GMT
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                   
Outerthought - Open Source, Java & XML Competence Support Center

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message