Hello,
I've noticed JSP isn't this list's favorite topic so I'll be brief:
I've successfully installed & configured Turbine under Resin 1.2, to
the point where I can build and run custom actions and screens using
ECS. I've browsed the javadoc and list archives, but I can't quite
figure out the specific steps I need to take in order build a working
application that works as follows:
- A request comes in; Turbine handles authentication, session
management and business logic.
- Turbine actions/screens put various pieces of data in objects that a
JSP can access via <jsp:useBean> or however.
- Turbine's navigation & layout features go largely unused.
- The flow of control is passed to a JSP, which munges data from the
action/screen together with HTML/XML. When a JSP needs to do things
that access application data (e.g. build links), it directly
accesses relevant Turbine singletons.
If somebody could provide a quick blow-by-blow on what I need to do
(what properties to set, what the screens to subclass & what methods
they should implement, how to specify and pass control to the jsp
template, etc) I would be very indebted. Also, I'd be happy to write
documentation once I better understand how the various parts of such a
framework fit together.
Unfortunately, Webmacro/Velocity isn't an option for this project, for
purely bureaucratic reasons. Thanks in advance and my apologies for
bringing up such an abominable topic ;-). I've been very impressed
with Turbine thus far, and can't wait to get it integrated into our
existing system.
Cheers,
David
--
David Noll, Public Digital
[EMAIL PROTECTED] | http://pudg.org
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
