Do you think the layout/navigation/screen module for jsp will be checked Any
time soon ?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of John McNally
Sent: Wednesday, November 15, 2000 8:07 PM
To: Turbine
Subject: Re: Request for help: JSP templating
services.TurbineTemplateService.default.screen=BaseJspScreen
Get started without layouts. You need a tag library to
use the layout/navigation/screen modules, which is
currently somewhere on my home machine.
Subclass BaseJspScreen and override the
getLayout(RunData) method to return null. Then set
the property above to this new screen module.
Let me know if this helps you get started with JSP
screen templates.
I know this doesn't really answer your question, but I
am not seeing a problem with your configuration. But
I do know an important component is missing to use
layouts with JSP.
John McNally
--- David Noll <[EMAIL PROTECTED]> wrote:
> Many thanks for the advice. I spent some time
> playing with WebMacro
> templates per the tutorial and now the JspService
> javadoc makes a lot
> more sense. :-)
>
> There is one little issue, though, that I am stuck
> on: when I make a
> JSP version of the WebMacro HelloWorld example
> (http://java.apache.org/turbine/webmacro-site.html)
> I get a 404 error
> where the server is looking for "/layoutsnull". This
> error seems tied
> to activating JspLayout as the default layout in the
> TR.props. In the
> past, it looks like people have solved this by using
> the
> TemplateSessionValidator; on that note I tried
> several of the
> different sessionvalidators, all with the same
> "layoutsnull" result.
>
> I suspect I've done something boneheaded in my conf
> file to cause
> this. Is there a property beyond
> "TurbineTemplateService.default.layout.template"
> that needs to be set
> in order to get a HelloWorld application running?
>
> If it's any help, I put the conf file at
> http://www.pudg.org/temp/TurbineResources.properties
>
> Regards,
> David
>
>
> ----- Original Message -----
> From: "John McNally" <[EMAIL PROTECTED]>
> To: "Turbine" <[EMAIL PROTECTED]>
> Sent: Tuesday, November 14, 2000 6:09 PM
> Subject: Re: Request for help: JSP templating
>
>
> [EMAIL PROTECTED] wrote:
> >
> > Hello,
> >
> > I've noticed JSP isn't this list's favorite topic
> so I'll be brief:
>
> You are right that it isn't the most popular
> templating system for
> Turbine, but there is no reason you can't use it.
> There is a basic
> interface, so that JSP can be used similarly to
> Velocity or WebMacro.
> All it needs is someone who wants to use it and is
> willing to make it
> better.
>
> >
> > 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.
>
> The Turbine servlet (along with default modules)
> contains code to help
> with the first; of course the business logic objects
> and
> action/screen/... modules to assemble them for the
> templates or process
> them are the main parts you need to build to put
> together an
> application.
>
> >
> > - Turbine actions/screens put various pieces of
> data in objects that a
> > JSP can access via <jsp:useBean> or however.
>
> My limited understanding of JSP has led me to just
> dump everything in
> the request for processing by the JSP. I do not
> think a page designer
> should be concerned about the scope of an object.
> If an object is being
> stored in the session and it is appropriate for a
> screen that will
> generate the response, The Java Screen should add
> the object to the
> request, so the JSP is not concerned about where all
> the objects are.
> That's just my opinion though. One example is that
> the JSP service adds
> the RunData object to the request, so it is always
> available to the JSP.
>
> >
> > - Turbine's navigation & layout features go
> largely unused.
>
> But they can be used. I have added all the classes
> necessary to use
> them. The one piece I have not checked in is the
> tld (which could
> easily be checked in, but is probably fairly useless
> without some
> docs). But you can use JSP without them, correct.
>
> >
> > - 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.
>
> 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.
>
> The JSP service and associated modules follow very
> closely the model
> given by all the rest of the template related
> services. Understand one
> and you understand them all.
>
> Good luck.
>
> John McNally
>
> (BTW, for anyone who is interested. I have been
> preparing for a move to
> CollabNet, where I start tomorrow. No guarantees
> when that might
> increase my contributions to Turbine, but just
> increasing my daily
> exposure to Java related work over what I have had
> the last few months
> ought to improve things considerably.)
>
>
>
------------------------------------------------------------
> To subscribe:
> [EMAIL PROTECTED]
> To unsubscribe:
> [EMAIL PROTECTED]
> Search:
>
<http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
>
>
>
>
------------------------------------------------------------
> To subscribe:
> [EMAIL PROTECTED]
> To unsubscribe:
> [EMAIL PROTECTED]
> Search:
>
<http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
