I totally agree with:
+1 on basing Jetspeed on the Portlet API standard
-1 on using Struts as the base framework of the Jetspeed "portal
server"
+1 on using Struts as the base framework for Portlet
Applications
As an end user it really doesn't matter to me what framework is used as
the base for the Jetspeed portal server, what I care about is writing
applications that conform to as many relevant standards as possible
making it easy to deploy within different portlet containers. The
upcoming portlet standard (JSR 168) should be a big help and I can't
wait for Jetspeed to implement it. The ability to deploy portlets that
use struts would also be very beneficial for creating complex portlet
applications. Whether Turbine or Struts is superior I don't know, there
does seem to be a lot of industry momentum behind struts (both WebLogic
and WebSphere for example are allowing struts based portlets).
The security framework is another very critical part for me. I would
like to see security (Authentication & Authorization) split from the
user properties. For me it would be great if Jetspeed could be
configured to use the JAAS based container security provided by many
application servers. This would enable single sign-on to be accomplished
in a straight forward manner. Many third party tools like Siteminder and
ClearTrust are available to help with this problem. It also would allow
complex authentication schemes like: multi-factor authentication and
identity federation to be available to anyone who wants (and can afford)
to purchase the tools.
Just my two cents ;-)
Regards,
James
James Chamberlain
General Dynamics - Advanced Information Systems
Concept Development Department
U.S. Joint Forces Command
[EMAIL PROTECTED]
-----Original Message-----
From: David Sean Taylor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 6:41 PM
To: Jetspeed Users List
Subject: Re: JetSpeed 2: Turbine or Struts?
On Wednesday, May 28, 2003, at 07:41 AM, Mete Kural wrote:
>> +1 on basing Jetspeed on the Portlet API standard
>> -1 on using Turbine or Struts as the framework
>> +1 on portlet applications implemented in Struts
>
> I may not have made myself clear. I wasn't talking about what
> framework to base "portlets" on. Obviously with the Portlet API
> standard, it does not matter what framework you use. I'm asking
> whether you think it is worth it to switch to Struts as the base
> framework of the "portal server" itself (a.k.a. JetSpeed core), not of
> the "portlets".
>
You made yourself clear, and I completely understood what you were
communicating to me.
I hope this is 'clear' enough:
-1 on using Struts as the base framework of the Jetspeed "portal server"
+1 on using Struts as the base framework for Portlet Applications
> I honestly think it would be well worth it to switch to Struts.
>
> +1 on basing Jetspeed on the Portlet API standard
> +1 on using Struts as the base framework of the JetSpeed "portal
> server"
> +1 on basing portlets on the Portlet API standard
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
+01 707 773-4646
---------------------------------------------------------------------
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]
