Re: Single instance of the ManagedConnectionFactory??
Binod <[email protected]> Fri, 4 May 2007 11:17:15 +0530
| Newsgroups | gmane.comp.java.sun.connector |
|---|---|
| Message-ID | <[email protected]> |
Stephen New wrote: >Thanks for the reply, Binod. Yes, I see what you mean about section 6.5.3.3 > >My issue is this: I need to find a resource adapter class that has only a >single object instance per EIS instance. In this object instance I want to >maintain a pool of objects that is centrally accessible from all >ManagedConnectionFactory instances. I believe that this may not be possible >in a clustered (multi-JVM) environment, but that does not concern me at >present. As long as I can make it work for a single JVM then I will be >happy. > >Any ideas? > > ResourceAdapter javabean is probably what you are looking for. Connector 1.5 specification introduced lifecycle management model for resource adapters and RA javanbean is designated as central authority or registry for the resource adapter instance specific information. Please see section 5.3 of the spec for more details. thanks, Binod. >-- >Stephen New >Rules Architect >Object Connections Australia > >W. www.objectconnections.com > > > >>-----Original Message----- >>From: A public list for J2EE Connector architecture interest. >>[mailto:[email protected]] On Behalf Of Binod >>Sent: Thursday, 3 May 2007 8:11 PM >>To: [email protected] >>Subject: Re: Single instance of the ManagedConnectionFactory?? >> >> >> >>>Hi, >>> >>>I am wondering if anybody can help me with an answer to the >>> >>> >>following >> >> >>>question. >>> >>>Does the JCA spec (1.5) guarantee that an application server will >>>maintain only a single instance of the >>> >>> >>ManagedConnectionFactory class >> >> >>>per target EIS instance? >>> >>> >>> >>No. An application server might create multiple connection >>pools each using a ManagedConnectionFactory instance. >> >>Also, section 6.5.3.3. is an example and is not a requirement. >> >>Can you explain what exactly is the issue you are facing? >> >>- Binod. >> >> >>>Section 6.5.3.3 seems to make this point a little fuzzy to me. >>> >>>Thanks for any help! >>>-- >>>Stephen New >>>Rules Architect >>>Object Connections Australia >>>W. www.objectconnections.com >>> >>> >>> >>> >>====================================================================== >> >> >>>===== To unsubscribe, send email to [email protected] >>> >>> >>and include >> >> >>>in the body of the message "signoff CONNECTOR-INTEREST". >>> >>> >>For general >> >> >>>help, send email to [email protected] and include in >>> >>> >>the body of >> >> >>>the message "help". >>> >>> >>> >>============================================================== >>============= >>To unsubscribe, send email to [email protected] and >>include in the body of the message "signoff >>CONNECTOR-INTEREST". For general help, send email to >>[email protected] and include in the body of the message "help". >> >> >> > >=========================================================================== >To unsubscribe, send email to [email protected] and include in the body >of the message "signoff CONNECTOR-INTEREST". For general help, send email to >[email protected] and include in the body of the message "help". > > =========================================================================== To unsubscribe, send email to [email protected] and include in the body of the message "signoff CONNECTOR-INTEREST". For general help, send email to [email protected] and include in the body of the message "help".