ingo schuster wrote:
>
> At 17:53 01/26/01, John McNally wrote:
> >I would prefer to see something that emphasized the "template" keyword
> >over "screen" or at least provided a property for it so it is as easy.
> >Also, would it not be good to include tags to add QueryData and PathInfo
> >to the URI?
>
> Yes, I will add a template keyword as well. Must admit that I interpreted
> the Rundata.screen as a template in Jetspeed - it was only a few days ago
> that I realized there is a ScreenTemplate which I should have used
> instead... Do you think the screen parameter should be removed so that
> there is only "template" and "action"?
>
That may be possible with JSP though not necessarily desirable. The
screen parameter should be used to specify a Java class that will be
responsible for generating a response. For example, when the response
is a binary file that for whatever reason (security) is being served
through Turbine. Since in JSP you code code this entirely within your
JSP template you do not have to use Screens, though that is one of the
reasons most people here are avoiding JSP. A class that almost entirely
consists of Java code should be written a normal Java class, not a JSP.
> Regarding QueryData and PathInfo, I don't really know what it is exactly
> used for. Is there any document explaining it (apart from the source code
> ;-) )? It looks as if it changed class variables and then it wouldn't make
> sense to set it via own tags as the object would be destroyed after the tag
> has been called.
I think it would best be implemented with inner tags
<x:uri template="department.jsp">
<x:pathinfo key="dept" value="shoe"/>
<x:querydata key="user" value="256"/>
</x:uri>
would result in something like
http://host/app/template/department.jsp/dept/shoe?user=256. Quite a few
details missing here as I do not know exactly how one nests tags in
jsp. But you can have multiple parameters so you need some way of
specifying more than one. I guess a simpler not as flexible tag would
have, say, 5 slots for each and they can be added as simple attributes.
<x:uri template="department.jsp" pathinfokey1="dept"
pathinfovalue1="shoe" pathinfokey2="user" pathinfovalue2="256">
to give http://host/app/template/department.jsp/dept/shoe/user/256/
> And you certainly don't want to hold a reference to a
> dynamicUri object within a Jsp.
> So it could only be another (optional) parameter for the DynamicUriTag and
> I'm not sure if this makes sense?
I think it should be possible that your tag instantiates a DynamicUri
and the setXXX methods directly set the corresponding DynamicUri
properties. (But maybe not, I just don't see why it can't be done more
efficiently.)
>
> ingo.
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
