Win a copy of Svelte and Sapper in Action this week in the JavaScript 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
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

what methods do you put in EJB remote interface?

 
Ranch Hand
Posts: 257
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
what methods do you put in EJB remote interface?
(a)defines signatures of EJB business methods
(b)defines all methods that client can call on EJB.

it seems both A and B correct. According to my idea only A is correct because we wont put create() and remove() methods in remote interface?
 
Ranch Hand
Posts: 97
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"defines signatures of EJB business methods" seems to be the right answer.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by yamini nadella:
because we wont put create() and remove() methods in remote interface?



Why wouldn't you but create() and remove() methods in remote interfaces?
 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
create() is supposed to be in home interface, isn't it?
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Correct. So create() isn't any help at all. But then there is remove(). remove():void is introduced through the javax.ejb.EJBObject interface along with getEJBHome():EJBHome, getHandle():Handle, getPrimaryKey() bject, isIdentical(o:EJBObject):boolean when you extend fron the EJBObject. So remove() has to be there but its there through interface inheritance. So in fact you "only" define the business method signatures with their return type in your interface.

You do implement an ejbRemove() in your bean - but thats not what the question is asking.

Note that the question is inaccurate in its use of the term signature; a signature consists of the method name and the parameter types but it does not include the method's return type - and you will have to specify the methods return type in the remote interface.
[ October 12, 2005: Message edited by: Peer Reynders ]
 
I'm so happy! And I wish to make this tiny ad happy too:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic