Speaker

1
(No Transcript)
2
(No Transcript)
3
(No Transcript)
4
Speakers Qualifications

• Peter Pilgrim develops Struts application since
  2001 for top investment banks in London, UK
• Written articles for TheServerSide.com
• Integrated Struts 1.2 into Expresso Framework
• Founded and currently organise the London base
  JAVAWUG
• BSc Sci (Hons) Scientific Computing

5
An Observation

• Remember Rickard Oberg initially created WebWork
  to fix some of the design-deficiencies with
  Apache Struts

6
Struts Community

• Leading MVC Model 2 Web Framework
• The People, The Companies, The Investment
• Healthy Downloads 15000 copies / month
• Cross pollination into other FOSS
• Books, Literature
• Tool Support

7
Struts 1.2.8

• Supports Commons Validator 1.1.4
• Upgrade Commons Validator 1.2 optional
• ActionError is deprecated, use ActionMessage
• RequestUtils deprecated, use TagUtils
• Upgrade Commons BeanUtils to support
  LazyDynaBeans
• Fixes for XSS Vulnerabilties
• ActionServlet Init Parameters move to
  Struts-Config.xml

8
Struts 1.3

• Realignment to Action-Oriented Framework
• Baseline Servlet 2.3 / JSP 1.2
• Integration of Commons Chains
• ComposableRequestProcessor
• Devolution of Struts Tiles to Standalone
• Devolution of Struts Taglibs to separate JARs
• Subprojects Scripting, EL, Flow, JSP Taglibs,
  Tiles

9
Great Debate Struts 2.0

• We, now, have legacy Java!
• Shale? No. Only built on JSF
• Struts Jericho abandoned to /dev/null
• Struggle with Change vs Backward Compatibility
• Productivity advances Ruby-on-Rails
• Struts Titanium is the latest idea

10
Struts Titanium

• Real-world example of consolidation
• Struts has great community and support
• WebWork implemented Actions correctly
• Architecture will be WebWork 2.2 lower levels
• Struts 1.x compatibility layer for migration
• Introduce Request Processor and CoR
• Rejuvenate Action-Oriented Framework with
  productivity gains and intelligent defaulting

11
Struts Ti Gains from WebWork

• WebWork documentation improved
• Focus on a ServletActionContext instead
• Better support for IoC instantiation of actions
• Additional extensions through WW Interceptors
• Better Type Conversion
• Better Custom Tags by using OGNL expressions

12
If You Only Remember One Thing

• Struts 1.3 is not Struts 0.5
• and neither is Java 5 not Java 1.0.
• Progress is inevitable fact of change.

13
Struts 2.0 Architecture
Apache Struts 2.x

• A1

Struts Ti
Compatibility Layer
WebWork 2.2
14
QA
15
References

• Apache Struts http//struts.apache.org
• Statistics http//people.apache.org/vgritsenko/st
  ats/projects/struts
• Upgrade to 1.2 http//wiki.apache.org/struts/Strut
  sUpgrade
• Upgrade to 1.3 http//wiki.apache.org/struts/Strut
  sUpgradeNotes12to13
• Clarity Initiative http//opensource2.atlassian.co
  m/confluence/oss/display/WAG/Clarity
• Java Web Alignment Group http//opensource2.atlass
  ian.com/confluence/oss/display/WAG/Home
• Struts SubProjects http//struts.apache.org/projec
  ts-overview.html
• Struts Jericho http//wiki.apache.org/struts/Strut
  sJericho
• Struts Ti https//www.twdata.org/projects/struts-t
  i
• Struts versus Ruby-on-Rails http//www-128.ibm.com
  /developerworks/java/library/wa-rubyonrails/index.
  html

16
References Continued

• Struts merging with WebWork to become Struts Ti
  http//www.theserverside.com/news/thread.tss?threa
  d_id37794
• WebWork http//www.opensymphony.com/webwork/
• Xwork http//www.opensymphony.com/xwork/
• Commons Chain http//jakarta.apache.org/commons/ch
  ain/
• Beehive http//beehive.apache.org/

17
(No Transcript)