As I understand things, there is nothing in the specification that says
providers cannot support JTA outside a container. In fact, in our
original EJB 3.0 preview, we provided a test container that provided a
very basic JTA implementation so people could test their application
without actually being in a container. Although this test container has
not been kept up to date, I would not be surprised if eventually
customers wanted this kind of functionality.
-Tom
Marina Vatkina wrote:
>Tom, Michael,
>
>Shouldn't this element be ignored in Java SE (along with ...-datasourse
>ones) if the provider uses properties for the resource settings? There
>is no value in specifying RESOURCE_LOCAL in this case.
>
>Mike, Linda, what do you think?
>
>thanks,
>-marina
>
>Tom Ware wrote:
>
>
>>Michael and Marina,
>>
>> Michael is right. Java SE examples should be updated to use
>>RESOURCE_LOCAL.
>>
>>-Tom
>>
>>Michael Bouschen wrote:
>>
>>
>>
>>>Hi Marina,
>>>
>>>the <persistence-unit> element in the persistence.xml file has an
>>>attribute transaction-type which defaults to JTA. I think this default
>>>is not useful in a Java SE environment, so the persistence.xml file
>>>should explicitly set the attribute to RESOURCE_LOCAL in this case.
>>>
>>>We should update the persistence.xml in the Java SE available on the
>>>glassfish "Persistence Example" page. What do you think?
>>>
>>>Regards Michael
>>>
>>>
>>>
>>>
--
Tom Ware
Principal Software Engineer
Oracle Canada Inc.
Direct: (613) 783-4598
Email: tom.ware_at_oracle.com