• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Is There any default trans-attribute value for a CMT Bean?

 
Alibabra Sanjie
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is There any default trans-attribute for a CMT Bean if trans-attribute somehow not specified? What happen if that happen? What kind of error or exception the bean or client will receive?
[ April 18, 2004: Message edited by: Alibabra Sanjie ]
 
Nathaniel Stoddard
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Alibabra,
Transaction attributes must be specified by the time it is deployed! (The spec says). Now that's about of the way: some containers may be more lenient. I know that when I deploy stuff in JBoss 3.2.3, it doesn't complain when I don't have any specified. I'm sure it assigns some default, but that's on a server-specific level. I'm supposed to have done it by the time I drop it in the deploy directory.
As far as the EJB spec is concerned though--there's no default. It's a mandatory portion of the deployment descriptors by the time it's deployed. (Officially, it's the job of the "Deployer" role to make sure that all methods the client can invoke have transaction attributes in the DD).
 
Victor Larr
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For WebSphere default is "Required"
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic