1.A stateless session bean must not implement the SessionSynchronization i
interface.why is this?. Does this implies that stateless beans cannot
participate in transaction. i am sure they can have transactions.Then
please explain this.
2.Are these callback interceptor methods are mandatory.
3.In section 4.3.11 . Stateful session bean has one or move remove methods
why do we need more than one remove methods.
Are there any differences the way in which container acts when we access
the session object
1. Through Dependency injection (DI)
2. JNDI lookup.
As of EJB3.0,
a)when we do a JNDI lookup what do we get as a result.Is it the referece to the stub of a EJBObject or something else?.
b) what does the Dependency injection gives?.
5. what is the significance of the methods getBusinessObject() and
getInvokedBusinessInterface().where they are useful
When the client calls a business method of the bean that has been designated as a Remove method, or a remove method on the home or component interface, the container invokes PreDestroy lifecycle callback interceptor method(s) (if any) for the bean instance after the Remove method completes.
Originally posted by Senthil Kumar SS:
in continuation with the earlier doubts,
what do they mean by designated remove method here.As we know already if the bean class implements SessionBean then the ejbRemove only can be annotated as PreDestroy callback. But why do we need to designate a business method as remove , when we already have a ejbRemove()/PreDestroy() for that.
My first bit of advice is that if you are going to be a mime, you shouldn't talk. Even the tiny ad is nodding:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earthhttps://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter