This week's giveaway is in the Spring forum.
We're giving away four copies of Microservices Testing (Live Project) and have Chris Love & Andres Sacco on-line!
See this thread for details.
Win a copy of Microservices Testing (Live Project) this week in the Spring 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:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

EJB Local vs Remote deployment environments

 
Ranch Hand
Posts: 185
Netbeans IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I'm a complete newbie to EJB and Java EE in general. I am going through this netbeans tutorial on remote EJBs, which is cool in itself. But one thing I want to know is why are they doing a tutorial on remote EJBs, when the tutorial is launching both the client app and the server side on the same app server? This is confusing me.

I was under the impression that if you use EJBs and the client and server are on the same JVM then use local interfaces, but if the client and server are on different JVMs (i.e. different computers), then use remote interfaces. This tutorial seems to go against that logic. Am I right/wrong here? Or does "remote" refer to the client and server not being a part of the same java project/deployment war/ear on the app server?

Sorry for the loaded questions!

Thanks,
Alan
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In the context of EJBs, remote refers to EJB components that belong to different applications/deployments even if they are on the same JVM.
 
Alan Smith
Ranch Hand
Posts: 185
Netbeans IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Jaikiran Pai wrote:In the context of EJBs, remote refers to EJB components that belong to different applications/deployments even if they are on the same JVM.



Thanks!
 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Jaikiran Pai wrote:In the context of EJBs, remote refers to EJB components that belong to different applications/deployments even if they are on the same JVM.



The client can also be a Java SE application that makes a lookup for the remote interface: e.g. a Java program running on a different JVM on the same or a different computer.

 
Jaikiran Pai
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Jack Dwaltz wrote:

Jaikiran Pai wrote:In the context of EJBs, remote refers to EJB components that belong to different applications/deployments even if they are on the same JVM.



The client can also be a Java SE application that makes a lookup for the remote interface: e.g. a Java program running on a different JVM on the same or a different computer.



That's true. My previous reply was meant to emphasize that the remote EJB don't necessarily mean separate JVMs.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic