Re: JCA in a non-managed environment
Jason <[email protected]> Mon, 13 Jan 2003 13:10:15 -0800
| Newsgroups | gmane.comp.java.sun.connector |
|---|---|
| Message-ID | <[email protected]> |
Van, Thanks for taking the time to reply. Strictly speaking though I think were talking about different issues. I don't necassarily want to connect to my RA remotely, I'm just looking for a JNDI provider to persist my Connection Factories. In any case, I've sort of settled on using the RMI Registry. Thanks again for the input and the link. By the way, the best discussion I found on the subject was here: http://www7b.software.ibm.com/wsdd/library/techarticles/0109_kelle/0109_kelle.html#JNDI -Jason > Hi, > > I posted a thread on this issue last year. Here is > the body: > > >> > I tried connecting from a remote VM to several > different adapters w/o > success. The specification says that you should > connect in managed or > non-managed environments the same way, via JNDI. I > assumed the > "non-managed" environment included remote VMs. > After all it works for > JDBC and JMS. As it turns out this assumption was > wrong. I found this > note up on the WebLogic site: > > http://e-docs.bea.com/wls/docs70/jconnector/trouble.html#1045779 > > Remote JVM > > As currently specified, the J2EE Connector > Architecture does not > provide > for remote access. None of the defined interfaces > are remote, and the > architected system contracts presume a local > relationship between a > ManagedConnectionFactory and a Connection Manager. > As a result, you must deploy your application so > that the application > components are hosted in the same Java Virtual > Machine as your > resource > adapters. > << > > Ram Jeyaraman, specification lead for JSR# 112, > confirmed that this is > the case. > > If you want to use a resource adapter from a remote > VM you should: > > 1) Instantiate the ManagedConnectionFactory > implementation. > 2) Set the properties on it as specified in the > RA.XML > 3) Call createConnectionFactory() - your > implementation should create > it's own ConnectionManager during this call > > > Van > > Van Dillon > Senior Software Engineer > 203 225-1817 > 203 225-1919 > Novell, Inc., the leading provider of Net Business > Solutions. > www.novell.com > > > >>> [email protected] 1/11/03 9:16:43 AM >>> > Hello, > > I've recently developed a JCA 1.0 compliant resource > adapter. I've tested it in the J2EE reference > implementation server with no difficulty. However, > I'm required to ship it with support for non-managed > (two-tier) deployment. The specification states > unambiguously that a connection factory should be > obtained via a JNDI lookup in both a managed and a > non-manged scenario. This is fine; the goal is > obviously to maintain a consistent client > programming > model. My problem though is that I can't find a > portable, free JNDI provider which preferably offers > support for a reference mechanism. How have others > handled this requirement? I'm considering just using > the RmiRegistry. Has anyone else done this? Can > anyone think of any problems with this approach? > Thanks in advance for any replies! > > -Jason > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up > now. > http://mailplus.yahoo.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". > > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.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".