I have two suggestions for XWork that I think are very important. 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? 2) In WW the property tag does two things. The first is that it acts much like a change directory, and the second is that it prints the item you specify. Having the same command for these totally different tasks is rather counterintuitive and doesn't help the code readability of PropertyTag. I propose <xw:property> and <xw:print> (or other better names if you have them) as a replacement for the dual functionality of <ww:property>. // Anders Hovmöller ------------------------------------------------------- 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
