[JBoss JIRA] Created: (EJBTHREE-724) persistence.xml jar-file processing
by Heiko W. Rupp (JIRA)
persistence.xml jar-file processing
-----------------------------------
Key: EJBTHREE-724
URL: http://jira.jboss.com/jira/browse/EJBTHREE-724
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Heiko W. Rupp
EJB 3 persistence spec says in 6.2.1.6, 2nd paragraph about <jar-file>
"Such JAR files are specified relative to the root of the persistence unit (e.g.,utils/myUtils.jar)"
When I have a persistence.xml like this:
<persistence>
<persistence-unit name="jon">
<jta-data-source>java:/JONDS</jta-data-source>
<jar-file>lib/on-enterprise-server-2.0-SNAPSHOT.jar</jar-file>
</persistence-unit>
</persistence>
The PersistenceUnitDeployment gives
file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar]
but the root of the PersistenceUnit is
file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/
2006-10-04 18:00:43,537 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] Found persistence.xml file in EJB3 jar
2006-10-04 18:00:43,538 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] adding JarFile URL: file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar
2006-10-04 18:00:43,586 INFO [org.hibernate.ejb.Version] Hibernate EntityManager 3.2.0.CR2
2006-10-04 18:00:43,625 INFO [org.hibernate.cfg.annotations.Version] Hibernate Annotations 3.2.0.CR2
2006-10-04 18:00:43,638 INFO [org.hibernate.cfg.Environment] Hibernate 3.2 cr4
2006-10-04 18:00:43,649 INFO [org.hibernate.cfg.Environment] hibernate.properties not found
2006-10-04 18:00:43,654 INFO [org.hibernate.cfg.Environment] Bytecode provider name : javassist
2006-10-04 18:00:43,666 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling
2006-10-04 18:00:43,906 DEBUG [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [
name: jon
persistence provider classname: org.hibernate.ejb.HibernatePersistence
classloader: org.jboss.mx.loading.UnifiedClassLoader3@3b31a6{ url=file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/ ,addedOrder=43}
Temporary classloader: null
excludeUnlistedClasses: false
JTA datasource: org.jboss.resource.adapter.jdbc.WrapperDataSource@c90acb
Non JTA datasource: null
Transaction type: JTA
PU root URL: file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/
Jar files URLs [
file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar]
Managed classes names []
Mapping files names []
Properties [
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-3770) JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool
by Weston Price (JIRA)
JBoss/JCA JDBC implementation should allow for Transaction isolation level to be reset on underlying JDBC connection prior to return to pool
--------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-3770
URL: http://jira.jboss.com/jira/browse/JBAS-3770
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Weston Price
Assigned To: Weston Price
Priority: Minor
By default, when we return a JDBC connection to the pool we execute the following in the ManagedConnection.cleanup() method:
if (jdbcTransactionIsolation != transactionIsolation)
{
try
{
con.setTransactionIsolation(jdbcTransactionIsolation);
jdbcTransactionIsolation = transactionIsolation;
}
catch (SQLException e)
{
mcf.log.warn("Error resetting transaction isolation ", e);
}
}
In this scenario we don't return the original isolation level on the underlying connection. The spec doesn't prohibit this, and I can't see any reason why we shouldn't do this, or provide a configurable option.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months