> I've been playing with Jetspeed for the better part of a day > and am pleased to report that I haven't encountered any real > problems (yet!) - it started fine, and I was surprised how > easy it is to create a rudimentary portlet. > > Some initial comments and questions come to mind. > > 1. Finding resources is sometimes difficult. Thank goodness for > Google caching the Portal Howto, and thanks to somebody on > this mailing list making the .war file available :)
Suggestions: - This mailing list. - Use mail-archive to look for past issues - http://jakarta.apache.org/jetspeed has quite a bit of documentation on it. - It's open source, so jump in! ;) > 3. According to the "Portal How To", "starting with version 2.0 > of Jetspeed, ECS will be deprecated." > I actually welcome this because ECS may be fine for engineers > but it results in the most unappealing webpages using basic html :-) > Anyway, what will replace ECS ? AFAIAK, there is no plan to replace ECS with another similar technology as most pages in Jetspeed are already written using the Velocity templating language. FYI, there is currently support for both Velocity and Jsp portlets in Jetspeed. > And how far off is Jetspeed v2.0 ? I think there a lot of factors affecting this. One of the ones I know of is the completion of a portlet standard proposed in JSR 168. Plus, there is quite a bit of functionality the jetspeed team is trying to finish and test. > 4. Yes, Jetspeed was quite slow initially. Then I removed some > of the portlets (xmlhack and some other newsfeed) and it improved. > The initial hit on jetspeed after the container has started is generally slow. Remember, the news feed portlets have to get there information from across the internet. This can initially mean slow performance, however, most portlets are cached which dramatically increases performance. The stock quote portlet is the worst, if it cannot contact the webservice that supports it, the delay can be up to 30 sec. I usually remove it from the default page just of for this reason. On average I see a sub 5 second response on most pages. > 5. Hitting "back" never works, the browser always reports "page > has expired". > > 6. Is there any documentation for all the variables in the .vm > files ? There's stuff like $clink and $l10n and I have no > idea where they came from. > These are what is known as "pull tools" that are automatically added to the context by Turbine, the framework that powers Jetspeed. You can find out what classes these use by looking under the pull tools section of TurbineResources.properties. More info on pull: http://jakarta.apache.org/turbine/turbine-2/services/pull-service.html Turbine in general: http://jakarta.apache.org/turbine/turbine-2 Becoming familiar with turbine is not a bad idea if you plan on really understanding how Jetspeed works. > 7. The "Customize portlet" page for all portlets shows 2 pulldowns, > namely "Skin" and "Security ID". I think that these aren't > really of interest to my prospective users. How do I customize > the "Customize portlet" page ? > You can customize templates/vm/portlets/html/customizer-portletset-layout.vm and remove these if you like. > Some of the above are just comments, but if anybody could help > with the question marks above, any and all feedback is much > appreciated. Thank you, > > Stephen. > > > > > > --------------------------------- > Get a bigger mailbox -- choose a size that fits your needs.
