Inside SessionBean, an Entity and direct queries

Question

Hi everybody,
Look at this example:
I already have a javaBean (simple, not enterprise) that updates an inventory table. I have to pass a java.sql.Connection as parameter.
I also have an EntityBean that put an order. Of course, i dont have to pass any Connection, because the EJB retrieve it from the container.
Now, I want to have both funcionalities in a single SessionBean stateless inside the same transaccion. Obviously, both, the JavaBean and the EntityBean, have to share the same DB Connection.
Is this possible???
Thanks in advanced
Iv�n.

Answer 1

Greetings,
Hi everybody,
Look at this example:
I already have a javaBean (simple, not enterprise)
that updates an inventory table. I have to pass a
java.sql.Connection as parameter.
I also have an EntityBean that put an order. Of
course, i dont have to pass any Connection, because
the EJB retrieve it from the container.
Now, I want to have both funcionalities in a single
SessionBean stateless inside the same transaccion.
Obviously, both, the JavaBean and the EntityBean, have
to share the same DB Connection.Erm, why do they have to share the same connection?? This is actually a 'transaction model' issue and not a database one... When dealing with stateless (poolable) session beans the thing to remember is that a transaction context exists within the bean only for the life of a single method call. As long as your slSB is calling on both the JavaBean and the Entity Bean within the same method call then your database accesses will share the same transaction - erm, depending, of course, on the transaction attributes assigned to your Entity Bean.
Is this possible???Sharing the DB connection? Erm, yes, but not really... You can write your EBs business methods to accept a Connection but this will create more headaches than it's worth since, as you rightly pointed out, the bean must be able to get it's own connection as part of the Container's management of it. If you REALLY need to share the same DB connection between JB and EJB then you may want to consider implementing the EJB functionality in a session bean - though, of course, this negates the benefits of using Entity Beans...
Thanks in advanced
Iv�n.I hope this is helpful.
Regards,
Tony "Vee Schade" Cook