On Monday, November 4, 2002, at 06:45 PM, Patrick Lightbody wrote:
I disagree. You have yet to ask for any functionality that can't be handled by the current configuration formats, either actions.xml or views.properties.I believe I've nailed down, in words, why the current configuration is sub-optimal. The Configuration object uses a single method:
Could the configuration be more graceful internally? Sure. So what? It works right now (or used to) and all the implementation details are hidden from the enduser. Why are you fixating on this when we have stuff that's actually broken?
As you can see, not only is the view mapping but also the CommandAware stuff
(something inherently built in to ActionSupport only, meaning it shouldn't
be in core configuration stuff). This is a very flat structure. It also
doesn't leave room for allowing us to specify parameters for our actions. An
example of this is:
You may know your ass from an Action, but you sure don't know a View from an Action. You model (Action) doesn't know it's being displayed right? It could be in an email or a webpage or whatever, so SendEmail is a view technology. This is no different than JSP, Velocity, or Jasper. So you should be passing parameters to a View, not an Action.
Say I have a SendEmail action. I want to be able to use the aciton in
various places. It sends generic emails out, so I want to re-use it. A
parameters to be passed in would be the "subject", as well as the "message"
body. I'd be very nice to be able able to alias SendConfirmationEmail and
also SendPasswordEmail:
SendConfirmationEmail would be mapped to SendEmail but would have two
paramters auto set (as in my code doesn't need to do this): subject and
message. Same goes for SendPasswordEmail.
(If this really is a single Action, and you haven't separated your View, just use inheritance to change your subject.)
Let's say for the sake of argument that you have configured SendMail to function as a View and are going to do this by returning a result that points to it. I.E. it's logically functioning as your View technology and sending out emails. Here's your configuration:
<action alias ="sendPasswordEmail" name ="GetUserInfo">
<view name="success"> SendEmail.action?subject=Your Password</view>
</action>
<action alias ="sendConfirmationEmail" name ="GetUserInfo">
<view name="success"> SendEmail.action?subject=Confirmed</view>
</action>
This you can do today. We can put sugar on it in the next major release.
<action alias ="sendPasswordEmail" name ="GetUserInfo">
<view name="success" target="SendEmail.action">
<param name="subject" value="Your Password/>
</view>
</action>
Explain to me again, what new functionality are you bringing to the table?
-Maurice
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
