블로그 이미지
Max.

calendar

    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    

Notice

'여유'에 해당되는 글 1

  1. 2008.03.12 Spring Web Flow 2.0 M4 Released
2008.03.12 09:52 이전글(~2009)

요즘 일에 빠졌다. 일에 빠졌다는 말은 대부분의 가용시간을 일(회사에서 진행하는 업무)하는 재미에 써버리게 된다. 나의 일정한 시간(19시 이후)을 자기계발이나, 신기술 모니터링하는 시간이 줄어들었다는 이야기이다. 이렇게 되니 내 스스로가 너무 바쁜상태를 유지하게 된다. 여유가 없어졌다. 일에서 자기계발에 대한 만족도를 높여주는 방법이 있다. 바로 신기술 도입을 시도하는 프로젝트를 하는 것이다.(이것이 가끔 도박에 가깝다는걸 안다.)

오래전부터 Spring Web Flow를 꼭 실무에 적용해 보고 싶은 생각이 있었는데, 이번 프로젝트에 적용할 생각을 못했다.(약간 여유가 있는 프로젝트인데 말이다.- 바보다 -_-;) 오늘 Spring 홈페이지에 2.0 M4가 릴리즈 되었다는 포스트를 보고 '아차'하는 소리를 질렸다.

[Spring Web Flow 2.0 M4 Released 내용 복사]

Dear Spring Community,

We are pleased to announce that Spring Web Flow 2.0 M4 is now available.  Download | Documentation

This release firms up the Web Flow 2 architectural model, including how SWF 2 integrates with Spring MVC, JavaServerFaces, and Ajax.  It also introduces many new features and improvements, including:

2.0 M4 New and Noteworthy

  • The introduction of a simplified XML flow definition syntax.   See the Spring Travel reference application for an example of the new syntax.
    • Use of the version 2 syntax reduces the size of a version 1 flow definition by up to 50%.  As an example, Spring Travel 1.0.5 consists of ~200 lines of flow-application code across six artifacts.  The latest 2.0 M4 version consists of 93 lines of code across two artifacts, a 50% reduction with four less files to maintain. 
    • Savings are achieved primarily by stronger Expression Language (EL) integration and simpler tags for action execution and data mapping.
  • Spring Security integration.  Full support for securing flows, states, and transitions is provided.
    A new "currentUser" EL variable makes it easy to reference the authenticated Principal from a flow definition or view template.
  • Flexible support for flow exception handling inside Spring MVC, including default support for automatically restarting ended or expired flows.
  • Support for handling Ajax events that do not change the current page.  A new "render" element allows you to selectively re-render fragments of a page after handling an Ajax event.
  • View variables. A view variable allocates when its containing view-state enters and goes out of scope when the state exits.  These variables provide a page context and are particularly useful for updating a model over a series of Ajax requests from the same page.
  • @Autowired flow variables.  Flow variables may now have their dependencies @Autowired by Spring, enabling them to hold references to Spring-managed @Services.   References to services are automatically re-wired for you between requests after variable deserialization.
  • Support for popups.  Mark a view-state with popup=true and it will render in a modal popup dialog when Javascript is enabled on the client.
  • The factoring out of a Javascript abstraction layer called "Spring Javascript" from Web Flow's JSF support.  Currently, Dojo and Ext based implementations of this layer are provided.  Spring.js provides:
    • A common interface for Ajax, regardless of which toolkit is being used under the covers
    • An aspect-oriented-like API for decorating HTML DOM nodes with behaviors, including client-side validation behaviors.
  • A small JSF component library that uses Spring.js underneath to progressively enhance Spring web applications using JSF.  This library degrades if Javascript is not available on the client.  See the Spring Travel example for an illustration: turn Javascript off and compare the application to when Javascript is turned on.
  • Support for rendering JSF views in a standard Spring MVC environment.  This enables Facelets templates to be rendered by plain Spring MVC Controllers as well as Flows.

Please see the Spring Travel reference applications included in the release for practical demonstrations of all these features.  The reference projects are directly importable into Eclipse as Dynamic Web Projects.

1.x Compatibility

A special note to existing Web Flow users: The upcoming 2.0 RC1 will provide support for version 1 flows in a version 2 environment.  This will allow 1.0.x flows to run unchanged along side version 2 flows in the same application.

For more information, see the full Web Flow 2 ChangeLog and RoadMap.  We also encourage you to visit our support forums and JIRA system to provide your feedback on M4 to the development team.

Enjoy!  2.0 final is right around the corner.

Keith Donald
Web Flow Technical Lead
SpringSource




 

신고
posted by Max.
prev 1 next

티스토리 툴바