[JBoss-dev] [JBoss JIRA] Created: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+

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

[JBoss-dev] [JBoss JIRA] Created: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1

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

[JBoss-dev] [JBoss JIRA] Updated: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1

[ 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

[JBoss-dev] [JBoss JIRA] Updated: (JBJCA-16) Changing readonly after autocommitt set to false fails with C-JDBC Driver

[ 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

[JBoss-dev] [JBoss JIRA] Commented: (JBJCA-16) Changing readonly after autocommitt set to false fails with C-JDBC Driver

[ 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

[JBoss-dev] [JBoss JIRA] Created: (JBJCA-16) Changing readonly after autocommitt set to false fails with C-JDBC Driver

Reporter: youngm Assigned to: Adrian Brock In the C-JDBC JDBC Connection driver it uses autoCommit=false to determine if it is in a transaction when changing readOnly. Unfortunatly LocalManagedConnection sets autoCommit=false prior to checkState() which synchronizes the readOnly

[JBoss-dev] [JBoss JIRA] Commented: (JBJCA-16) Changing readonly after autocommitt set to false fails with C-JDBC Driver

[ 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

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-26) Update 4.0.2 to use Tomcat-5.5.x

[ 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

[JBoss-dev] [Design of the JBoss Web Container] - Re: Tomcat 5.5 in JBoss

Thanks, I'll anxiously watch that task for updates. :) Mike View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3862049#3862049 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3862049

[JBoss-dev] [Design of the JBoss Web Container] - Re: Tomcat 5.5 in JBoss

So now that JBoss 4.0.1 is out is it possible to do a 4.0 branch build with tomcat 55 as the web container? I'd be more than happy to help test the tomcat 55 integration that will be going into 4.0.2 if I only had a little direction on how to do a build with tomcat 55. Mike View the original

[JBoss-dev] [JBossWeb] - Tomcat 5.5 in JBoss

Is there any kind of timeline of when we can expect some kind of preliminary Tomcat 5.5 support in JBoss? Assuming integration is planned will we see it in 3.2.x and 4.x or will it only be available in 4.x? Thanks, Mike View the original post :