Why can't a Stateless SEssion Bean implement the SessionSynchronization interface? it might also want to be notified of the transaction events.

Created May 4, 2012

facebook
twitter
in
Email

Alessandro A. Garbagnati

It's just because a Stateless Session Bean does not have state. The container does not guarantee (like for the Stateful SEssion Bean) that the bean that will be used on two method calls, will be the same.

Post a comment
Email Article
Print Article

The Java Game Development Tutorial
Files and Directories in Java
Load Testing your Applications with Apache JMeter
Unit Testing Java Programs
Using SOAP with Java

Advertiser Disclosure: Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.