Hi!
i try to migrate an old cocoon application (started with 2.0, and was
migrated to 2.1 at least partly, will say with least possible efford...)
As a matter of fact, i try to modularize our application and with that i
run in some problems.
So long we had a central cocoon.xconf, and in
So, now did i try out some things, i guess i have to get down to the
base first :-). I configured a data source in the target block itself
in a cocoon.xconf file under src/main/resources/META-INF/cocoon/xconf/
and used that data source in the sitemap, but it looks like the xconf is
not read
The main reason (speaking as a user) I think XSP was deprecated
is that it does not fit well with the cocoon mantra of 'separation of
concerns' i.e. too easy to mix in markup and code in one place (not
that you have to, of course). I also used ESQ/XSP for my early DB
apps, but I really find that
Stephen Winnall wrote:
I think a lot of the anti-XSLT sentiment comes from people who don't see
the point of XML.
Yes, there are many of these.
XML and its philosophy are far too complicated for the average
designer-cum-website-hacker. This is neither a criticism of XML nor of
the d-c-w-h.
Out of interest... which part of Cocoon lacks date/time awareness -
the sitemap? Can't a (custom-written) java module execute/call an
external program? Also not sure about directory listing - does the
Directory Generator not serve in that role?
On 2009/04/30 at 02:48, in message
Some further investigations and a little bit try and error got me a bit
further:
- the xconf file has to be placed in
src/main/resources/META-INF/cocoon/avalon
- i figured out that if i write some xml which is not valid, that the
file is read, because then a error during the startup is
oddly enough, the first example of embedded XSP in the Moczar and Aston
book is to find the time
with a tiny bit of embedded java.
xsp:logic
Date now = new Date();
/xsp:logic.
...
By the way, today's date is xsp:exprnow,/xsp;exp
--
I have also used the considerable date/time
