Kathy: can you explain in more detail about local interfaces and do we need again a corresponding local home interface to create/lookup the local interface?? thanks
I always wondered why do we have 2 interfaces. I understand the benefit of local interfaces, to bypass RMI and increase performance. Why does the developer take the burden of developing another interface for the bean to be used locally. At the time of deployment, let the deployer tool generate all the neccesarry classes for both local and remote use. Can the Vendor not identify the bean(if the bean is deployed locally or not) and use the corresponding classes. Can't the Vendor's container be smart [ October 29, 2003: Message edited by: Vish Kumar ]
naing, my question is..since local interface is on the same process as the EJB Component, we can always get a reference to that..right. Then , why again going through local home interface and use create/lookup for getting the reference, just why cant we use "new" and get the reference??
Hi Local interfaces are typically used while using the entity beans .In a typical scenario one would like to make a request to a stateless session bean which in turn would like to aggregate a whole bunch for entity beans .The entity beans in order to implement the Aggregate patterm would make use of local home interfaces and gives the data required to the stateless bean .This is typically known as Session Facade pattern. Typically you wont be doing a look up using local home interface as they would be bundled in the samee ejb-jar.xml Rishi SCJP,SCWCD,IBM OOAD
this may be other use of a local interface..but according to EJB 2.0 spec., you can call enterprise beans in a fast and efficient way by calling them through their local object rather than by EJB objects and local objects implement "local interface" rather than remote interface...My question is again whats the use of "local home interface" here and is local home interface necessary?
IMO,What pradeep meant was,the use of interfaces enables location transparency of a bean.You can access a co-located Bean today using local interface.later,if the situation requires the bean to be deployed in a remote location,you still can use its services by accessing it via remote interface.Isnt it pradeep?
Hi, I think what Siva and Pradeep pointed out earlier was fair enough, one would like to expose both the local and remote interfaces and depending upon where it is deployed , either of two can be made use of. Rishi SCJP,SCWCD,IBM OOAD
Post by:autobot
Story like this gets better after being told a few times. Or maybe it's just a tiny ad:
a bit of art, as a gift, that will fit in a stocking
![[Logo]](/templates/default/mobile/images/mobile-moose.gif)
