Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

EJB client jar on Weblogic 8.1

 
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I deployed a Stateless Session Bean on Weblogic 8.1 (which is EJB 2.0 compliant). I believe we need the Remote Component Interface and Remote Home Interface stub classes generated by the container are required by the client if we are looking up and invoking a business method on EJB from a remote client (from different JVM).

But I could invoke the EJB from a remote client with only the Remote Component Interface and Home Interface on the classpath of the client (without even getting the stub implementations from the container).

So is this something specific the Weblogic that it provides the stub classes on the fly to the client upon request (a feature similar to downloadable class files)? Or is this feature defined by EJB 2.0 spec?

Thanks in advance.

Regards,
Pranav
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do your build (I do it with the wlappc Ant task) which will cause the RMI compiler to run in order to generate the dymamic proxies.
 
Pranav Shukla
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am not using wlappc or any other build utility. I had compiled the interfaces and the bean class by having weblogic.jar on classpath. Then I supplied the client with only compiled Remote Interface and Remote Home Interface (without using weblogic.ejbc EJB compiler for generating stubs).
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic