Hi,
I'm creating <container-transaction> elements
to control the transactional properties of methods in my application. I've
noticed that the <method-name> element accepts "*" as a valid
entry.
I'm wondering, how does JBoss resolve conflicts
that might be caused by this? For example, I'd like to say, for a
particular bean, that all the methods are of transactional type "Supports",
except for one, which is "Required". Is this legal?:
<assembly-descriptor>
<container-transaction>
<ejb-name>MyBean</ejb-name>
<method-name>*</method-name>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>
<ejb-name>MyBean</ejb-name>
<method-name>needsATransaction</method-name>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
My testing on JBoss seems to indicate that JBoss
resolves this correctly, and that order does not matter. I'm wondering, is
this just lucky for me, or is this the specified behavior for resolving methods
in the spec? I can't find a place in the specification that talks about
how methods resolution should work in the event that there are conflicts in the
<assembly-descriptor>.
Thanks in advance for any help.
-Eric
|
- SV: [JBoss-user] <assembly-descriptor> element Eric Lindauer
- SV: [JBoss-user] <assembly-descriptor> elemen... Lennart Petersson