On Feb 7, 2012, at 16:05 , Scott Marlow wrote:
> The use case for duplicate EntityManagerFactory, would be the application
> that is depending on the persistence unit name that may or may not be
> unique across multiple application deployments.
Or many integration test environments. Test setups
The current API reads:
public interface ParameterizedBridge {
//TODO inject Properties? since the annotations cannot support Object
attribute?
void setParameterValues(Map parameters);
}
Shall we apply the TODO, or at least change it to specify the expected
Map types?
public inter
On 02/08/2012 04:23 AM, Christian Bauer wrote:
> (For whatever reason, I still don't understand why EMF clustering would be
> different than SF clustering.)
This is exactly the point I am missing here as well.
--
st...@hibernate.org
http://hibernate.org
_
+1
On Feb 8, 2012, at 5:05 AM, Sanne Grinovero wrote:
> The current API reads:
>
> public interface ParameterizedBridge {
> //TODO inject Properties? since the annotations cannot support Object
> attribute?
> void setParameterValues(Map parameters);
> }
>
> Shall we apply the TODO
http://lists.jboss.org/pipermail/infinispan-dev/2012-February/010125.html has
more context.
Since there are no easy/quick fixes that can be applied at this time, to
remove the AS7 Infinispan dependency on the Hibernate-Infinispan module,
I think we should avoid depending on the service loader w
It wouldn't be difficult to switch back to using UUIDs in the EMF.
Neither way is perfect (see discussion on HHH-6897).
On 02/08/2012 08:28 AM, Steve Ebersole wrote:
> On 02/08/2012 04:23 AM, Christian Bauer wrote:
>> (For whatever reason, I still don't understand why EMF clustering would be
>>
Scott, what do you suggest doing instead then? Without the commands, evictAll
invalidation won't work.
Are you suggesting that I revert back to using the cache as a notification bus
so that regions are invalidated?
On Feb 8, 2012, at 4:13 PM, Scott Marlow wrote:
> http://lists.jboss.org/piperm
On 02/08/2012 10:25 AM, Galder Zamarreño wrote:
> Scott, what do you suggest doing instead then? Without the commands, evictAll
> invalidation won't work.
>
> Are you suggesting that I revert back to using the cache as a notification
> bus so that regions are invalidated?
For the clustered case
Btw, I'd rather go with Paul's suggestion to modify AS7 Infinispan subsystem.
Also, reverting to the old way of using the cache as a notification bus won't
work as is because it relied on using the same cache as for
entiies/collections, and it relied on 5.0.x or before logic that caches could
b
If I understand correctly you are thinking there is a case where the
"PU name" would not be unique for a given app? That is the only time
I can see this being a concern. If it is possible that the same app
can have different PU names on different nodes in the cluster then
simply using PU name as
I'll set the EntityManagerFactory name to:
(1) explicit AvailableSettings.SESSION_FACTORY_NAME if specified
(2) use application specified pu-name if pu-name is specified (not
always the case, especially in test environments)
(3) uuid
On 02/08/2012 11:08 AM, Steve Ebersole wrote:
> If I understa
Ah, nice. I did not even think of reusing SESSION_FACTORY_NAME for the
EMF name, but that should work well.
On Wed 08 Feb 2012 01:26:30 PM CST, Scott Marlow wrote:
> I'll set the EntityManagerFactory name to:
>
> (1) explicit AvailableSettings.SESSION_FACTORY_NAME if specified
> (2) use applica
Both 4.1.0 and 3.6.10 were released today.
http://in.relation.to/Bloggers/HibernateORM410Release
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate
13 matches
Mail list logo
