Hello Sahoo, Rima,
I truly believe you should file a bug.
Whatever the outcome, it'll be more easy to trace
for other people facing this very same issue.
thanks,
-Alexis
Sahoo a écrit :
> Hi Rima,
>
> Yes, I am aware of those wordings. They don't cover the scenario you
> have come across. Not sure, why the spec authors did not clearly cover
> that scenario. Although I agree with you as far the intention of the
> spec goes, I think your interpretation can be challenged.
>
> Thanks,
> Sahoo
>
> glassfish_at_javadesktop.org wrote:
>> Sahoo,
>>
>> I thought that you'd like to know about this in the JPA spec. Under
>> 5.7, I found the following:
>>
>> "When a JTA application-managed entity manager is used, if the entity
>> manager is created outside the scope of the current JTA transaction,
>> it is the responsibility of the application to associate the entity
>> manager with the transaction (if desired) by calling
>> EntityManager.joinTransaction."
>>
>> Not sure if this can be construed as:
>>
>> When a JTA application-managed entity manager is used, if the entity
>> manager is created outside the scope of the current JTA transaction,
>> the provider [b]will not[/b] associate entity manager with the
>> transaction without a call to EntityManager.joinTransaction.
>>
>> Regards,
>> Rima.
>> [Message sent by forum member 'rpatel' (rpatel)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=223536
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>