On 06/09/2011 04:52 PM, Scott Marlow wrote:
Sounds like our JPA deployment processor needs a way to ignore
certain
applications or certain parts of the application.
Yeah, it would be for the best.
I've submitted
https://issues.jboss.org/browse/AS7-946 with a tentative approach for this.
I'm also trying something on the file exclusion thing that I mumbled
about on IRC yesterday.
On 06/09/2011 04:28 PM, Marius Bogoevici wrote:
> Just another use case to consider: Spring applications may use
> @PersistenceContext/@PersistenceUnit even though they may not use
> container-managed persistence (but Spring-created EMF beans) - moreover,
> such annotations may be found on classes which are outside of the Java
> EE injection scope.
>
>
> On 06/09/2011 04:16 PM, Bob McWhirter wrote:
>> I have no idea what any of this means, but I know people use JPA with
>> TorqueBox applications.
>>
>> Marek Goldmann put one together today. I dunno if shifting to purely
>> annotation-based would help or hurt us.
>>
>> -Bob
>>
>>
>> On Jun 9, 2011, at 3:37 PM, Scott Marlow wrote:
>>
>>> Currently, we are injecting JPA related module dependencies into
>>> applications that have valid persistence units in persistence.xml.
>>>
>>> This is wrong I think. We probably only need to look for the presence
>>> of @PersistenceUnit @PersistenceContext and same in deployment
>>> descriptors (which we currently also do).
>>>
>>> I don't want to inject the JPA dependencies just because there is
>>> persistence unit definition (we can still parse it and have it
>>> available
>>> for use).
>>>
>>> This might help us deploy native Hibernate applications that don't use
>>> EE JPA.
>>>
>>> Scott
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>