Transaction configurations in XPetstore-2.2 aren't spec 2.0 compliant.
CMP beans can have only Required, RequiresNew or Mandatory tx
attrs, while in XPetstore we can meet Supports and even NotSupported
(Account.getUserId()).

I didn't run the XPetstore on 3.0 but I ran it on JBoss-3.2RC2 and
HEAD.
In RC2 I was able to browse the catalog but something's wrong with
the shopping cart: the state is just not stored.
In HEAD, I couldn't even browse the catalog due to the exception saying
there is not tx associated with the current thread.

Changing tx attributes to Required fixes the problem.

PS: below is the relevant excerpt from the spec.

alex

17.4.1 Transaction attributes
...
For entity beans that use EJB 2.0 container-managed persistence, only the Required,
RequiresNew, or Mandatory transaction attributes should be used for the methods 
defined in the
bean’s component interface and all the direct and indirect superinterfaces of the 
component interface,
excluding the getEJBHome, getEJBLocalHome, getHandle, getPrimaryKey, and isIdentical
methods; and for the methods defined in the bean’s home interface and all the direct 
and
indirect superinterfaces of the home interface, excluding the getEJBMetaData and 
getHomeHandle
methods specific to the remote home interface. Containers may optionally support the 
use of the
NotSupported, Supports, and Never transaction attributes for the methods of entity 
beans with
container-managed persistence. However, entity beans with container-managed 
persistence that use
these transaction attributes will not be portable.




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to