I don't look at persistence context/unit injection as a service, rather, as a resource utilized by a service for handling domain persistence. I don't know how well this fits into the SCA specification, however, as an add-on it is an appealing feature to Tuscany. Frameworks like Spring already support such features and there are efforts in implementing non-JPA aspects of EJB 3.0 in lightweight Ioc containers (pitchfork for example).
Also, according to my understanding of composites conceptually, services can be as coarse-grained or fine-grained as they need to be. From that perspective you could have a data access service for domain persistence, that may need resources like datasources and persistence contexts. Ta Meeraj >> -----Original Message----- >> From: scabooz [mailto:[EMAIL PROTECTED] >> Sent: 03 October 2006 17:29 >> To: [email protected] >> Subject: Modeling persistence services, was Re: EJB3 (JPA) support >> >> Hmmmm...a service modeled as a property is what seems odd. >> I'm trying to keep an open mind. >> Imagine drawing a picture of this using the icons from the >> SCA spec. You'd have some kind of a connection from a >> component's property to a database? That's what doesn't >> make sense. I need to think more on this, and maybe I'll >> change my mind. Didn't want to let this thread just die. >> >> Dave >> >> ----- Original Message ----- >> From: "Jim Marino" <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Tuesday, October 03, 2006 11:40 AM >> Subject: Re: EJB3 (JPA) support >> >> >> > >> > On Oct 3, 2006, at 7:44 AM, scabooz wrote: >> > >> >> Hi Jim, >> >> >> >> Somewhere buried in your explanation is the answer to >> >> my question, but I can't find it, so I'll have to ask. I'm >> >> trying to understand how you have modeled this WRT >> >> the assembly model. It looks like you've added in a >> >> SCDL extension, and are playing with the semantics >> >> of a property. I would have expected such a formal >> >> part of the application to have been modeled in a >> >> formal way, such as with an SCA component. >> > It's a property (or "resource") just like a datasource or >> type system >> > helper (e.g. SDO) would be. Modeling it as a service on a >> component >> > seems kind of odd. There's a system service responsible >> for providing >> > a value for the property (just like all property values in >> Tuscany) >> > but that's an implementation detail. Make sense? >> >> Am I >> >> understanding this correctly? I'm asking from a spec >> >> perspective, trying to make sure that we're clean. >> >> >> >> Dave >> >> >> >> <snip> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> This message has been checked for all email viruses by MessageLabs. >> >> ***************************************************** You can find us at www.voca.com ***************************************************** This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX This message has been checked for all email viruses by MessageLabs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
