> -----Original Message----- > From: Hamilton Verissimo de Oliveira (Engenharia - SPO) > [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 13, 2004 9:35 AM > To: [EMAIL PROTECTED] > Subject: JCA implementation > > Hi there, > > > I still digesting the spec but a few abysses already appeared. > > - Security: JCA depends on JAAS (Subject) security. I'm not sure how is > Merlin's architecture for security. This can (?) be solved if the JCA > facility acts as a bridge between Merlin model and JCA requirements. Or we > can not implement this at all :-)
A while back I started looking as JAAS and plugging it into Avalon but just didn't have the time or resources at the moment. Definitely a +1 to getting a *good* implementation in Avalon (ie- not just "bolted" on). > - EJB: The spec cleary states that Resource Adapter may access EJBs. No > question about it: we won't implement such thing. Or ....... (please fill > to dotted space) :-D Or also avoid current EJB spec and wait until EJB3 which looks to be more inspired by IoC and "lightweight" container ideas. > - JMS: I'm a completely ignorant about JMS. Haven't worked with it. JMS is cool. I've got the latest OpenJMS running in Merlin now. I'll be committing the changes to phoenixjms.sf.net soon (though it may just be donated back to OpenJMS in the end). I also want to work on hosting ActiveMQ (Geronimo's JMS Server) in Avalon. Additionally I started work on a Merlin facility that allows Avalon components to subscribe to JMS destinations, ie- an Avalonized Message Driven Bean, or as I call them, Message Driven Services (MDS). Summary: we'll have good JMS support really soon now. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
