Remote Interface and Related Classes.

[L Goundalkar]

Hi,

In HFEJB book in architectural overview chapter, the lady (Kathy ???) says that we need to ensure the classes for the serialized objects returned as result of remote method call should be present on the client side. Also the calsses for the stub. Well thats fine.
On the next page we have explanation for Remote Business Interface which will help in letting the client know the business methods available in the remote object. If this interface is "Remote" then how this can be sent to client !!?

Bit confusing for me.
Can anyone please explain.

Cheers.

[Miki Muzsi]

If this interface is "Remote" then how this can be sent to client

The client application has a jar file containing the interface (class file) that represents the component (remote) interface that your ejb implements. At client side you also have a stub that implements that interface and this stub makes sure he can comunicate with the remote object (EJBObject).

Miki

[KasiMurugan Ramasamy]

U have to pack those interfaces(Home and EJBObject) as well as Helperclasses.

Some container tools generate client jar when deploying the jar. We have to make this jar available in the client side.

[sawan parihar]

Some container tools generate client jar when deploying the jar. We have to make this jar available in the client side.

Not in all cases some container will make dynamic proxies.


sawan

[KasiMurugan Ramasamy]

Hi sawan,

Yes, i agree with you.

That time we don't need to pack the stubs(For Home and EJBObject). But any way we need the interfaces( Home and Component interfaces) in client side for compiling the client. Am i right?.

Thanks & Regards
Kasimurugan R.