Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7190025
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T19:25:34+00:00 2026-05-28T19:25:34+00:00

In EJB 2.0 we have Home interface, and Component interface. But in EJB 3.0

  • 0

In EJB 2.0 we have Home interface, and Component interface. But in EJB 3.0 we don’t have those interfaces(instead we have annotations). My doubt is, if we don’t have those interface, then who is doing their job in EJB 3.0, and how the implementation and working (calling and callee) procedure changed??

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T19:25:35+00:00Added an answer on May 28, 2026 at 7:25 pm

    In EJB 3 you don’t need the home interface anymore, as the container is directly injecting the bean when you use the @EJB annotation

    @EJB
    MyLocalInterface bean1;
    
    @EJB
    OtherRemoteInterface bean2;
    
    String foo = bean1.doSomething();
    String bar = bean2.soSomethingElse();
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Guys, I HAVE tried reading tons of stuff about EJB. And I don't get
Lots of frameworks let me expose an ejb as a webservice. But then 2
I have a EJB bean that exposed to two interface like below: Local interface
I have an EAR without a WAR but with an EJB-JAR. One EJB inside
Considering we have some ejb's and their transaction settings are : ejb1 starts doing
I have a remote EJB with a method that validates an object (returning true
I have an old EJB (2.1) project that uses xdoclet (1.2.3) to generate the
I have a large application that uses EJB 2.x entity beans (BMP). This is
We have some JavaEE5 stateless EJB bean that passes the injected EntityManager to its
In EJB 3.0 you can write your domain objecs, then convert them into entitities

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.