I'm trying to understand to difference between the stateless and stateful bean. I had created an simple application to test it. But both the beans seems to work in the same way. Could some one explain me with an example the difference between the stateful and stateless bean ... I'm using J2EE Reference Implementation and Deploytool . Please help me .. Urgent .... Cheers !!! Prabs
The effect - though not the practice of stateless session beans is that they are created, called, then destroyed. Nothing can be retained between calls. They're just collections of business methods. Stateful session beans, on the other hand, are distinct objects - you can store something in a stateful bean on one call and retrieve it on another. Thus, stateful session beans are like entity beans except that they don't have the extra stuff for long-term persistence - and have no unique key, so you have to track which is which yourself.
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
0
