ApplicationPortlet and Turbine Application Service

[Shawn Dahlen <sm...@syr.edu>]

I was wondering what people's views were on the proposed Turbine 
Application Service
that would allow for pluggable sub-applications.  Does this conflict 
with the
ApplicationPortlet, or are they complimentary?

I am in the process of creating an eCommunity platform that would 
combine the
concepts of a portal and web application.  I had been looking at this 
from Turbine's
point of view and realized the need for pluggable web applications into 
the
"community application".  Jetspeed could be my "community application", 
I just need
to know where the pluggable web app functionailty would fall.

I suspect that this should be part of the Turbine framework, to allow 
other Turbine-based
applications to have this feature as well.

Shawn Dahlen

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org