Jetspeed2 - User .vs. Integrator .vs. Core API/jars

[Todd Kuebler <tk...@cisco.com>]

IMHO one of the greatest barriers to entry to Jetspeed 1.x was the mixing 
of the core API with the end user API.

Is Jetspeed 2 going to address that by separating out the user api 
(events/action, etc), the integrator api (security interfaces, etc) and the 
core api (all the guts you can't/shouldn't change) into separate 
jars/javadocs, or will there be pages and pages of javadoc to plow through 
including pipelines and valves and other non-user configurable stuff just 
to get a portlet to display Hello World?


-tk


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