I'd have to test to be sure but I don't thinl the plug in cares about
the method. It will do action-return.jsp the way it does for normal
processing.
On 5/29/09, Jim Collings wrote:
> So if I use dynamic method invocation, like so:
>
> /admin/change-wingding!change
>
> How will the result urls fo
So if I use dynamic method invocation, like so:
/admin/change-wingding!change
How will the result urls for that call be constructed?
Jim C.
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands,
Musachy Barroso wrote:
> if you add a "/" to the action name, it won't append the namespace to
> it, but use it as the whole action name. If your namespace is
> "myactions", and you set the name as "/action", the action name is
> "/action", if you set it to "action" then the action name will be
> "
if you add a "/" to the action name, it won't append the namespace to
it, but use it as the whole action name. If your namespace is
"myactions", and you set the name as "/action", the action name is
"/action", if you set it to "action" then the action name will be
"/myaction/action".
musachy
On T
So I have this working but I had to specify a value for @Action. I don't
think I should have to do this. There should be a convention in the
convention plugin of assuming that a result mapped the way I tried to map it
is for the current method using it's conventional url when value is left
blank.
Currently I have no unusual interceptors or changes thereto. I've been
holding off trying to learn em just yet.
First things, first. I'm using the default stack.
Jim C.
On Thu, May 14, 2009 at 1:34 PM, Musachy Barroso wrote:
> Do you have a custom stack interceptor? If the fields are not
> pop
Do you have a custom stack interceptor? If the fields are not
populated in the action, then the params interceptor is not getting
applied, it is hard to say without more details.
musachy
On Thu, May 14, 2009 at 1:30 PM, Jim Collings wrote:
> I have an action with "execute" in the superclass (Act
I have an action with "execute" in the superclass (ActionSupport) being
called by one activity and another method of the same Action called
"doSomething" being called by ! notation in a form submit.
I've noticed that when I annotate the "doSomething" method with:
@Action(results = {...@result(nam
8 matches
Mail list logo