Re: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow)

[Erwin V. <erw...@er...>]

Regarding the back button: if your requirements mandate that the user be=20
able to use the back & refresh buttons offered by the browser, SWF is=20
basically out unless you are prepared to go for a continuations based flo=
w=20
storage strategy (e.g. PortletSessionContinuationFlowExecutionStorage). O=
n=20
the other hand, if it is acceptable that use of the back/refresh button=20
leads to an error page that allows the user to restart the flow, you can =
use=20
SWF no problem.


Erwin Vervaet
erw...@er...
----- Original Message -----=20
From: "Steven Devijver" <ste...@gm...>
To: <spr...@li...>
Sent: Tuesday, May 24, 2005 9:18 AM
Subject: Re: [Springframework-developer] Support for state/controller=20
chaining in Portlets? (not quite webflow)


Regarding the WebFlow FAQ entry, this should not be a limitation for
CRUD applications. For example, you should never call the remove
action before you have displayed the related record which is by itself
an example of a workflow. The same for detail screens, you should
first pass through a table view or another detail screen.

I'm not sure about the back button, maybe somebody from the WebFlow
crew could comment on that.

On 5/17/05, Tim Kettering <tim...@vi...> wrote:
>
> Hi everyone,
>
> I'm just throwing this out here to see what other people have to say.  =
I=20
> can
> see from the list that there are a few developers actively working on=20
> portal
> solutions using Spring MVC.  We are starting on our first project using=
=20
> this
> as well, and one of the issues I'm trying to figure out now is the matt=
er=20
> of
> maintaining state in a portlet.
>
> In a typical CRUD example, if we have a portlet to display, edit and=20
> maange
> information about a certain object, like a Book. We'd have view, edit a=
nd
> delete functionality for example.
>
> In a typical non-portlet webapp, we could easily split those up across
> different servlets for fine-grained areas of responsibility.
>
> But it's not as simple with portlets, because there are limitations on=20
> what
> can be done, and essentially, all requests would need to go thru a sing=
le
> portlet configuration.
>
> So, it no longer become sufficient to configure a simple portlet=20
> controller
> for a portlet.  There needs to be a way to maintain state and to delega=
te
> the request/response process to different types of controllers dependin=
g=20
> on
> the state.  Like a View page would need to go thru a derivation of
> BaseCommandController, an Edit page would go thru SimpleFormController.
>
> And not to mention adding yet another dimension when considering portle=
t
> modes as well!
>
> This article at IBM Developerworks pretty much covers the same issue I =
am
> bringing up:
>
> http://www-106.ibm.com/developerworks/websphere/library/techarticles/03=
12_ha
> nis/hanis1.html
>
> I did look at Spring's WebFlow a few days ago to see if it could addres=
s=20
> our
> issue, but in the Webflow FAQ, it pretty much states that WebFlow shoul=
d=20
> not
> be used in cases where the user will be using back-button, or=20
> indeterminate
> actions not within a strict flow.
>
> So that kinda leaves me back at square one.  After some discussion with=
 my
> co-worker, I would imagine that this is a common problem for any Spring
> portlet developer creating more than just simple portlet functionality.=
=20
> And
> that as Spring portlet support matures, this will be a more common issu=
e=20
> for
> everyone.  Hence this email to the list.
>
> I'm now wondering how some of you have addressed this problem, and whet=
her
> there is a need for Spring's portlet support, to be in Spring 1.3 to=20
> include
> some way to configure and facilitate a state process, maybe even based =
on
> WebFlow's state machine - although I have only given WebFlow's state
> functionality a brief look.
>
> Thanks in advance,
>
> -tim
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=3D7412&alloc_id=3D16344&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>


--=20
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id=16344&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer