> 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?
This is the whole idea behind the JSR 168 standard. To get your portlet to work, you just deploy it, that's it. You shouldn't have to know squat about how Jetspeed works internally. Your portlet should never (if it wants to stay portable) need/have to directly access any resources within the Portal. > Is Jetspeed 2 going to address that by separating out the user api > (events/action, etc), the integrator api (security interfaces, etc) and Jetspeed 2 uses the JSR 168 model of one action and multiple renders per request. To stay compliant we should not stray from this. The api is pretty cut and dried on this approach. There is really no other user api apart from the portlet-api. Regards, *================================* | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | *================================* > -----Original Message----- > From: Todd Kuebler [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 23, 2003 6:40 PM > To: Jetspeed Developers List > Subject: Jetspeed2 - User .vs. Integrator .vs. Core API/jars > > > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
