Section 6.3 , the last sentence just before the start of 6.3.1 says:
� Obtain a handle for the remote home interface. The home handle can be serialized and written to stable storage. Later, possibly in a different JVM, the handle can be deserialized from stable storage and used to obtain back a reference of the remote home interface.
Why would one want to do this , given that session beans are indentical?Why would one serialize the handle and reuse it , if you gonna get a bean similar to what you had initially(i.e before serialization)?Or is this statement to make a point that "it can be done" , even though it doesn't make sense?Or i'm just not thinking hard enuff
the spec discusses Statefull Session beans as being the most common or intended type of session bean. in reality that may or may not be the case, but regardless, this handle allows you to get a reference to the component interface without going through jndi, get reference to home, create bean.
these handles aren't used much from my experience, but the test probably doesn't include only popular features.
It's the Home that's get serielized, not bean itself. Here is one way I want to use it: You can send this home handle through MDB as a message, on client side, you can get the Home without going through JNDI call. That's a big performance increase.
WHAT is your favorite color? Blue, no yellow, ahhhhhhh! Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop