Well, by "convention" these things could be defined in the top most package
of the actions packages (ie. struts.convention.action.packages) in
package-info.java. This seems natural to me.
I would think that at least the default interceptor-ref should be made
available on package-info.java(s) because this would prevent you from having
to create a parallel xml configuration just to house this information.
After all, the namespace annotation is allowed there (which is outside the
action element).
Bob
--------------------------------------------------
From: "Musachy Barroso" <[EMAIL PROTECTED]>
Sent: Sunday, June 08, 2008 10:34 AM
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: [Struts2] Convention Plugin - Annotationd
I think that convention should support everything from the current
xml configuration element "action" down. For things outside action,
like global result, stacks, beans etc, is not really intuitive where
the annotations should be.
musachy
On Sun, Jun 8, 2008 at 10:25 AM, Bob Tiernay <[EMAIL PROTECTED]> wrote:
I am currently trying to convert an existing project over to use the
convention plugin. In, the process I discovered that it appears as though
I
cannot do the following with the annotations:
1. Declare interceptor annotations on package-info.java
2. Set a default interceptor ref (eg. for a package-info.java)
3. Define an interceptor stack
4. Create global results
Perhaps 4. can be done by declaring @Results on package-info.java of my
base
action package?
Anyways, just wondering if these features are of worth. Is one of the
goals
of this plugin to allow for 100% zero xml?
Thanks,
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
