From: Brian Pontarelli <[EMAIL PROTECTED]>
Eric,
SmartURLs (and the zero-config/code-behind) provides a property
that seems like what you need. SmartURLs property is named:
smarturls.action.default.parent.package
which sets the default parent package for all actions that don't
provide something else. I think the zero-config/cobe-behind is
something similar and I can find it if you need. Is that what you
are looking for?
I couldn't find anything in either zero-config or code-behind, but
the SmartURLs looks like exactly what I need now. However I think
your followup on the JIRA issue outlines the more complete long term
solution. Single application default, per package override, per
class override.
But I'm not sure an annotation based approach can/should work for the
per-package override. AFAIK you can't annotate packages, which is
why I was suggesting the "actionPackage" property of an XWork package
as the middle configuration override. Alternatively you'd have to
introduce an "XworkPackage" interface that people can implement as a
place to hang the annotation, but I can't think of any useful
introspection conventions/coding use for such a beast. Yes you could
also hang interceptors, interceptor stacks, global results, etc, but
in the absense of something intrinsicly better/easiesr than XML it
doesn't seem worth it... Perhaps anonymous inner class based
interceptors, perhaps static constants for global results.... but its
still not easier... simply annotations for annotations sake, which
wouldn't be a good thing. It might be possible to hang annotations
on the java (as opposed to html) style Javadoc package overview file,
but that sounds very strained to me...
Thanks.
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
