See inter mixed > -----Original Message----- > From: Ian Roughley [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 21, 2006 3:58 PM > To: Struts Users Mailing List > Subject: Re: Action Oriented Framework Rendering Mode > > > below. > > /Ian > > -- > From Down & Around, Inc. > Innovative IT Solutions > Software Architecture * Design * Development > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > web: www.fdar.com > email [EMAIL PROTECTED] > phone: 617.821.5430 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > Pilgrim, Peter wrote: > > >Hi All > > > >What is the state of play with WebWork / Struts Action 2.0? > > > >I am trying to come up with a design / architecture / proposal > >for a new aspect of an enterprise project. > > > >I have been reading the WebWork in Action book, and I have come > >to the conclusion that it is best to start a brand Action-Oriented > >framework using WebWork 2.2. I found the design decisions in the > >book to really solid, and not fanciful. Especially like the > >decision to use OGNL as the EL. > > > >I have a requirement to possibly build a new web application to > >support portlets and also be displayable in a standard Java EE > >webapp server in the future. Does WebWork 2.2 support portlets? > > > > > > > Yes - action can be used as portlets in various web > containers. This is > realitively new, so check the wiki at wiki.opensymphony.com for the > latest information. >
Great Webwork can support portlets, and of course from the book it can easily divorce itself from PortletRequest and PortletResponse interfaces! > >Basically it looks like the web application has to > >support two view styles. > > > >One style is the classical Tiles and regionalisation of the > >JSP view. For instance you would have a corporate header, > >footer, a navigation menu and a content area. This is something > >that every web developer like myself has done over the > >last five years. > > > >The other style is to chuck all the extra tiles stuff away like > >the header, portal and menu system. For the portlet view > >just render the content region. The content > >view is the same as it would with the Tiles regions. > > > >What I want to know is this architecturally possible to > >develop with WebWork now or is this on the book of work > >to do? > > > > > I'm not a tiles expert, so I can't help you there. But using > sitemesh, > I believe you can specify a URL parameter that sitemesh can > interpet and > change the decoration of the page to a "plain" / non-decorated look. > Alternatively, you could provide a secondary mapping in the > configuration files for the portlet view - this would be good > for if the > portlets are a subset, otherwise it may be alot of work. > Tiles is the wrong way to go for a filtered look. I will look at SiteMesh. I am sure I have a big old Red Wrox Book with a chapter on SiteMesh. "JSP Site Design?" is the probable title and rings a bell with me. Cheers > >I have called this a ``style'', but now I come to think > >of it ought to be called a ``mode'' as in mode of (render) > >employment. > > > >Thoughts are most welcome, even from the Component-oriented people. > > Any more ideas more than welcomed. > >Thanks in advance > > -- Peter Pilgrim :: J2EE Software Development & Architecture Operations/IT - Credit Suisse Group - "One Bank", Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom Tel: +44-(0)207-883-4497 :::: peter dot pilgrim at credit-suisse.com :::: ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
