No problem. It is already pretty far along...things you can do right now are package up a deployable Portlet in a .war file with a standard
Spring application context. You can configure a PortletDispatcher and dispatch to Controllers and JSTL Views.
There is simple proof a concept app pacakged up at:
http://www.tnt-web.com/springportlet/
JSR-168 is still a bit too fresh...the portal frameworks are still working it in which has slowed us a down a bit...having to attend to production deployments in the very near term with legacy APIs. I am hopeful we can start to bring more focus to Spring PortletMVC in the near term.
Cheers,
Bill
-----Original Message-----
> Date: Mon Jul 19 07:39:30 EDT 2004
> From: "Rainer Schmitz" <Rai...@ab...>
> Reply-To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet support status?
> To: spr...@li...
>
> Thanks for the information, Bill. With my still somewhat limited
> experience with portlets it seems best to wait until at least some
> example code is published.
>
> Rainer
>
> William G Thompson Jr wrote:
>
> > we are mostly at the same stage...which is a good base but still needs polish and good sample useage.
> >
> > with what is in the sandbox and the sample springportlet you can route portet modes to controllers and render via jstl using portlet tag lib all configured in a standard spring application context.
> >
> > things remaining include:
> > * convenience controllers
> > * data binding
> > * javadoc clean up
> > * sample app
> >
> > later.
> > Bill
>
>
|
