Menu
▾
▴
RE: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow)
|
From: Boyce, K. G. <Kei...@bc...> - 2005-05-24 20:25:05
|
The is no current method to just automatically restart the flow right?=0D -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Erwin Vervaet Sent: Tuesday, May 24, 2005 4:08 PM To: spr...@li... Subject: Re: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow) From the JavaDoc: * A downside of this storage strategy (and of server-side continuations in * general) is that there could be many copies of the flow execution stored in * the portlet session, increasing server memory requirements. * <p> Erwin Vervaet erw...@er... ----- Original Message ----- From: "Boyce, Keith Garry" <Kei...@bc...> To: <spr...@li...> Sent: Tuesday, May 24, 2005 9:54 PM Subject: RE: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow) What's the disadvantage to using PortletSessionContinuationFlowExecutionStorage? -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Erwin Vervaet Sent: Tuesday, May 24, 2005 3:55 PM To: spr...@li... Subject: Re: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow) Regarding the back button: if your requirements mandate that the user be able to use the back & refresh buttons offered by the browser, SWF is basically out unless you are prepared to go for a continuations based flow storage strategy (e.g. PortletSessionContinuationFlowExecutionStorage). On the other hand, if it is acceptable that use of the back/refresh button leads to an error page that allows the user to restart the flow, you can use SWF no problem. Erwin Vervaet erw...@er... ----- Original Message ----- From: "Steven Devijver" <ste...@gm...> To: <spr...@li...> Sent: Tuesday, May 24, 2005 9:18 AM Subject: Re: [Springframework-developer] Support for state/controller 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 can see from the list that there are a few developers actively=0D > working on portal solutions using Spring MVC. We are starting on our=0D > first project using this as well, and one of the issues I'm trying to=0D > figure out now is the matter of maintaining state in a portlet. > > In a typical CRUD example, if we have a portlet to display, edit and=0D > maange information about a certain object, like a Book. We'd have=0D > view, edit and 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 > what can be done, and essentially, all requests would need to go thru=0D > a single portlet configuration. > > So, it no longer become sufficient to configure a simple portlet=0D > controller for a portlet. There needs to be a way to maintain state=0D > and to delegate the request/response process to different types of=0D > controllers depending 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=0D > portlet 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/0 > 312_ha > nis/hanis1.html > > I did look at Spring's WebFlow a few days ago to see if it could=0D > address our issue, but in the Webflow FAQ, it pretty much states that=0D > WebFlow should not be used in cases where the user will be using=0D > back-button, or indeterminate actions not within a strict flow. > > So that kinda leaves me back at square one. After some discussion=0D > with my co-worker, I would imagine that this is a common problem for=0D > any Spring portlet developer creating more than just simple portlet functionality. > And > that as Spring portlet support matures, this will be a more common=0D > issue for everyone. Hence this email to the list. > > I'm now wondering how some of you have addressed this problem, and=0D > whether there is a need for Spring's portlet support, to be in Spring > 1.3 to include some way to configure and facilitate a state process,=0D > maybe even based on WebFlow's state machine - although I have only=0D > 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=0D > 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=0D > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- "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 ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=3Dfad-ysdn-ostg-q22005 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=3Dfad-ysdn-ostg-q22005 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=3Dfad-ysdn-ostg-q22005 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. |
