I tested the recent multi-tenant code in hibernate 4 and it works well
in the mode of the test case (manual session creation). Thanks guys,
great work.
My question is about support for what I see as the more normal usage of
SessionFactory getCurrentSession(). Looking at the current code I canno
Good point. To be honest I have not thought much about it. Do you have
suggestion(s)?
Not sure I much like overloading for getCurrentSession(String
tenantIdentifier)
On 06/20/2011 02:57 AM, Peter Yuill wrote:
> I tested the recent multi-tenant code in hibernate 4 and it works well
> in the m
On 20/06/2011 11:11 PM, Steve Ebersole wrote:
> Good point. To be honest I have not thought much about it. Do you have
> suggestion(s)?
>
> Not sure I much like overloading for getCurrentSession(String
> tenantIdentifier)
Doesn't make sense to me either. How about tenantId set on a
ThreadLocal.
If this were the direction, I'd rather suggest a
"CurrentTenantIdentifierResolver" contract registered with the
SessionFactory.
Just brainstorming... this might also be usable from ConnectionProvider
and eliminate the need for
org.hibernate.service.jdbc.connections.spi.MultiTenantConnectionPro
+1 for a CurrentTenantIdentifierResolver contract registered with the
SessionFactory.
This seems like a reasonably flexible approach.
Donnchadh
On 20 June 2011 15:06, Steve Ebersole wrote:
> If this were the direction, I'd rather suggest a
> "CurrentTenantIdentifierResolver" contract register
On 06/17/2011 07:22 AM, Steve Ebersole wrote:
> I remember Scott and I discussing this exact issue. Unfortunately I do
> not remember the specifics. java.util.ServiceLoader#load(Class
> service) does use the TCCL, but I think that the end result of our
> discussion was this is ok.
>
> We need to h
On Jun 20, 2011, at 11:01 PM, Scott Marlow wrote:
>
> On 06/17/2011 07:22 AM, Steve Ebersole wrote:
>> I remember Scott and I discussing this exact issue. Unfortunately I do
>> not remember the specifics. java.util.ServiceLoader#load(Class
>> service) does use the TCCL, but I think that the end
[06/20/11 11:33] Meeting ended Mon Jun 20 16:33:26 2011 UTC.
Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[06/20/11 11:33] Minutes:
http://people.redhat.com/~manderse/irc.freenode.org/meetings/hibernate-dev/2011/hibernate-dev.2011-06-20-15.04.html
[06/20/11 11:33] Mi
Hi,
all the information you need on in.relation.to -
http://in.relation.to/20882.lace
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> and adding envers into org.hibernate module, means there will no
> org.hibernate.envers module, and a (jpa) app's classloader can access
> org.hibernate module, right? so it can access envers class too.
Wrong, just adding envers to org.hibernate (either via a module
dependency or the jar di
FYI I've created
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-778 to gather
this need.
On 1 juin 2011, at 12:42, Sanne Grinovero wrote:
> 2011/6/1 Emmanuel Bernard :
>>
>>>
>>> I dislike "orm" as it's too generic, we don't want to imply to support any
>>> orm.
>>>
>>> W
>> 2. Specific issues:
>> o org.hibernate.search.batchindexing.impl.Executors is used by
>> MutablefactoryTest
>> should we keep executors as private or should we consider it an actual API
>> or SPI?
>
> I don't think exposing this as SPI is very useful to people, but at
> some point in future
Hi,
Apologies for any inconvenience and thank you to those who have already
completed the survey. We will keep the survey open for another couple of
weeks. But, we do hope you will consider responding to the email request
below (sent 2 weeks ago).
Thanks,
Dr. Jeffrey Carver
Assistant Professor
U
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6336
On 06/20/2011 09:29 AM, Donnchadh Ó Donnabháin wrote:
> +1 for a CurrentTenantIdentifierResolver contract registered with the
> SessionFactory.
> This seems like a reasonably flexible approach.
>
>Donnchadh
>
>
> On 20 June 20
In looking at
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6338 I
really started digging into this notion of "binding state" and
specifically EntityBindingState.
I ran into a question. I don't quite follow reasons for some of the
details here. For example, I do not get why w
On Jun 21, 2011, at 1:56 AM, Scott Marlow wrote:
>>
>> and adding envers into org.hibernate module, means there will no
>> org.hibernate.envers module, and a (jpa) app's classloader can access
>> org.hibernate module, right? so it can access envers class too.
>
> Wrong, just adding envers to
On Jun 20, 2011, at 7:56 PM, Scott Marlow wrote:
>>
>> and adding envers into org.hibernate module, means there will no
>> org.hibernate.envers module, and a (jpa) app's classloader can access
>> org.hibernate module, right? so it can access envers class too.
>
> Wrong, just adding envers to
17 matches
Mail list logo
