Comments on: Exposing/Accessing JBoss JNDI Objects/Datasources From an External JVM

By: Abdul Mohsin

Abdul Mohsin — Thu, 29 Jul 2010 18:30:30 +0000

Hats off to you .. Exact resolution of the problem and brilliant explanation.

Thanks so much for sharing this information .

Abdul Mohsin

By: Steven

Steven — Wed, 10 Mar 2010 21:56:27 +0000

i should have expanded… is HTTP communication the only way that you can secure access to the JNDI entry? JNP doesnt allow such a thing? it just feels like my datasources are living in the wild for anyone who could try to access (assuming firewalls allow ports to be used that is)

By: Steven

Steven — Wed, 10 Mar 2010 21:41:05 +0000

this was VERY helpful – wanted to get this going for a while now and most documents i found never mentioned the attribute in the datasource config files. that was the piece i was missing!

however, it does bring a conern to mind. now that this datasource is exposed, how can i restrict who can use it?

By: Raquel

Raquel — Wed, 18 Nov 2009 19:33:16 +0000

Hi!

I solved my problem

Let me explian you:
I have two Datasources because I want to use two databases in the same class communicating one to each other.

I solved the problem with a property in JBoss file: jbossts-properties.xml:

By: engfer

engfer — Wed, 18 Nov 2009 16:56:27 +0000

I guess I’m at a loss to understand the issue you are having… What specific situation are you referring to?

On the outset, I would tell you to make sure that both of your datasource xml’s are using the global JNDI namespace. You should be able to connect to both…

By: Raquel

Raquel — Wed, 18 Nov 2009 15:56:11 +0000

Great post but what about having 2 datasources and use them at the same time? When I have two datasources I just can acceed the first one! I don’t know how to solve this…

By: Vladimir

Vladimir — Wed, 17 Jun 2009 17:07:57 +0000

Hi Jason, you can’t get a specific Oracle object because you are running in a different JVM; that’s why you only get a proxy.

The good news is you don’t need it if you are using an oracle jdbc driver 10.2 or newer. To work with clobs/blobs, use:

ResultSet rs = …
byte[] myBlob = rs.getBytes(1);
String myClob = rs.getString(2);

or:

Statement s = …
byte[] myBlob = …
s.setBytes(1, myBlob);
String myClob = “This is my huge clob.”);
s.setString(2, myClob);

hope it helps,
Vladimir

By: Jason

Jason — Mon, 11 May 2009 17:51:42 +0000

Excellent article, wish I’d found it sooner!! We are using this technique to access an Oracle data source while running batch java (which is naturally outside the container). The problem we are having is that we have an XMLType field in the database, so we need the actual OracleConnection object in order to create a CLOB or XMLType to store in there. If running inside the container from MDB or web, no problems. However, if running in batch we can’t get the Oracle data types. The JNDI lookup works just fine, we get a java.sql.Connection. The problem is we can’t cast that to any Oracle data type. Inspecting the data source object in debug mode, we find that it evaluates to $Proxy1. Any thoughts on that? Thanks!

By: Recent Links Tagged With "jvm" - JabberTags

Recent Links Tagged With "jvm" - JabberTags — Sun, 07 Dec 2008 17:34:20 +0000

[...] public links >> jvm Exposing/Accessing JBoss JNDI Objects/Datasources From an External JVM Saved by goldduke on Sun 16-11-2008 JSR 326 – Post mortem JVM Diagnostics API Saved by [...]

By: Yassine

Yassine — Wed, 22 Oct 2008 08:20:43 +0000

Many many thanks your post clarified my understanding related to remotely exposining JNDI resources.

keep up the good work
merci!!