• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Remote Interface and Related Classes.

 
Ranch Hand
Posts: 395
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 120
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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
 
Ranch Hand
Posts: 125
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 250
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Ranch Hand
Posts: 125
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
I didn't do it. You can't prove it. Nobody saw me. The sheep are lying! This tiny ad is my witness!
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic