view state vs. physical view

[victorB]

Hello there,

I have a simple flow in mind but I am not sure whether it will work as spring webflow?
lets say my webflow starts with view state A. I would like to maintain webflow just by sitting in that view state A while allowing arbitrary navigation to different pages/views. So the latter navigation is not defined/declared in the webflow but is rather performed by spring MVC view resolvers or by Struts action mappings. My webflow will terminate when the user logs off or user session timeouts. Question - whether I will be able to maintain conversation ID through out navigation that is not declared as part of webflow?

thanks
victor

[dr_pompeii]

Hello

With the best intentions, read first this
Spring Web Flow Reference Guide

BTW Struts is out of date. Even with Struts 2 keep the things simple.

BTW you can work with Spring MVC + SWF in peace

[victorB]

Hi Manual

thank you for your reply and for referring me to the user guide documentation. I just wanted to clarify what I am trying to achieve. We have a large application that is using different MVC frameworks, including Spring MVC and spring webflow, Struts like home grown framework, JSF etc. The application consists of dozens of different transactional scenarios origniated form the same central home page (hub). What we discovered lately that if we use IE8 we may end up with concurrent access to the same transaction due to the session sharing between IE8 instances and/or tabs. In order to avoid that, we would like to wrap the entry point - hub page as a webflow and maintain transaction ID that will distinguish between access to application from different instances of IE8 or different tabs so we can avoid concurrent access to the same unit of work (same transactional scenario).
Ideally, it would be nice to convert the entire application into hierarchical webflow (with main flow, subflows etc.) but this is not feasible at the moment. So my original question was that if I could just use the home page as a view state and leave the dozens of scenarios originating from that page "as-is" (not declaring that navigation as webflow), yet maintaing conversation ID throughout the entire navigation?

I hope I clarified my question and I look forward to hear your thoughts,
cheers
victor

[dr_pompeii]

Hello Victor

I just wanted to clarify what I am trying to achieve. We have a large application that is using different MVC frameworks, including Spring MVC and spring webflow, Struts like home grown framework, JSF etc.

All these differents frameworks used in one project? I cant believe it!

What we discovered lately that if we use IE8 we may end up with concurrent access to the same transaction due to the session sharing between IE8 instances and/or tabs.

BTW, FF, Opera and Chrome has tab pages too. So the problem could be in any Web Browser

In order to avoid that, we would like to wrap the entry point - hub page as a webflow and maintain transaction ID that will distinguish between access to application from different instances of IE8 or different tabs so we can avoid concurrent access to the same unit of work (same transactional scenario).

OK, I understand your concern

If you are talking about SWF. For each Flow Process in N tab pages, each one should be a unique and isolated flow execution.

Ideally, it would be nice to convert the entire application into hierarchical webflow (with main flow, subflows etc.) but this is not feasible at the moment.

Well you should speak carefully with your team. I dont see other solution.

So my original question was that if I could just use the home page as a view state and leave the dozens of scenarios originating from that page "as-is" (not declaring that navigation as webflow), yet maintaing conversation ID throughout the entire navigation?

Sorry I dont understand your context. Do you mean that the home page should be the first state of the flow and from there call or use the other dozens of scenarios like sub flows?