|
From: William G. T. Jr. <wg...@ru...> - 2004-04-14 13:15:40
|
this also might help... http://exo.sourceforge.net/multiproject/exo-portlet-framework/index.html Dmitriy Kopylenko wrote: > Here what the eXo platform did with Bridges/Adapters approach: > http://exo.sourceforge.net/bridges-intro.html (the source code is available) > > Regards, > Dmitriy. > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf Of > Alef Arendsen > Sent: Wednesday, April 14, 2004 5:40 AM > To: spr...@li... > Subject: RE: [Springframework-developer] Portlet and JSFs > > > Ok, back in town ;-). > > I think an approach of making the context available is a good first step. > From there later on we could possibly extend things to include mappings > based on portal mode, window state and maybe other criteria. But since I'm > seeing a lot of code getting duplicated if we go ahead there, I want to take > things slowly to see what the other options are. > > To get the context available, I think it's best to create something like a > FrameworkPortlet (similar to the FrameworkServlet). This allows for further > extension later on (possibly the creation of a DispatcherPortlet if we need > it). > > So: FrameworkPortlet extends PortletBean extends GenericPortlet, > offering the same functionality as the FrameworkServlet. I think extending > ApplicationContext to get a PortletApplicationContext is needed as well, to > allow for access to the PortletContext (instead of the ServletContext). > > This is the approach I've been taking last time I spent time on it. If we > can continue this discussion a bit to see what everybody thinks, then I'll > probably be able to implement something tomorrow, Friday and over the > weekend (got some stuff lying around already so it shouldn't be that hard). > > Regards, > Alef > > > >>-----Original Message----- >>From: spr...@li... >>[mailto:spr...@li...] On >>Behalf Of William G. Thompson, Jr. >>Sent: Wednesday, April 14, 2004 1:30 AM >>To: spr...@li... >>Subject: Re: [Springframework-developer] Portlet and JSFs >> >>jürgen höller [werk3AT] wrote: >> >>>But what criteria do you base your dispatching on when there's no >>>URL? >> >>Request parameters? >> >>yes, plus perhaps the Portal Mode (edit,view,help,...) and maybe some >>state... >> >>and of course the other tricky bit is the two step >>call...ActionRequest/Response and then some time later the >>RenderRequest/Response. >> >> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im >>>Auftrag >> >>von Eduardo Issao Ito >> >>>Gesendet: Di 13.04.2004 22:15 >>>An: spr...@li... >>>Betreff: Re: [Springframework-developer] Portlet and JSFs >>> >>> >>> >>>jürgen höller [werk3AT] wrote: >>> >>> >>>>>Portlets can not access the URL that the client used to initiate >>>>>the >> >>request on the portal. >> >>>> >>>>While that makes sense, it effectively makes me wonder whether we >>>>need a >> >>Portlet dispatcher: With Servlets, dispatching is all about flexible >>URL mapping. AFAIK, Portlets have doView, doEdit etc callbacks, >>similar to doGet, doPost, etc from the Servlet API. >> >>>>So for typical Portlets, it's probably most important to allow for >>>>easy >> >>access to Spring facilities from those methods, rather than dispatch >>to some other components from a Portlet doView method. Portlet support >>classes similar to the ones I just added for Struts come to my mind. >> >>>>This doesn't seem to be much effort at all. Am I on the wrong track >> >>here? >> >>>>Juergen >>> >>> >>>While in most cases a Portlet should be simple (just display some >>>info), sometimes one portlet can be a complete web application in >>>itself. In >> >>this case, >> >>>having an MVC framework can make a huge difference. Imagine >>>implementing >> >>a whole >> >>>web application inside a servlet doPost(), and no framework >>>underneath. >> >>With >> >>>portlets you only have doView() to do the same thing... >>> >>>A PortletDispatcher should be very similar to ServletDispatcher and >> >>reuse >> >>>everything that is possible from the actual mvc framework. Ideally, >> >>implementing >> >>>a portlet with Spring should be the same as implementing a servlet. >>> >>> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: IBM Linux Tutorials >>Free Linux tutorial presented by Daniel Robbins, President and CEO of >>GenToo technologies. Learn everything from fundamentals to system >>administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo > technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |