That could work. BTW where is the advanced tiles PDF?
The other possibility I suppose is to have the default layout use an include that
specifies
c:set var=titleKeytiles:getAsString name=titleKey//c:set
titlebean:message key=${titleKey}//title
and it could be overriden in an extended
Thanks Denial,
But the code which I have submitted fine, there is no need to add anything
extra.
-Jignesh
On Friday 21 May 2004 21:36, Daniel Perry wrote:
If you are calling saveToken(request) before isTokenValid like your code
suggests, you are probably overwriting the token in the session,
Providers is a framework to be used with JSP to fill Select options in
HTML. You can use it with Struts to replace html:options tag and use
prv:options to fill the select without the need of creating a collection
in an Action.
Providers is intended to help in managing select related problems.
http://providers.sourceforge.net/
-Original Message-
From: Guillermo Meyer [mailto:[EMAIL PROTECTED]
Sent: Sábado, 22 de Mayo de 2004 09:24 a.m.
To: Struts Users Mailing List
Subject: [ANN] Providers 0.3 Released (includes DisplayTag tip)
Providers is a framework to be used with JSP to
Tim,
The advanced tiles pdf is under the User and Developer Guides
(http://jakarta.apache.org/struts/userGuide/index.html), Tiles Guide
(http://jakarta.apache.org/struts/userGuide/dev_tiles.html), under the
bottom-of-the-page link Tiles Advanced Features:
I am having a problem using Action forms because I do not know what to call
the attributes (setters and getters on the form) so that they are called
with the request values. Here is a sample of the JSP:
td
html:select name=yeast property=yeastLab.ID
html:options collection=labList property=ID
Thomas T. Veldhouse wrote:
I am having a problem using Action forms because I do not know what
to call the attributes (setters and getters on the form) so that they
are called with the request values. Here is a sample of the JSP:
td
html:select name=yeast property=yeastLab.ID
html:options
I'm using the 1.1 validator framework. I have activated the validator
pluging correctly, because I can see the validations
from the validation.xml file being displayed on the output from the
app-server. I know that the validations themselves are working as per
the validations that I set up in
Hi all,
I am puzzled about the behavior of the set-property element when it is nested in an
action element. I thought it was setting the properties of the Action class, but it
seems not working. Could you please help me clear it up?
Thanks!
Paraman
9 matches
Mail list logo