Ah, light comes on. In any event, I specified FoobarDS and since JBoss plunked it down in java:/FoobarDS am I correct in assuming that direct access to datasources is not supported? Normally we use session beans and delegate database access through the session beans. In this case I wanted to cobble together a quick 'n dirty test app that used the datasource on a running instance of JBoss. Should I use the session façade in this case also or is there a way to get the datasource remotely?
-----Original Message----- From: Alexey Loubyansky [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 4:37 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] JNDI Name Everything under 'java:/' is not remotely accessible. alex Rod Macpherson wrote: > JBoss is binding my datasource just fine and my webapp works but > trying > to connect from a stand-alone client outside of the server fails: > > 14:25:52,704 INFO [FoobarDS] Bound connection factory for resource > adapter for ConnectionManager 'jboss.jca:service=LocalTxCM,name=FoobarDS > to JNDI name 'java:/FoobarDS' > > The datasource is FoobarDS and we lookup the string java:/FoobarDS and > that works fine within our J2EE application. Only fails from a remote > client (fabled option D did not work either:) > > TIA, > > Rod > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
