[wildfly-dev] PicketLink pulling in JPA (Was: Changes to the PicketLink Module)

[David M. Lloyd]

On 08/05/2013 05:34 PM, Bill Burke wrote:
>
>
> On 8/5/2013 5:53 PM, Jason Greene wrote:
>>
>> On Aug 5, 2013, at 3:26 PM, Bill Burke <bburke at redhat.com> wrote:
>>
>>> Not sure I agree with your perspective on this anymore.  JPA is
>>> something that does not require Wildfly to run.  You can use it
>>> in library/resource-locale mode if desired.  WTF do we have JBoss
>>> Modules if we can't use it to scope services exactly like this?
>>
>> The integration with JPA is complex in that it needs to do scanning
>> of classes, reflective analysis, annotation analysis, bytecode
>> generation, etc. The SE implementations assume all kinds of things
>> like you can just go back and forth between Files and Jar URLs to
>> do the scanning bit. You also need multiple class loaders in this
>> very ugly stupid SPI so that various implementations can load the
>> classes analyze them, then throw them away generate new classes and
>> get those reloaded in a new class loader.
>>
>
> IIRC, JPA doesn't require scanning either.
>
>> There are other issues as well, like someone implements something
>> that is tied to hibernate (pretty easy to do) or a specific version
>> of hibernate.
>>
>
> So why can't this be solved by JBoss Modules?

It can be, easily.  It's not a technical limitation, just not a great 
idea.  We could support a dozen Hibernate versions at once, and 
EclipseLink and whatever else besides, if we wanted to.  We just 
wouldn't want to.  Modules isn't the problem here.

-- 
- DML