Type: Feature Request
Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: Hib-Cache 1.0.1.GA
Affects:Documentation (Ref Guide, User Guide, etc.), Release Notes
Similar Issues:Show 10 results
JBCLUSTER-278 ClusterPartition should not send service name twice per message JBCLUSTER-150 CNFE issues with Hibernate and JBoss Cache JBCLUSTER-289 Eliminate use of ProtocolStackConfigurator, ProtocolData, ProtocolParam JBCLUSTER-52 Provide description for all JGroups MBean configuration elements JBCLUSTER-284 Deprecate use of term "partition" (HAPartition, ClusterPartition, etc) JBCLUSTER-206 Enhanced Jboss Cache 1.4.x and Hibernate 3.2.x integration JBCLUSTER-9 Entity cache replication in ejb3 JBCLUSTER-293 Reimplement distributed sessions using single cache instance for all web applications JBCLUSTER-290 Not able to create a distributed cache JBCLUSTER-27 Create a new overall architecture diagram for ejb3/j2ee15 for server side replication
Galder Zamarreno wrote:
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.
> Galder Zamarreno wrote:
>> 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.