This came from XPetstore-2.2.
First, tx propagation in 3.2 and HEAD differs.
Consider the following situation:
- CMP CategoryEJB with default tx attr Required;
- CategoryEJB has business method getCategoryValue with tx attr
Supports (this is not spec compliant but anyway);
- session bean PetstoreEJB with the following method:
/**
* @ejb.interface-method
* @ejb.transaction
* type="NotSupported"
*/
public CategoryValue getCategory( String categoryId )
throws FinderException
{
return getCategoryLocalHome().findByPrimaryKey(categoryId).getCategoryValue();
}
In HEAD this throws the exception saying there is no tx associated
with the current thread.
But in 3.2 it passes. I think it's a bug in 3.2, as the tx context should
be associated only with the finder (Required) but not with
getCategoryValue (Supports).
alex
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
