C
Chris S
We are currently upgrading our EJB modules from 1.1 to 2.0 local. We
have a repository structure like the following in front of the entity
beans:
SessionRepository
calls on
TopicRepository
The SessionRepository only has JDBC calls into our database using a
1.1 compliant connection in WebSphere (v4 for those that use the DB2
data source). The TopicRepository uses a local entity EJB which gets
2.0 compliant connections (v5 DB2 data source) from WebSphere. Each
version of the data source has a different JNDI binding such as
"jdbc/DB2CONN4" and "jdbc/DB2CONN5". On the TopicLocal EJB which is
used from the TopicRepository, the "trans-attribute" tag for the
container-transaction uses "RequiresNew". I thought that this would
allow for the full transaction to work across the mixed EJB
compliance.
Could somebody help me with a way to make this work? Are there more
file descriptor modifications to make? Is it possible to mix
compliance within an application function area?
have a repository structure like the following in front of the entity
beans:
SessionRepository
calls on
TopicRepository
The SessionRepository only has JDBC calls into our database using a
1.1 compliant connection in WebSphere (v4 for those that use the DB2
data source). The TopicRepository uses a local entity EJB which gets
2.0 compliant connections (v5 DB2 data source) from WebSphere. Each
version of the data source has a different JNDI binding such as
"jdbc/DB2CONN4" and "jdbc/DB2CONN5". On the TopicLocal EJB which is
used from the TopicRepository, the "trans-attribute" tag for the
container-transaction uses "RequiresNew". I thought that this would
allow for the full transaction to work across the mixed EJB
compliance.
Could somebody help me with a way to make this work? Are there more
file descriptor modifications to make? Is it possible to mix
compliance within an application function area?