On 10/4/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote:
> We have a search where the user can select whether he gets the result
> as a gallery (many pics, few content), data summary ( less pix, more
> content) and list (no pics, only content). They are produced by
> different jsp pages (using tiles for same parts) but considered one
> "result page".
This is what I do too. I mean, many pages by one action.
> there is always a separate path (mapping) for each use-case (which can
> map to the same action class, but still considered different action,
> at least virtually), and each use-cases has one "page" assigned to it.
> In reality it could be 5 possible JSP choosen alternatively by the
> action, but it still one "result page".
This is what I don't do. I prefer to have less actions, usually
stateful. I pass parameter to it or submit a form, and it selects a
proper view. But I guess you are right: I am able to google static
html pages for my live samples, that precede my actions. But google
does not show the actions (*.do) themselves. My actions show different
content on GET, and accept POST as well.
I don't think this is a huge issue. If I had a large website, I think
I would have some static pages anyway.
On 10/5/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> But the basic mechanisms regarding the whole page flow system are very similar
> in jsf and struts
Please correct me if I am wrong, but in JSF I always ask for a page.
In Struts I can ask for any arbitrary service, then Struts action
would generate output (if any) itself, and return null. This is more
flexible.
> although I have to admit (please do not beat me for that ;-) )
> the JSF syntax and handling with possible optional combined controller-model
> and binding patterns
> is easier to understand than the struts system for people being used to
> classical non html ui
> programming also it is more suitable for easy to handle stateful
> scope systems, like Seam proves.
For me, "classical non html ui programming" includes a message loop
;-) Anyway, Struts does not have to be cryptic. How do you like this
syntax:
<component path = "/Home"
type = "org.acme.HomeAction"
view = "/pages/home.jsp">
<event name = "logon" path = "/Logon.do"/>
<event name = "signup" path = "/Registration.do"/>
</component>
If I have more than one view generated by one action, I can use
slightly different syntax:
<component path = "/Logon"
type = "org.acme.LogonAction"
form = "LogonForm">
<event name = "error" path = "/Logon.do" />
<event name = "success, cancel, logout" path = "/Home.do" />
<render name = "notloggedin" path = "/pages/logon.jsp" />
<render name = "loggedin" path = "/pages/logoff.jsp" />
</component>
It is the same old Struts Classic, enhanced with custom ruleset class ;-)
Michael Jouravlev.
--
Struts Dialogs
http://struts.sourceforge.net/strutsdialogs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
