cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [WARNING] Incompatible change (was Re: DELI support added)
Date Fri, 11 Jan 2002 09:45:57 GMT
Ovidiu Predescu wrote:
>
> On Thu, 10 Jan 2002 18:00:22 -0500, Berin Loritsch
> <bloritsch@apache.org> wrote:
>
> > Ovidiu Predescu wrote:
> >
> > > I guess the problem comes from the fact that cocoon.jar was built with
> > > the Deli classes in it. I'll update the build.xml to verify the
> > > presence of Deli libraries, and skip the compilation if they are not
> > > present.
> >
> >
> > With the Deli.jar in the CVS repository there is little to be gained by
> > that.  My point was that even if DELI support was compiled into
> the cocoon.jar
> > file, the runtime should not force users to include the deli.jar file as
> > dead weight in the system.
>
> Did you try removing the <deli>...</deli> configuration from
> cocoon.xconf, and the "deli" role from cocoon.roles?
>
> This should solve the problem as there's no place in the code that
> makes reference directly to DELI, other than the
> org.apache.cocoon.components.deli.Deli interface.
>

Unfortunately, this is not true. The TraxTransformer has dependencies
to some hp.* packages!
A clean solution shouldn't have this dependency. The TraxTransformer
should check if the deli component is available and only then use and
the hp.* classes should be wrapped by some lightweight
cocoon.components.deli
classes to get rid of the external imports.

Regards
Carsten

> Please let me know if this fixes the problem. I will anyway work on
> fixing the build problem.
>



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message