Use Hibernate style format for the property names ------------------------------------------------- Key: JBCLUSTER-212 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-212 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Hibernate-Cache-Provider Reporter: Galder Zamarreno Assignee: Galder Zamarreno Galder Zamarreno wrote: Hi, Chris Bredesen wrote: > I have to nit-pick though, because I'm crazy like that. > > Why choose a property name like "local.puts.only" when the rest of the Hibernate code base is consistent > with using '_', like "use_second_level_cache" or "provider_configuration_file_resource_path"? Because I didn't realise of that :) and clustering projects generally use '.' as separator more than '_'. More an oversight rather than anything else. Same with hibernate.treecache.querycache.local.writes.only. Let me figure out where to open a JIRA for this. Cheers, > > -CB > > Galder Zamarreno wrote: >> Hi, >> >> The news is out, there's a new cache provider implementation for the HB 3.2.x and JBC 1.4.x series as >> you can read from http://galder.zamarreno.com/?p=56 and and http://blog.jboss-portal.org/2008/09/scaling-jboss-portal-to-new-height.html >> >> This is of interest to Portal Clustering users and customers who're using Hibernate entities but not EJB3 >> beans (for EJB3 beans some of the improvements are already present there) with JBC as 2nd level cache. >> >> Cheers,

Use Hibernate style format for the property names ------------------------------------------------- Key: JBCLUSTER-212 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-212 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Hibernate-Cache-Provider Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Galder Zamarreno wrote: Hi, Chris Bredesen wrote: > I have to nit-pick though, because I'm crazy like that. > > Why choose a property name like "local.puts.only" when the rest of the Hibernate code base is consistent > with using '_', like "use_second_level_cache" or "provider_configuration_file_resource_path"? Because I didn't realise of that :) and clustering projects generally use '.' as separator more than '_'. More an oversight rather than anything else. Same with hibernate.treecache.querycache.local.writes.only. Let me figure out where to open a JIRA for this. Cheers, > > -CB > > Galder Zamarreno wrote: >> Hi, >> >> The news is out, there's a new cache provider implementation for the HB 3.2.x and JBC 1.4.x series as >> you can read from http://galder.zamarreno.com/?p=56 and and http://blog.jboss-portal.org/2008/09/scaling-jboss-portal-to-new-height.html >> >> This is of interest to Portal Clustering users and customers who're using Hibernate entities but not EJB3 >> beans (for EJB3 beans some of the improvements are already present there) with JBC as 2nd level cache. >> >> Cheers,

Use Hibernate style format for the property names ------------------------------------------------- Key: JBCLUSTER-212 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-212 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Hibernate-Cache-Provider Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 1.0.1.GA Galder Zamarreno wrote: Hi, Chris Bredesen wrote: > I have to nit-pick though, because I'm crazy like that. > > Why choose a property name like "local.puts.only" when the rest of the Hibernate code base is consistent > with using '_', like "use_second_level_cache" or "provider_configuration_file_resource_path"? Because I didn't realise of that :) and clustering projects generally use '.' as separator more than '_'. More an oversight rather than anything else. Same with hibernate.treecache.querycache.local.writes.only. Let me figure out where to open a JIRA for this. Cheers, > > -CB > > Galder Zamarreno wrote: >> Hi, >> >> The news is out, there's a new cache provider implementation for the HB 3.2.x and JBC 1.4.x series as >> you can read from http://galder.zamarreno.com/?p=56 and and http://blog.jboss-portal.org/2008/09/scaling-jboss-portal-to-new-height.html >> >> This is of interest to Portal Clustering users and customers who're using Hibernate entities but not EJB3 >> beans (for EJB3 beans some of the improvements are already present there) with JBC as 2nd level cache. >> >> Cheers,

Use Hibernate style format for the property names ------------------------------------------------- Key: JBCLUSTER-212 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-212 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Hibernate-Cache-Provider Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 1.0.1.GA Galder Zamarreno wrote: Hi, Chris Bredesen wrote: > I have to nit-pick though, because I'm crazy like that. > > Why choose a property name like "local.puts.only" when the rest of the Hibernate code base is consistent > with using '_', like "use_second_level_cache" or "provider_configuration_file_resource_path"? Because I didn't realise of that :) and clustering projects generally use '.' as separator more than '_'. More an oversight rather than anything else. Same with hibernate.treecache.querycache.local.writes.only. Let me figure out where to open a JIRA for this. Cheers, > > -CB > > Galder Zamarreno wrote: >> Hi, >> >> The news is out, there's a new cache provider implementation for the HB 3.2.x and JBC 1.4.x series as >> you can read from http://galder.zamarreno.com/?p=56 and and http://blog.jboss-portal.org/2008/09/scaling-jboss-portal-to-new-height.html >> >> This is of interest to Portal Clustering users and customers who're using Hibernate entities but not EJB3 >> beans (for EJB3 beans some of the improvements are already present there) with JBC as 2nd level cache. >> >> Cheers,