On Monday 27 April 2009 02:57:29 pm Musachy Barroso wrote:
> Wild cards are different from DMI, from the docs:
>
> "The Wildcard Method feature is implemented differently. When a
> Wildcard Method action is invoked, the framework acts as if the
> matching action had been hardcoded in the configuration. The framework
> "believes" it's executing the action Category!create and "knows" it is
> executing the create method of the corresponding Action class.
> Accordingly, we can add for a Wildcard Method action mapping its own
> validations, message resources, and type converters, just like a
> conventional action mapping. For this reason, the Wildcard Method is
> preferred."
>
> I am not sure that Convention works with wild cards, I have never
> looked into it.
Yes, I see that wildcard-mappins are a different issue. It would, however, be
cool if one could do wildcard-mappins using annotations too. At a first glance
it seems "only" a matter of extending the @Action-annotation with a
"method(String)"-argument analogous to what's in struts.xml, so one could do:
@Action(value = "user_*", method = "{1}")
public class UserAction
Anyway, the class-based @Action(s)-annotations seem to work as expected, good
work and thanks for listening:-)
--
Andreas Joseph Krogh <[email protected]>
Senior Software Developer / CEO
------------------------+---------------------------------------------+
OfficeNet AS | The most difficult thing in the world is to |
Rosenholmveien 25 | know how to do a thing and to watch |
1414 Trollåsen | somebody else doing it wrong, without |
NORWAY | comment. |
| |
Tlf: +47 24 15 38 90 | |
Fax: +47 24 15 38 91 | |
Mobile: +47 909 56 963 | |
------------------------+---------------------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
