[jboss-as7-dev] Modularity is the spawn of Lucifer and a stinking donkey

[David M. Lloyd]

On 05/23/2012 10:10 AM, Steve Ebersole wrote:
>
>
> On 05/23/2012 09:11 AM, David M. Lloyd wrote:
>> On 05/23/2012 09:09 AM, Steve Ebersole wrote:
>>> On Wed 23 May 2012 09:01:27 AM CDT, David M. Lloyd wrote:
>>>> We don't ship them. Only our provided Hibernate(s) would need such a
>>>> hook. If the customer bundles it in their deployment, we don't need to
>>>> do anything like this anyway.
>>>
>>> Well you are assuming that mixing app-bundled jars and AS-provided jars
>>> is not allowed. Consider the application bundling some Hibernate ORM
>>> version but still wanting to use the AS-provided Hibernate OGM version
>>> (with requisite deployment descriptor). If this is allowed, we do
>>> absolutely still have to "do this".
>>
>> Doesn't OGM have a link-time dep on ORM, thus making this impossible?
>
> Yes, OGM has a link-time dependency on ORM. I am not following why that
> precludes the set up I mentioned.

Because if the user bundles an ORM and tries to use our OGM, you'll get 
CCEs if you try to get it to use the in-container OGM because OGM is 
linked against the in-container ORM.  Modules aren't class paths, 
they're class loaders; you only get one copy of each class.

I think if the user bundles their own hibernate core, they should be on 
their own.

-- 
- DML