On 7/4/07, David Jencks <[EMAIL PROTECTED]> wrote:
4. Modify the openejb protocol and interfaces to be jaspi-friendly but not actually implement jaspi right now 5. Actually write a jaspi implementation for geronimo/openejb. I may be getting distracted by shiny objects but I'm working on 4 and 5. AFAICT this is definitely going to change the openejb protocol to include a security object in responses and the openejb IdentityResolver and SecurityService interfaces, so if this is not acceptable I'd rather know this sooner than later. I'd expect that openejb would eventually want to support jaspi so before 3.0 is actually released seems like a better time to have modifications than say 3.1. Comments?
I read it a couple of times, but honestly I couldn't understand it as much as I wish. If you got something working I think that it's time to include it now as there will not be a better time to do it. Every release will put on us an additional burden to maintain backword compatibility. If you think it's necessary, I'm fine introducing it now and include a note in RELEASE NOTES what steps are necessary to upgrade Geronimo to the latest version. As to OpenEJB, I see it as ready to be shipped as 3.0 (with some rather small obstacles that prevent us doing it now) and would rather avoid introducing new (revolutionary?) stuff into it. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
