Sorry, what do you mean "non-terminals that *act* like terminals."?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joseph Ottinger Sent: Tuesday, September 23, 2003 12:24 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Hyperlink best practices - use of actions I do it. I have a url attribute in a "base action," and my browse.action uses it from the valuestack, as it's set by non-terminals that *act* like terminals. On Tue, 23 Sep 2003, Robert Douglass wrote: > I have another question on how people organize the navigation within their > apps. First a use case: > > login -> homepage -> account details -> change password > > >From what I have understood so far, a typical WW application would have > > login.action -> homepage.action -> account.action -> and changePass.action > > Each action would build up the context or offer a model in anticipation of > the page to come. Homepage.action would offer a UserBean as a model, and > account.action would offer an AccountBean, or something similar. Xork.xml > would specify that homepage.success = account.jsp, and homepage.login = > login.jsp. This is what I understand to be the typical approach from reading > the docs, examples and mailing list. > > To me, however, I tend to see the use case above as the following set of > actions: > > login.action, browse.action -> browse.action -> browse.action -> > changePass.action, browse.action > > login.action has no view, browse.success = some sort of forward, > changePass.success has no view. > > In other words, things like logging in and changing account details always > chain to a browse.action. Browse.action would expect to receive at the > minimum an id of some sort and a template name of some sort, from which it > would build a URL and redirect or forward the request to it. > > I haven't implemented this yet, as I'm still discovering the ins and outs of > basic WW2 usage. The question is, though, does anybody else do business this > way? If so, how did you implement it? > > -Robert Douglass > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Robert Douglass > Sent: Tuesday, September 23, 2003 7:58 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Hyperlink best practices > > > Hello, > I'm looking for code examples of how people build their hyperlinks in > WW2/JSP view. The examples in the distribution don't really address this, > and the ww:url tag seems to be more of an encoding helper than the beginning > of a solution to generating dynamic anchor tags. What I'd ideally like is a > <ww:anchor> tag: > > <ww:anchor href="ognl.here" target="'_top'" encode="true|false"> > <ww:param/> > </ww:anchor> > > I'm sure that this problem has been solved a hundred times and I just > haven't comprehended it yet. > > -Robert Douglass > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------------------- Joseph B. Ottinger http://enigmastation.com IT Consultant [EMAIL PROTECTED] J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
