see intermixed > -----Original Message----- > From: Ian Roughley [mailto:[EMAIL PROTECTED] ==////== > > > The ww:action is not used for AJAX interactions with the > server. There
Ok that is cool to know. > are several UI widgets that can be AJAX enabled - the one you > would be > looking for is the remote DIV. But, this would be most helpful in a > webwork application to make it portlet-like, not sure how it > would help > when deployed into another porlet container. > Yep you are right. The AJAX request has to asynchronously make it through the portlet container/server to the target web application. Oh, I suppose we could make the portlet a read-only one for the initial phase. In other words we could come that decision when and if we ever get there. > /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: > > >See intermixed > > > > > > > >>-----Original Message----- > >>From: Michael Jouravlev [mailto:[EMAIL PROTECTED] > >>Sent: Tuesday, February 21, 2006 7:02 PM > >>To: Struts Users Mailing List > >>Subject: Re: Action Oriented Framework Rendering Mode > >> > >> > >>On 2/21/06, Pilgrim, Peter <[EMAIL PROTECTED]> wrote: > >> > >> > >>>>>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. > >>>>> > >>>>> > >>Do you mean any portlets or JSR-168 portlets? > >> > >> > >> > >Actually I am unsure of the portlet world. > >I believe the target server is going to be a Weblogic Portal server. > >So I am assuming it will be JSR 168 portlets. > >Does this make a huge difference? > > > > > > > >>>>>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. > >>>>> > >>>>> > >>>>>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. > >>> > >>> > >>How about this as food for thought: http://jspcontrols.sourceforge.net >> >> >> > >>From the book WebWork in Action, I believe Webwork can implement >some aspect of a page controller methodolody, by using the ><ww:action> tag inside a JSP. In this way a WW action can >render a portion of the view. What I dont know is if you can >use the <ww:action> tag to render AJAX components i.e. >AJAX styled box out or dependency list drop downs. > >BTW: The JSP Control live examples look nice. > >Thanks > -- 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]
