DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
Key: HIBERNATE-10
URL: http://jira.jboss.com/jira/browse/HIBERNATE-10
Project: Hibernate
Type: Bug
Reporter: youngm
Assigned to: Gavin King
DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
-
Key: HIBERNATE-11
URL: http://jira.jboss.com/jira/browse/HIBERNATE-11
Project: Hibernate
Type: Bug
Reporter: youngm
[ http://jira.jboss.com/jira/browse/HIBERNATE-11?page=history ]
youngm updated HIBERNATE-11:
Attachment: hibernate-cache.diff
Here is a patch that appears to fix the problem. It replaces all instances of
TreeCache with TreeCacheMBean.
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=history ]
youngm updated JBJCA-16:
Description:
In the C-JDBC JDBC Connection driver it uses autoCommit=false to determine if
it is in a transaction when changing readOnly.
Unfortunatly LocalManagedConnection
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314910
]
youngm commented on JBJCA-16:
-
Actually, after thinking about this is a bigger problem then I thought. Moving
checkState() above setAutoCommit() won't help if the underlying
Changing readonly after autocommitt set to false fails with C-JDBC Driver
-
Key: JBJCA-16
URL: http://jira.jboss.com/jira/browse/JBJCA-16
Project: JBoss JCA
Type: Bug
Versions: JBossAS-4.0.1
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314914
]
youngm commented on JBJCA-16:
-
The managed connection property would be an acceptable solution for me If you
think it would be a good idea.
Mike
Changing readonly after
[ http://jira.jboss.com/jira/browse/JBAS-26?page=comments#action_12314867 ]
youngm commented on JBAS-26:
This is just a vote to move this item up to 4.0.2 RC1 To show that there is
interest out there for this item. The classloading fix and faster JSP
