transaction-type

If I have a session bean marked with

<transaction-type>Bean</transaction-type>

in ejb-jar.xml

but also this...

<container-transaction >

<method >

<ejb-name>SdskatEjbSB</ejb-name>

<method-name>*</method-name>

</method>

<trans-attribute>required</trans-attribute>

</container-transaction>

<container-transaction >

<method >

<ejb-name>SdskatEjbSB</ejb-name>

<method-intf>Remote</method-intf>

<method-name>koordination</method-name>

<method-params>

<method-param>dk.modulus.drift.jobtrin.to.JobtrinContext</method-param>

<method-param>dk.modulus.drift.jobtrin.ydelser.sdskat.SdskatParam</method-param>

<method-param>dk.modulus.drift.jobtrin.ydelser.sdskat.SdskatKvittering</method-param>

</method-params>

</method>

<trans-attribute>NotSupported</trans-attribute>

</container-transaction>

is the last part just ignored by the container ?

Kris

[1195 byte] By [klindpa] at [2007-10-3 5:23:21]
# 1
Yes, it's ignored. None of the container-managed transaction information in the assembly portion of thedescriptor applies if the bean has bean-managed transactions. In fact, it would be better to remove it since it's confusing. --ken
ksaksa at 2007-7-14 23:30:26 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...