Yes, these are velocity views I'm using w/ WW actions.

I haven't read any of this thread, so forgive me if I'm totally off base
here. If we're talking about a velocity view, $someMethod() won't work
afaik. Anything in the form $foo is considered a property, not a method,
and can't accept parameters. $foo looks for getFoo() in the context. This
came up in last weeks meeting (and the minutes are on their way, I promise
:) ). There isn't a way to call a method in an action from a velocity
view.
I didn't understand this last remark. Lines like the below example call my actions methods just fine.

<input type="text" name="toolSetName">

... so that calls this ....

public void setToolSetName(String name) {...

though using a checkbox in the same way doesn't call either the get or set method.

The work around is to add a method to your action that returns
`this`:

public MyAction getMyAction() {
  return this;
}

Then you can do $action.setSomeMethod(...) (I think?).

My action is extended from ActionSupport, so just to clarify (cause I'm not clear on the suggestion of $action.setSomeMethod(...)), when I click the submit, I'm expecting that setSomeMethod(...) get called for every checkbox that's checked and stores those values.

I'm going to play w/ that example some more to see if I can understand what you mean.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to