To a large extent this is in agreement with Raphael Luta's perspective.
<resent-after-corrections>
How I intend to use Jetspeed at my company
------------------------------------------
I am looking at Jetspeed being the presentation engine for the eServices
that we have/are developing.
Details below -
I have lots of services running off many servers using different
environments - PowerDynamo, Apache JServ, NT-Tomcat, VC++-ASP-COM etc .
I will use Jetspeed to put all these services in one place for the user.
So the user can pick and choose the service(s) that (s)he needs.
I will also have some services that are mandatory, i.e.,
users will be compulsorily subscribed.
</resent-afetr-corrections>
One more thing: do you agree with this assertion by Rapha�l Luta?
> Jetspeed is not an application or publication framework. I don't see
> *anybody* building a whole site with jetspeed. Jetspeeed is used to
> aggregate contents and publish this in one or several screens.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
