This does seem to be the way companies are going--I have worked on three
separate projects in the past few months, with exactly that goal for their
web-enabled products. None of them has made it to production yet (one was
cancelled, two are still in development), so I can't comment on future
support issues/workload. In all three cases, comparison of the available
options led to the adoption of Pluto as portlet container, with a
custom-designed web application using Struts to display the portlets,
handle navigation, etc. JS2 would be the ideal choice, but all three
projects had a tight time-to-market constraint, and JS2 isn't ready. The
hope with all was to eventually migrate to JS2 once it's stable.
The reason Jetspeed 1.x was not chosen in all cases, was because it seemed
that it would be easier to migrate from a custom portal application using
Pluto (and, therefore, JSR168-compliant portlets) to JS2, than to migrate
from JS1.x to JS2. (Jetspeed folks, I'd love to hear what you think on
this topic...)
Meghan
"David Holliday"
<[EMAIL PROTECTED] To: <[EMAIL PROTECTED]>
vepro.com> cc:
Subject:
Jetspeed for product framework?
01/03/2004 01:53 PM
Please respond to "Jetspeed Users List"
We have several products that we would like to display in a portal (think
network management and security). Jetspeed and Tomcat would be shipped
with each product. As a customer buys add-on products, they would just be
added to their portal.
Is this a good idea? Is Jetspeed suitable for such a project? Does anyone
have any experience with such a portal? Problems? Suggestions? Ideas?
Thanks,
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
