1. Can the convention plugin discover new actions deployed at run-time
via the OSGI plugin? Or is the OSGI plugin going to be responsible
for triggering a re-calculation of the Configuration?
I am not even sure what would happen if you put them together, the
thing is that the both provide implementations for
"com.opensymphony.xwork2.config.PackageProvider" and the order in
which the plugins are loaded is undefined. I guess the question would
be, how do we make convention work on top of OSGi?.
2. Does the ConventionPlugin support the NamedVariablePatternMatcher
(that is, allow params in the namespace "/users/{userid}")? To do it
would be using the PatternMatcher provided by XWork to match
namespaces rather than rolling its own.
Convention just builds the configuration, how the package/actions are
matched on the request is up to xwork. So yes, it would support
wildcards.
3. Is it feasible that an action class could have multiple base
namespaces? That is, I know it's not supported now, but does it seem
a major or minor change? Multiple name spaces would imply multiple
packages are created/joined.
eg. @Namespaces([EMAIL PROTECTED]("/baseA"), @Namespace("/baseB"))
This is something I need but Codebehind can't easily be adapted for it.
As you said, not implemented right now, could be added easily, I
think. I will take a look at it.
musachy
On Wed, May 21, 2008 at 11:49 PM, Jeromy Evans
<[EMAIL PROTECTED]> wrote:
> Apologies I still haven't had a change to look at the convention plugin/rest
> changes yet.
>
> I've got three quick questions about the convention plugin that I can't
> answer without digging deep into the source so I thought I'd put them out to
> others. 1. Can the convention plugin discover new actions deployed at
> run-time via the OSGI plugin? Or is the OSGI plugin going to be responsible
> for triggering a re-calculation of the Configuration?
> 2. Does the ConventionPlugin support the NamedVariablePatternMatcher (that
> is, allow params in the namespace "/users/{userid}")? To do it would be
> using the PatternMatcher provided by XWork to match namespaces rather than
> rolling its own.
> 3. Is it feasible that an action class could have multiple base namespaces?
> That is, I know it's not supported now, but does it seem a major or minor
> change? Multiple name spaces would imply multiple packages are
> created/joined.
> eg. @Namespaces([EMAIL PROTECTED]("/baseA"), @Namespace("/baseB"))
> This is something I need but Codebehind can't easily be adapted for it.
>
> Thanks,
> Jeromy Evans
>
> ---------------------------------------------------------------------
> 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]
