> > 1. <map:action type="SomeActions.doMyAction">
> > <!-- directly use the method -->
>
> Do you mean <map:act>?
ups... sure! ;)
> > 2. <map:action type="SomeActions.MyAction">
> > <!-- have a fix prefix like "do" -->
> >
> > 3. <map:action type="SomeActions" method="doMyAction">
> >
> > 4. <map:action type="SomeActions" method="MyAction">
>
> 5.
> <map:actions>
> <map:action src="com.foo.SomeActions" method="doMyAction"/>
> </map:actions>
>
> <map:act type="SomeActions"/>
Hm... but then you always have to define each method of the
class inside the sitemap plus you have to come up with all
different names. So let's assume we have a usermanager class
public class UserManagerAction extends SomeAction {
public Map doAdd(...) {
}
public Map doUpdate(...) {
}
public Map doDelete(...) {
}
private void commonStuff() {
}
}
Sitemap:
<map:actions>
<map:action name="usermanager-add" src="org.apache..UserManagerAction"
method="doAdd"/>
<map:action name="usermanager-update" src="org.apache..UserManagerAction"
method="doUpdate"/>
<map:action name="usermanager-delete" src="org.apache..UserManagerAction"
method="doDelete"/>
</map:actions>
...
<map:act type="usermanager-add">
...
I think this is much to complicated and verbose for the
sitemap. I see no benefit over:
<map:actions>
<map:action name="usermanager" src="org.apache..UserManagerAction"/>
</map:actions>
...
<map:act type="usermanager.add">
...
Isn't this simple and straight forward?
The "do" prefix could make sure only desire methods can be used
as action from a class.
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
