]
Sent: Friday, October 19, 2001 2:21 PM
Subject: Re: Velocity / JSP / XML XSLT : Why ???
Norman Schoneich wrote:
Jetspeed supports different template engines.
But in the moment, the default template layout engine is velocity and
it'is
the most supported engine by the jetspeed
PROTECTED]
Sent: Friday, October 19, 2001 2:21 PM
Subject: Re: Velocity / JSP / XML XSLT : Why ???
Norman Schoneich wrote:
Jetspeed supports different template engines.
But in the moment, the default template layout engine is velocity and
it'is
the most supported engine by the jetspeed developers
We are making Jetspeed evolve so that it supports both byte-stream
portlets (be them java-class-portlets, jsp, vm,...), and
sax-event-stream portlets (be them XSLT based or generated). You are
welcome to help here. ;-)
Where is the code ? to try to help a bit :), i'm interested..
Ignacio J. Ortega wrote:
We are making Jetspeed evolve so that it supports both byte-stream
portlets (be them java-class-portlets, jsp, vm,...), and
sax-event-stream portlets (be them XSLT based or generated). You are
welcome to help here. ;-)
Where is the code ? to try to help a bit :),
I will try to open something ASAP. In the while, looking at
the current
Velocity rendering process and making it abstract and compatible with
JSP should help to have a cleaner set of interfaces. For instance,
having tools being exposed automagically as JSP-beans using
introspection
