Win a copy of Head First Android this week in the Android 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Can I use local interface?

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi experts,

I am running WebLogic 8.1 sp3.

I have 2 ejb modules (2 x ejb jar files) each with only 1 EJB.

I deploy each module to the same managed server but it seems I cannot use the local interfaces to call 1 EJB from the other.

I thought this would be ok because these bean will run in the same JVM.

Can someone explain why I must use the remote interfaces? Did I do something wrong?
 
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You must use local interfaces when you have all EJB calls contained in one EAR or one jar file.

As you are packaging one ejb in one jar file and second one in second jar.
And you are also deploying these two ejb's seperately.

If you still want to use local interface.
you can do it by making an EAR file that will contain two jars
one for EJB1
and second for EJB2.
 
Kelly Walker
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have create a single ear file and everything now works fine. Thanks for the help.

Just out of interest can someone explain what weblogic is doing under the hood when the ejb jar files are deployed seperately that means only remote interfaces will work.

Do each managed server have its own JVM? If so then these beans should share the same JVM and local interfaces should work right? Is it a further restriction on classloaders.

WebLogic experts please explain what is happen under the hood.
reply
    Bookmark Topic Watch Topic
  • New Topic