any advice in choosing tiles vs jetspeedy?
I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments?
It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his "ideal goal" for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s).
I think after the release of JSR-168 Reference Inplementation, many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process.
BaTien DBGROUPS
Alex wrote:
Mike,
Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions?
Session information is missing after porting existing Struts application to JetSpeed portlet.
Thanks, Alex
Mainguy, Mike wrote:
I'll agree, if you're already using Turbine, then struts is really a waste
of time and effort. Just use the turbine framework (it's more complete
anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in
a different servlet context and then wrapping it in a portlet so you don't
end up with a confused mish-mash of technologies.
-----Original Message-----
From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM
To: Struts Users Mailing List
Subject: Re: Struts and Jetspeed
At 22:22 -0600 7/30/03, jakarta-lists wrote:
Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any.
It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout.
Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix.
Joe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
