-1 on removing the action tag. <ww:action/> is VERY useful. Let me give you an example:
My DocumentLoader action pulls up an entire graph of document metadata. This includes "long[] getDocTypes()". However, when I display the document metadata, I don't want to show the info type IDs, I want to show the String names of these IDs in the JSP. I consider this a UI issue, and my DocumentLoader action shouldn't care about showing a String form of this information. It's job is to strictly pull the data from the database. So I solve this using the action tag: <ww:action name="'InfoTypeLoader'"> <ww:param name="'infoTypes'" value="../infoTypes"/> <ww:iterator value="infoTypeStrings"> <li><ww:property value="."/></li> </ww:iterator> </ww:action> 0 or +1 (possibly) on having two tags to replace the PropertyTag. I'll let others give their feedback on this, I don't really care. ----- Original Message ----- From: "boxed" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 30, 2002 10:41 AM Subject: [OS-webwork] xwork suggestions > 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 ------------------------------------------------------- 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
