You get very similar functionality for date/time in flowscript;
also it seems that XSLT 2.0 can do this via fn:current-dateTime()
http://www.w3.org/TR/xpath-functions/#func-current-dateTime
(Disclaimer: I have not used 2.0 - but others in this thread have;
maybe they can respond here?)
On
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
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
Yes it is.
Just add the saxon-transformer to your sitemap, add the necessary
lines in cocoon.xconf and make sure you are using the correct
transformer in your pipelines have installed the appropriate jar in
you lib-folder.
It also works to do a quick google on the subject (apache cocoon saxon):
Derek Hohls wrote:
Ken
I would echo most of your sentiments, except for the XSP part.
I have found that the flowscript/JXT gives me all the logic/layout
options I need ... without having to worry about any Java at all in
my apps. I think that is why the developers decided to deprecate
XSP
Hi Derek,
Thanks for spotting out my error. I was wondering why there where too
few related mails about Freemarker in cocoon. :P
Best Regards,
Antonio Gallardo
Derek Hohls escribió:
Antonio
True - but it would be useful to tell the original author this
as well!
PS it is Freemarker (not
Ken
I would echo most of your sentiments, except for the XSP part.
I have found that the flowscript/JXT gives me all the logic/layout
options I need ... without having to worry about any Java at all in
my apps. I think that is why the developers decided to deprecate
XSP quite a while back,
Antonio
True - but it would be useful to tell the original author this
as well!
PS it is Freemarker (not maker)
[1] http://cocoon.markmail.org/search/?q=freemarker
On 2009/04/24 at 10:07, in message 49f21bea.7030...@agssa.net,
Antonio Gallardo agalla...@agssa.net wrote:
hi Derek,
It is possible to make cocoon use Saxon, which implements xslt 2.0, as it's
underlying xslt processor.
StanD.
Derek Hohls wrote:
Ken
I would echo most of your sentiments, except for the XSP part.
I have found that the flowscript/JXT gives me all the logic/layout
options I need ... without
Stephen Winnall wrote:
I think a lot of the anti-XSLT sentiment comes from people who don't
see the point of XML.
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. XML and tools which make use of
Antonio Gallardo wrote:
hi Derek,
Comparing XSLT with JSP is like comparing pears and apples. XSLT is
quite useful for some tasks and weak in others. The same apply for JSP.
We still use XSLT even if you have JSP at hand. In cocoon particular
wolrd, perhaps he should compare JSP with XSP.
I
Hi Ken,
I guess that many people feel the same way about XSP. Remember XSP is
evil :
http://www.nabble.com/Re:-How-can-i-activate-XSP-in-cocoon-2.2---p19457928.html
http://markmail.org/message/ciwirkn5gs4lrahz
From my point of view, XSP was one of the reasons of Cocoon's success,
of course
I think a lot of the anti-XSLT sentiment comes from people who don't
see the point of XML.
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. XML and tools which make use of it and fairly
. It really helps to separate the content
from the layout. But in the end that's a matter how you design your
application. I see a lot of people using other frameworks than Cocoon
and pass the output from that framework to XSLT after the framework has
rendered the content. So I don't think that XSLT
the framework has
rendered the content. So I don't think that XSLT itself is dead. The
attraction of Cocoon as a separate framework has decreased, but that's
definitly not due to XSLT.
Carsten
--
Carsten Ziegeler
cziege...@apache.org
--
This message is subject to the CSIR's copyright terms
the framework has
rendered the content. So I don't think that XSLT itself is dead. The
attraction of Cocoon as a separate framework has decreased, but that's
definitly not due to XSLT.
Carsten
--
Carsten Ziegeler
cziege...@apache.org
--
This message is subject to the CSIR's copyright terms
Derek Hohls wrote:
Carsten
I had hoped comments like these would be added to the blog :)
I usually do not comment blog entries - sorry :)
One other point, you say:
The attraction of Cocoon as a separate framework has decreased,
but that's definitely not due to XSLT.
Why do you say
.
-Ursprüngliche Nachricht-
Von: Derek Hohls [mailto:dho...@csir.co.za]
Gesendet: Freitag, 24. April 2009 09:14
An: users@cocoon.apache.org
Betreff: [!! SPAM] Re: XSLT is Dead ?!
Oh, and on the flip side, there's this article:
http://www.onenaught.com/posts/8/xslt-in-server-side-web-frameworks
Von: Merico Raffaele [raffaele.mer...@less.ch]
Gesendet: Freitag, 24. April 2009 14:17
An: users@cocoon.apache.org
Betreff: AW: Re: XSLT is Dead ?!
Dear Cocoon Community
First of all I have to say that I am a Cocoon lover.
We are working with this framework since 2005
more tempting for me at the moment because of its
simplicity.
Chris
Von: Merico Raffaele [raffaele.mer...@less.ch]
Gesendet: Freitag, 24. April 2009 14:17
An: users@cocoon.apache.org
Betreff: AW: Re: XSLT is Dead ?!
Dear Cocoon Community
First of all I
@cocoon.apache.org
Betreff: AW: Re: XSLT is Dead ?!
Chris
I had to smile - here you say:
the Maven build-process, the maven-plugins needed and the changes in
the project-structures gave me the impression of relearning the entire
thing from scratch.
while in the next breath you talk about the simplicity
Derek Hohls wrote:
At least, according to this article:
http://java.dzone.com/news/death-xslt-web-frameworks
Maybe some of the developers, or other power users here,
would like to comment at this blog - I see Cocoon also gets
a dig in the ribs ...
Derek
I saw this also. A few of his
: Re: XSLT is Dead ?!
Derek Hohls wrote:
At least, according to this article:
http://java.dzone.com/news/death-xslt-web-frameworks
Maybe some of the developers, or other power users here,
would like to comment at this blog - I see Cocoon also gets
a dig in the ribs
hi Derek,
Comparing XSLT with JSP is like comparing pears and apples. XSLT is
quite useful for some tasks and weak in others. The same apply for JSP.
We still use XSLT even if you have JSP at hand. In cocoon particular
wolrd, perhaps he should compare JSP with XSP.
I did not read the whole
At least, according to this article:
http://java.dzone.com/news/death-xslt-web-frameworks
Maybe some of the developers, or other power users here,
would like to comment at this blog - I see Cocoon also gets
a dig in the ribs ...
Derek
PS I'm also curious about the package mentioned a
27 matches
Mail list logo
