>+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". 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 -Mete ---------- Original Message ---------------------------------- From: David Sean Taylor <[EMAIL PROTECTED]> Reply-To: "Jetspeed Users List" <[EMAIL PROTECTED]> Date: Wed, 28 May 2003 13:55:22 -0700 > >On Wednesday, May 28, 2003, at 03:20 AM, Mete Kural wrote: > >> >> Thanks for your input. The reason why I was wondering about this topic >> is because Struts has industry-wide tools support and it seems like >> this support is going to increase in the future. > >> Additionally Struts has/will have good integration with JavaServer >> Faces > >has....really, be honest > >> which I think is crucial for a portal server such as JetSpeed in order >> to be truly client agnostic. > >> Furthermore there are a lot of developers familiar with Struts which >> may get more developers interested in committing to JetSpeed. What do >> you think? Do you think these factors are worth the hassle of >> switching from Turbine to Struts as the base framework layer? >> > >+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 > >-- >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]
