Fixed in 2.4. Bug base is at
although a quick search didn't yield any hits.
 
Fred Loney
Spirited Software, Inc.
www.spiritedsw.com
----- Original Message -----
Sent: Thursday, September 20, 2001 2:38 PM
Subject: [JBoss-user] transactional settings on methods

Hi,
 
I am trying to setup transactional settings on the methods of a bean via the <assembly-descriptor> element.  According to the spec, I can set a default on all the methods by using <method-name>*</method-name> for one transactional setting, and then <method-name>setName</methodName> for another.
 
When I try this, the bean acts as though the setting I created with * is set for all the methods, even those that have been overriden to some other setting.  Do I misunderstand the spec?  Might this be a bug?
 
I've included my (edited) ejb-jar.xml file to help.  Thanks for any suggestions you may have.
 
    -Eric
 
PS.  Is there a list of known bugs that I can search someplace?  I apologize if this is a known issue.
 
<ejb-jar>
 <enterprise-beans>
  <session>
   <description>the ARemote session bean</description>
   <display-name>ARemote</display-name>
   <ejb-name>com.hcm.tools.test.ARemote</ejb-name>
   <home>com.hcm.tools.test.ARemote_Home</home>
   <remote>com.hcm.tools.test.ARemote_Remote</remote>
   <ejb-class>com.hcm.tools.test.ARemote_Bean</ejb-class>
   <session-type>Stateful</session-type>
   <transaction-type>Container</transaction-type>
  </session>
 
 </enterprise-beans>
 <assembly-descriptor>
  <container-transaction>
   <method>
    <ejb-name>com.hcm.tools.test.ARemote</ejb-name>
    <method-name>*</method-name>
   </method>
   <trans-attribute>Never</trans-attribute>
  </container-transaction>
  <container-transaction>
   <method>
    <ejb-name>com.hcm.tools.test.ARemote</ejb-name>
    <method-name>requiresNew</method-name>
   </method>
   <trans-attribute>RequiresNew</trans-attribute>
  </container-transaction>
 </assembly-descriptor>
</ejb-jar>

Reply via email to