As my EJB was bean-managed, I had no problems with the connection pool. I
got my connection simply by calling "con = datasource.getConnection();".
But since I changed my EJB from bean-managed to container-managed, I am not
able to use the ascertained connection as before.
For example:
I have to put the connection object to a oracle-spatial-method, to receive a
sdoAdapter object ... code looks something like this ...
GeometryAdapter sdoAdapter = OraSpatialManager.getGeometryAdapter ("SDO",
"8.1.6", null, STRUCT.class, null, con);
But unfortunately sdoAdapter is always null. So I changed the code to ...
GeometryAdapter sdoAdapter = OraSpatialManager.getGeometryAdapter ("SDO",
"8.1.6", null, STRUCT.class, null, DriverManager.getConnection
("jdbc:oracle:thin:@xxx:nnnn:xxxxxx","user", "pw"));
And then it works, ... but I don't want to use this possibility, because the
configuration code is hard-coded.
Does anybody know, why this is so ?
And another peculiar thing is, that, if i change the EJB back to
bean-managed, only the connection-pool variante works, and the hard-coded
drivermanger variante does not work anymore (then ... the sdoadapter object
is null).
Help is appreciated.
Best regards,
Roman Wittchen
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
