[weld-dev] ARQ-518 - Support @PersistenceContext injection in weld-ee mock container
Ales Justin
ales.justin at gmail.com
Wed Jul 20 15:36:41 EDT 2011
Yeah, hence I mention that this could be added/done as well, as it's not.
Or is there a reason on why it's not?
On Jul 20, 2011, at 8:21 PM, Aslak Knutsen wrote:
> That is what's being done:
>
> https://github.com/arquillian/arquillian-container-weld/pull/1/files
>
> -aslak-
>
> On Wed, Jul 20, 2011 at 4:42 PM, Ales Justin <ales.justin at gmail.com> wrote:
>> public EntityManagerFactory resolvePersistenceUnit(InjectionPoint injectionPoint)
>> {
>> return null;
>> }
>>
>> This method could probably be also implemented then, with same limitations.
>>
>> On Jul 18, 2011, at 5:30 PM, Pete Muir wrote:
>>
>>> It seems ok to me as long as we document any limitations carefully.
>>>
>>> On 18 Jul 2011, at 12:01, Aslak Knutsen wrote:
>>>
>>>> Heya
>>>>
>>>> Michal has a branch of the Arquillian Weld EE Mock Containers where he
>>>> has implemented a v. of JPAInjectionService that can handle simple
>>>> creation of PersistenceContext using
>>>> Persistence.createEntityManagerFactory()
>>>>
>>>> https://github.com/arquillian/arquillian-container-weld/pull/1
>>>>
>>>> This could open up for some easy / lightweight cdi + jpa testing.
>>>>
>>>> Simply using @PersistenceContext in your CDI Beans.
>>>>
>>>> Is this useful as is, or is it to 'risky' without
>>>> TransactionManagement support etc etc etc..
>>>>
>>>> wdyt?
>>>>
>>>> -aslak-
>>>> _______________________________________________
>>>> weld-dev mailing list
>>>> weld-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>>
More information about the weld-dev
mailing list