btw #parameters['model.parentId'] will return an array, not just one
value, so #parameters['model.parentId'][0] will give you the value you
are looking for.
musachy
On Jan 31, 2008 2:07 PM, Laurie Harper <[EMAIL PROTECTED]> wrote:
> Dave Newton wrote:
> > --- [EMAIL PROTECTED] wrote:
> >> Yeah, t
n" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, January 31, 2008 2:22 PM
Subject: Re: #request scope
> --- Laurie Harper <[EMAIL PROTECTED]> wrote:
> > Dave Newton wrote:
> > > --- [EMAIL PROTECTED] wrote:
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
> Dave Newton wrote:
> > --- [EMAIL PROTECTED] wrote:
> >> Yeah, that's what I thought too! I'm passing the parameter via:
> >>
> >>
> >>
> >>
> >>
> >> and the tag outputs the
> >> number to the t
Dave Newton wrote:
--- [EMAIL PROTECTED] wrote:
Yeah, that's what I thought too! I'm passing the parameter via:
and the tag outputs the
number to the top of the page just fine.
Do you have a "model" property in your action?
In fact,
--- [EMAIL PROTECTED] wrote:
> Yeah, that's what I thought too! I'm passing the parameter via:
>
>
>
>
>
> and the tag outputs the
> number to the top of the page just fine.
Do you have a "model" property in your action?
> In fact, if I
Yeah, that's what I thought too! I'm passing the parameter via:
and the tag outputs the
number to the top of the page just fine. In fact, if I use
#parameters.model.parentId I get nothing. The problem is that I don't get
anything from the
--- [EMAIL PROTECTED] wrote:
> Parameters and it contains the value immediately before entering the
> iterator, as I am printing it out. Seems goofy to have to set a var just
> to use it in the loop two lines later.
#request is attributes. #parameters is parameters.
I can't dupe the issue with a
Parameters and it contains the value immediately before entering the
iterator, as I am printing it out. Seems goofy to have to set a var just to
use it in the loop two lines later.
On Jan 29, 2008 5:10 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- stanlick <[EMAIL PROTECTED]> wrote:
> > I hav
--- WongTseng <[EMAIL PROTECTED]> wrote:
> in S2, inside iteration, the item object is push onto the VS, so just
> remove the pound key.
Accessing a request attribute, however, still requires the "#" because it's a
named value on the stack, not simply a pushed action or the current object of
an it
in S2, inside iteration, the item object is push onto the VS, so just
remove the pound key.
--
Best Regards
Wong Tseng
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- stanlick <[EMAIL PROTECTED]> wrote:
> I have a weird situation where I am losing a request
> parameter inside a loop!
> [...]
>
Doesn't "#request" retrieve request *attributes*?
Dave
-
To unsubscribe, e-mail: [EMAIL PROTE
Dave Newton wrote:
>Kyle W. Cartmell wrote:
>
>
>>I understand the concept behind this, but does anyone actually use
>>this in production code? Seems more trouble than it's worth since the
>>user could simply start multiple sessions.
>>
>>
>
>How? Isn't that browser-dependent?
>
>And no, I w
On 5/3/06, Y. Thomas Gan <[EMAIL PROTECTED]> wrote:
Dave Newton wrote:
> Kyle W. Cartmell wrote:
>
>> I understand the concept behind this, but does anyone actually use
>> this in production code? Seems more trouble than it's worth since the
>> user could simply start multiple sessions.
>>
>
> Ho
Dave Newton wrote:
Kyle W. Cartmell wrote:
I understand the concept behind this, but does anyone actually use
this in production code? Seems more trouble than it's worth since the
user could simply start multiple sessions.
How? Isn't that browser-dependent?
And OS dependent too. On
Kyle W. Cartmell wrote:
> I understand the concept behind this, but does anyone actually use
> this in production code? Seems more trouble than it's worth since the
> user could simply start multiple sessions.
How? Isn't that browser-dependent?
And no, I wouldn't bother dealing with this use-case
I understand the concept behind this, but does anyone actually use this
in production code? Seems more trouble than it's worth since the user
could simply start multiple sessions.
Michael Jouravlev wrote:
On 5/3/06, Y. Thomas Gan <[EMAIL PROTECTED]> wrote:
Is there a way in struts to chain a
On 5/3/06, Y. Thomas Gan <[EMAIL PROTECTED]> wrote:
Is there a way in struts to chain a series of requests (paging through a
list) and pass data through request scope?
In my scenario, I keep the a result list in session, but this prevents
me from opening two windows (same session)
and paging thro
17 matches
Mail list logo
