You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Joerg Heinicke <jo...@gmx.de> on 2005/09/18 13:21:00 UTC
Re: Cocoon 2.1.t: is it still difficult to embed a CForm into legacy
pages?
On 13.05.2005 14:59, Enrico Migliore wrote:
> I think that Cocoon should not introduce tags like <html>
> or <body> in the process. Those tags should be introduced
> by the user. You can't imagine how many hours I spent in
> modifying those XSL stylesheet.
This is not the case since really a long time. Don't know if it was a
year ago, but the stylesheets were splitted and can be now reused and
integrated quite easily. There is one stylesheet integrating all others
when doing CForms standalone. This stylesheet is the only one producing
<body>, <head>, etc.
In the meantime the core stylesheets have even been moved into the
cforms.jar while the integrating stylesheet called
forms-samples-styling.xsl remains in the samples section of the cforms
block.
> Yet, the Java Flow classloader doesn't reload a class that
> has been modified by an external tool. That means that,
> at developing time, each time you make a modification in
> the class, you have to stop and restart Cocoon....
Don't know about the current status here. Do you have tested the
CompilingClassLoader. This should even have worked with former Cocoon
versions.
The future looks even more bright: JCI (Java Compiler Interface) and
Javaflow have both been moved from Cocoon to Jakarta Commons Sandboy and
are developed independently. I expect an integration with much
improvement in the near future.
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org