Sorry for the late reply. Busy happenings lately.
Don Brown wrote:
Hmm..I'm a bit leary about this "component" talk. I'd like to keep
Struts 2 simple and I see the goal of this is to define a plugin that:
* Builds configuration based on annotations
* Defines default results when none specified
Components are currently part of core and plugins in general. I'd just
like to formalize this more. I don't think they are out of scope at all
and need to be addressed. Essentially, if I want to ship some actions
and results in a JAR file, I currently just define everything in the
struts-plugin.xml. Pretty straight-forward since Struts finds this file
and loads it up. Well, with the code-behind stuff, we want to get rid of
as much struts XML as we can and therefore we need a mechanism for
locating action packages. Stripes uses naming conventions and I'm fine
with that. SmartURLs uses a component.xml file and I'm fine with that as
well. Either way should work, but I definitely think this is a
requirement because it is fundamentally wired into core. I mean this is
the reason for FreeMarker/Velocity in the first place (in my opinion).
As to the REST stuff, I'm fine either way. My main concern is to address
the URL to class mapping, followed by the result lookup, followed by the
index handling. After that, I'm game for whatever, but I definitely
think things should play nicely together and I should be able to REST an
application with convention based approach.
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
