Fixed in 2.4. Bug base is at
http://sourceforge.net/tracker/?group_id=22866&atid=376685
although a quick search didn't yield any
hits.
Fred LoneySpirited Software, Inc.www.spiritedsw.com
- Original Message -
From:
Eric Lindauer
To: [EMAIL PROTECTED]
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 element.
According to the spec, I can set a default on all the methods by using
* for one transactional setting, and
then setName 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.
the
ARemote session
bean ARemote com.hcm.tools.test.ARemote com.hcm.tools.test.ARemote_Home com.hcm.tools.test.ARemote_Remote com.hcm.tools.test.ARemote_Bean Stateful Container
com.hcm.tools.test.ARemote* Never com.hcm.tools.test.ARemoterequiresNew RequiresNew