Comments on: The Spring Web Flow 2.0 Vision http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/ The voice of SpringSource Thu, 21 Aug 2008 01:33:04 +0000 http://wordpress.org/?v=2.0.11 by: 乙� http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-105495 Wed, 07 May 2008 00:34:11 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-105495 Why can't I see? Why can't I see?

]]> by: Double J http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-100532 Wed, 12 Mar 2008 20:02:28 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-100532 Hi Keith!!! Only to tell you that It's very exciting this release, has an excellent concept about the integration with AJAX and will be good use this feature by separated or in SpringMVC... I will be following you in your job to put more comments about this part of the Spring's portfolio... "Have a good hands for a good code..." Thks for readme and congratulations... Hi Keith!!!
Only to tell you that It's very exciting this release, has an excellent concept about the integration with AJAX and will be good use this feature by separated or in SpringMVC…
I will be following you in your job to put more comments about this part of the Spring's portfolio…
"Have a good hands for a good code…"
Thks for readme and congratulations…

]]> by: Development Management Consultants http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-96777 Tue, 05 Feb 2008 11:17:10 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-96777 <strong>IT Consultant: How To Manage Your Time During Start Up</strong> As an IT consultant looking to go solo, how you can cut through the information overload so you can tune out the distractions and focus on only the most relevant, critical tasks for starting up a business? You need to first realize you may need to stop... IT Consultant: How To Manage Your Time During Start Up

As an IT consultant looking to go solo, how you can cut through the information overload so you can tune out the distractions and focus on only the most relevant, critical tasks for starting up a business? You need to first realize you may need to stop…

]]> by: diziler http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-87986 Sun, 13 Jan 2008 16:49:10 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-87986 Thanks for Work, good achievement Thanks for Work, good achievement

]]> by: Keith Donald http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-80051 Tue, 18 Dec 2007 23:11:51 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-80051 Hi Anantha, Sorry for the delay in the response. In general, I would recommend going with Spring Web Flow 1.0.5 for now until 2.0 enters stabilization as part of its release candidate phase in February, then begin planning your 1 to 2 migration then. You can expect 2.0 to introduce a new, simplified variant of the XML-based flow definition syntax in the M4 release; however, the 2.0 series will retain full support for the 1.0.x syntax throughout to ease migration. You can also expect a 1.0 to 2.0 migration guide to be published at that time. An exception to this general recommendation would be if you are using Web Flow with JSF.  If you are doing this, I would recommend adopting the 2.0 line from the start, as the JSF integration approach is much improved in 2.0 than 1.0. You definitely shouldn\'t feel bad about using 1.0 - its solid, and the migration to 2.0 will be straightforward. Keith Hi Anantha,

Sorry for the delay in the response.

In general, I would recommend going with Spring Web Flow 1.0.5 for now until 2.0 enters stabilization as part of its release candidate phase in February, then begin planning your 1 to 2 migration then. You can expect 2.0 to introduce a new, simplified variant of the XML-based flow definition syntax in the M4 release; however, the 2.0 series will retain full support for the 1.0.x syntax throughout to ease migration. You can also expect a 1.0 to 2.0 migration guide to be published at that time.

An exception to this general recommendation would be if you are using Web Flow with JSF.  If you are doing this, I would recommend adopting the 2.0 line from the start, as the JSF integration approach is much improved in 2.0 than 1.0.

You definitely shouldn\'t feel bad about using 1.0 - its solid, and the migration to 2.0 will be straightforward.

Keith

]]> by: Paul http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-80035 Tue, 18 Dec 2007 21:16:07 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-80035 Anantha, springframework.org says, Spring Web Flow 2.0 final is due out in March of 2008. I would suggest that you go with SWF 2.0. Regards, Paul Anantha,

springframework.org says, Spring Web Flow 2.0 final is due out in March of 2008. I would suggest that you go with SWF 2.0.

Regards,
Paul

]]> by: Anantha http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-76471 Thu, 06 Dec 2007 15:23:39 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-76471 Keith, We are on the verge of beginning a large project in my team that is expected to be delivered by the end of 2008.Having decided to program the web app based on spring web flow, we now have to decide whether to being the development based on Spring web flow 1.0.5 or should we start with web flow 2.0. We now have to publish the development standards within few days.Request you to throw some light on the expected timeframe for production release of Spring web flow 2.0.Any guidance will be appreciated. Thanks Anantha Keith,
We are on the verge of beginning a large project in my team that is expected to be delivered by the end of 2008.Having decided to program the web app based on spring web flow, we now have to decide whether to being the development based on Spring web flow 1.0.5 or should we start with web flow 2.0. We now have to publish the development standards within few days.Request you to throw some light on the expected timeframe for production release of Spring web flow 2.0.Any guidance will be appreciated.

Thanks
Anantha

]]> by: Victor http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-74995 Sun, 02 Dec 2007 04:55:59 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-74995 What skills and tools does a nonprogrammer (albeit one with very good computer expertise) need to write, modify and manage page flows within an application developed in the Spring framework? What skills and tools does a nonprogrammer (albeit one with very good computer expertise) need to write, modify and manage page flows within an application developed in the Spring framework?

]]> by: Shoaib http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-73663 Thu, 29 Nov 2007 15:11:29 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-73663 Keith, Thanks for reply. I have looked the javadocs and wondering that Can we inject Transaction manager inside the HibernateFlowExecutionListener and use Flush mode manual?. That way we can avoid flushing the session in btw the flow execution and at the last step of flow we can flush the session ourself. And by the way it is the recommneded way by Hibernate folks they dont say that you should not use transactions 9 i know with JPA its a standard way) but with Hibernate there is almost no issue at all and that is what i believe seam is doing as personally i am against not using transaction. Can you explain why? Best Regards, Shoaib Keith,
Thanks for reply. I have looked the javadocs and wondering that Can we inject Transaction manager inside the HibernateFlowExecutionListener and use Flush mode manual?. That way we can avoid flushing the session in btw the flow execution and at the last step of flow we can flush the session ourself. And by the way it is the recommneded way by Hibernate folks they dont say that you should not use transactions 9 i know with JPA its a standard way) but with Hibernate there is almost no issue at all and that is what i believe seam is doing as personally i am against not using transaction. Can you explain why?

Best Regards,
Shoaib

]]> by: Keith Donald http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-72445 Tue, 27 Nov 2007 20:52:46 +0000 http://blog.springsource.com/main/2007/11/15/the-spring-web-flow-20-vision/#comment-72445 Shoaib, Checkout the documentation for HibernateFlowExecutionListener or JpaFlowExecutionListener. Essentially data access occurs non-transactionally until the flow enters a commit state, at which any changes to managed entities are flushed in a transaction. With that said, you can perform read-only transactional access using Hibernate during intermediate steps of a conversation by demarcating @Transactional at your service layer. This is not supported with JPA, however. Keith Shoaib,

Checkout the documentation for HibernateFlowExecutionListener or JpaFlowExecutionListener. Essentially data access occurs non-transactionally until the flow enters a commit state, at which any changes to managed entities are flushed in a transaction. With that said, you can perform read-only transactional access using Hibernate during intermediate steps of a conversation by demarcating @Transactional at your service layer. This is not supported with JPA, however.

Keith

]]>