> Sounds like I need to start building out of CVS and playing with it to see
> how it's going to hang together.

Most definitely!  The more feedback we get now, the better than when we get near a 
beta release.  Right now, expect J2 to be in a state of flux.  Things will change, 
disappear without warning ;)

Regards,
*================================* 
| Scott T Weaver                 |
| <[EMAIL PROTECTED]>            | 
| Apache Jetspeed Portal Project |
| Apache Pluto Portlet Container |
*================================*

> -----Original Message-----
> From: Cordell, Ronald L. [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 22, 2003 2:29 PM
> To: 'Jetspeed Users List'
> Subject: RE: JetSpeed 2 Development list
> 
> Thanks again, Scott.
> 
> Sounds like I need to start building out of CVS and playing with it to see
> how it's going to hang together.
> 
> Regards,
> 
> -ronc
> 
> -----Original Message-----
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 22, 2003 2:20 PM
> To: 'Jetspeed Users List'
> Subject: RE: JetSpeed 2 Development list
> 
> 
> 
> > -----Original Message-----
> > From: Cordell, Ronald L. [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 22, 2003 2:06 PM
> > To: 'Jetspeed Users List'
> > Subject: RE: JetSpeed 2 Development list
> >
> > Scott,
> >
> > Thanks for the reply!
> >
> > Things I've been wondering about are Struts compatibility (I think this
> is
> > indirect to JetSpeed, though, as I can use the work done in the Velocity
> > <>
> > Struts integration), LDAP-based user authentication (listed as a 1.4b3
> > issue, just wondering if it will carry over to 2.0).
> 
> We will definitely support LDAP, however the security model is still in
> the
> planning stages.  As for Stuts, I hear they (the Struts team) are working
> on
> new controller servlets that should "play well" with JSR-168 portals.  I
> have yet to plug a struts app into J2 yet, but it is on the top of my
> list.
> 
> 
> 
> > To clarify your note, although OJB is the default persistence layer, I
> > could
> > use any other persistence layer if I needed to.
> >
> 
> Sure, you just need to implement a couple of interfaces to act as adapters
> to the persistence layer of your choice.
> 
> > What about user roles and how that applies to accessibility as described
> > for
> > JetSpeed 1.4? Will that be maintained?
> 
> That is still up in the air, it will probably become clearer when we start
> working on conversion tools/adapters for existing J1 applications.
> 
> >
> > Likewise for the use of skins a.k.a "branding" - will that still be
> there?
> 
> Most definitely, however in a different fashion than what you are used to
> current in J1.  There will no longer be skin registries and the
> layouts/themes/skins what have you will be much easier to develop and
> deploy.
> 
> >
> > Thanks again,
> >
> > -ronc
> >
> 
> *================================*
> | Scott T Weaver                 |
> | <[EMAIL PROTECTED]>            |
> | Apache Jetspeed Portal Project |
> | Apache Pluto Portlet Container |
> *================================*

Reply via email to