Actually now that you mention it, yeah, it should use the outer form by
default, I will fix it for 2.1
regards
musachy
On 4/13/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
That did it!
Thank you, thank you. Not sure why I have to specify
a form I am already in, but I don't care. It works!
That did it!
Thank you, thank you. Not sure why I have to specify
a form I am already in, but I don't care. It works!
Thanks again,
Scott
--- Musachy Barroso <[EMAIL PROTECTED]> wrote:
> Ooops sorry, now I got it, you need to put sportsOrg
> inside a form, and
> point to it from the other a
Ooops sorry, now I got it, you need to put sportsOrg inside a form, and
point to it from the other autocopleter, using "formId"
musachy
On 4/13/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
Well, there is not submit per se, the action is
getting called when the user types the second char in
th
Well, there is not submit per se, the action is
getting called when the user types the second char in
the lookup editor.
Here is the log when the user types zz:
DEBUG interceptor.FileUploadInterceptor - Bypassing
/html/ LookupSportsTeam
DEBUG interceptor.StaticParametersInterceptor -
Setting s
When you click submit, are they getting submitted to the action (with
values)?
musachy
On 4/13/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
Well, it is great that we are both right but it is
still not working.
I don't care about "foo", I was just trying to make my
code simpler in the email.
Well, it is great that we are both right but it is
still not working.
I don't care about "foo", I was just trying to make my
code simpler in the email. The actual code has two
autocompleters like this:
In LookupSportsTeamAction I need the value of wh
--- Scott Nesbitt <[EMAIL PROTECTED]> wrote:
> Not sure why it should be getBar(). The name of the
> hidden field is foo, so shouldn't that be the
> variable that has the getter and setter?
You guys are both right.
The argument to the 'value' attribute is an object:
> > >
*is* looking for a
the value for the field comes from the "value" attribute, which is evaluated
against the Value Stack.
musachy
On 4/12/07, Harring Figueiredo <[EMAIL PROTECTED]> wrote:
I am sure it should NOT be getBar() either. It should be getFoo().
Perhaps there is a bug with the framework on not processin
I am sure it should NOT be getBar() either. It should be getFoo().
Perhaps there is a bug with the framework on not processing/doing reflection
on hidden fields?
hf.
On 4/12/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
Not sure why it should be getBar(). The name of the
hidden field is foo,
Not sure why it should be getBar(). The name of the
hidden field is foo, so shouldn't that be the variable
that has the getter and setter?
Regarding passing the field as a parameter, I am not
too proud for that. Could you post a little example
code? I tried to do something like this:
A
Scott:
I had a similar problem, and I got around it by getting the parameter
myself...
(I know.. a little pain, but got it done)
Let me know if you get the _correct_ way working.
hf.
On 4/12/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
I have a form with an autocompleter like this:
You should have a "getBar()" defined on your action, not a "getFoo()"
regards
musachy
On 4/12/07, Scott Nesbitt <[EMAIL PROTECTED]> wrote:
I have a form with an autocompleter like this:
I expected that my LookupSportsTeamAction class (which
extends ActionSupport and has
12 matches
Mail list logo
