users@jpa-spec.java.net

[jpa-spec users] [jsr338-experts] Re: support for multitenancy

From: Steve Ebersole <steve.ebersole_at_redhat.com>
Date: Tue, 10 Apr 2012 12:47:23 -0500

Sounds reasonable, thanks.

On Tue 10 Apr 2012 12:19:16 PM CDT, Linda DeMichiel wrote:
>
>
> On 4/10/2012 10:16 AM, Steve Ebersole wrote:
>> On 04/10/2012 11:33 AM, Linda DeMichiel wrote:
>>>
>>>
>>> On 4/10/2012 9:26 AM, Steve Ebersole wrote:
>>>>>>>> Ideally, the management of the tenant id should be transparent
>>>>>>>> to the
>>>>>>>> application, although we should revisit this in Java EE 8 as we
>>>>>>>> move
>>>>>>>> further into support for SaaS.
>>>>>>>
>>>>>>> For the application to not have to manage tenant ids, I guess the
>>>>>>> tenant identifier
>>>>>>> would need to be available to the provider on a per-invocation
>>>>>>> basis
>>>>>>> (in a thread
>>>>>>> context set by the container)? As you mention, not something
>>>>>>> that we
>>>>>>> necessarily have to worry about now, but just so we know what we
>>>>>>> will
>>>>>>> need
>>>>>>> in the future if this is what we want.
>>>>>>>
>>>>>>
>>>>>> Right. For shared application instances we will need this.
>>>>>
>>>>> You had said this would be available via ENC/JNDI before I think?
>>>>
>>>> Will the tenant identifier be available in ENC/JNDI regardless of
>>>> strategy being used?
>>>>
>>>
>>> Yes
>>
>> And will it be available from JNDI when the EMF is being built?
>
> I wasn't assuming that. I was assuming that the container would pass
> in the
> requisite information to the createEMF call, as we do today.