On Wednesday, October 30, 2002, at 01:41 PM, boxed wrote:
I have two suggestions for XWork that I think are very important.Huh? Why is this a bad reason? Having the action tag means you could point to regular jsp pages that are webworked, rather than pointing to the action. It makes migrating to webwork much smoother. It's a useful tag and if one doesn't like it, then one shouldn't use it. I don't really agree with the mentality behind this suggestion, of harming users and breaking their apps just because someone happens to dissaprove of the way in which they used webwork. Another use is if you want to support multiple dynamic views all using a single action, and have an admin UI to handle this. Removing this tag would mean that no such UI can exist, as it would have to modify the view mappings file, which would be akin to having a webapp that contains an admin UI to modify it's own web.xml. Not cool.
1) Remove the action tag.
2) The property tag does two things in WebWork, in XWork we should have two
tags, one for each thing.
1) The first one is simple enough. The action tag only removes the loose
coupling between the action(s) and the view, which is counterproductive.
Only reason to do this as far as I know is to remove the need to edit your
view mapping file, and this is a very bad reason. Is there some other reason
for it that I am not aware of?
Hani
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
