Hi, major +: - open source (no license cost sources) - really nice portlet functions
major minus: - high learning curve because of thight integration with turbine + not easy to build on existing (standardized) knowledge -> EJB etc ... - maybe to limited access control (see my posting: http://www.mail-archive.com/jetspeed-user@jakarta.apache.org/msg07717.html and please help me with that issue!) Kris "Stephen Townsend" <[EMAIL PROTECTED]> 28.01.2003 23:51 Please respond to "Jetspeed Users List" To: <[EMAIL PROTECTED]> cc: Subject: Is Jetspeed a good solution? Hello, We have determined that Jetspeed is a candidate for use as our portal. This determination was made by: 1. It was quickly implemented and tailored for a demonstration. 2. There is a migration path to a commercial portal. JetSpeed's API was the basis for WebSphere. Should there ever be a need for a commercial portal, a conversion to Websphere is feasible. 3. The activity in this mailing list is indicative of possible support. Firstly does this make senses? As well, is there anything else one should consider? I also wish to quickly identify any gotchas in the use of Jet Speed as portal for a business. We are targeting Jetspeed as a possible solution for different user groups: 100's, 1000's 10,000's of users. Where does jetspeed top out on load, and what productions sites are actually using JetSpeed? Also, please indicate any major plus' or minus' on the use of Jetspeed. Thank you. Stephen
