It has a lot out of the box.
.V
Joe Germuska wrote:
At 2:21 PM -0300 8/20/03, Emerson Cargnin wrote:
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's a little early to say that anything follows the portlet specification since it's just barely in public review! I can also tell you that on the Struts developer list there seems to be decent awareness of Portlets and a general commitment to making Struts work equally well in either a portlet or servlet context -- but no one is in a hurry to start before the spec is final, it seems.
If all you want is a portlet container, Jetspeed is one already, regardless of JSR-168. Struts isn't a portlet container, and besides tiles, you'd have to build up user authentication and preference support which Jetspeed has out of the box.
Joe
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]
-- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA
Advanced <a href ="baseBeans.com">Struts Training</a>, mentoring and project recovery in North East.
Struts conversion and <a href ="baseBeans.com"> fixed bid development</a>.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
