You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by jakarta-lists <ja...@apoco76.com> on 2003/07/31 06:22:34 UTC
Struts and Jetspeed
Hello,
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.
Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: Struts and Jetspeed
Posted by "Todd G. Nist" <tn...@bellsouth.net>.
Have you looked at http://www.liferay.com/products/index.jsp which is built
open source technologies like Hibernate, Lucene, and Struts.
-----Original Message-----
From: BaTien Duong [mailto:batien.duong@dbgroups.com]
Sent: Thursday, July 31, 2003 12:13 PM
To: Struts Users Mailing List
Subject: Re: Struts and Jetspeed
Joe Germuska wrote:
> 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.
>
Struts has a much better control, while JetSpeed has established
portlets and facilities to connect devices to portlets. The problem with
Jetspeed is that it is binding to Turbine, while Struts allows complete
separation of controller framework and presentation layer. Struts-Tiles
enable 1 single web-page view rather than portal view and portlet view.
With the release of JSR-168 specification of portal/portlet container
based on standard Servlet container, it makes a lot of sense to refactor
Struts framework to work with standard Servlet / Portal /Portlet
container. Then an effort to refactor Jetspeed portlets into this
framework. I wonder if any developer has playing with this idea? I heard
Craig and Cedric have something under their desks, and not ready to
share yet? Am I right?
>>
>
> 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
>
BaTien
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Struts and Jetspeed
Posted by BaTien Duong <ba...@dbgroups.com>.
Joe Germuska wrote:
> 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.
>
Struts has a much better control, while JetSpeed has established
portlets and facilities to connect devices to portlets. The problem with
Jetspeed is that it is binding to Turbine, while Struts allows complete
separation of controller framework and presentation layer. Struts-Tiles
enable 1 single web-page view rather than portal view and portlet view.
With the release of JSR-168 specification of portal/portlet container
based on standard Servlet container, it makes a lot of sense to refactor
Struts framework to work with standard Servlet / Portal /Portlet
container. Then an effort to refactor Jetspeed portlets into this
framework. I wonder if any developer has playing with this idea? I heard
Craig and Cedric have something under their desks, and not ready to
share yet? Am I right?
>>
>
> 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
>
BaTien
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Struts and Jetspeed
Posted by Joe Germuska <Jo...@Germuska.com>.
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
--
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"If nature worked that way, the universe would crash all the time."
--Jaron Lanier
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org