This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem with HF-EJB Chap 01 example

 
Subhash Bhushan C
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Guys,

I am using HF-EJB for my preparation towards SCBCD (just started).
In chap 1, I have followed all the instructions mentioned to deploy the AdviceBean EJB. I have deployed it successfully. But when I run the client, I get this error message.

*************************************************
E:\Java\SCBCD\Projects\Advice>java -cp %CLASSPATH%;AdviceAppClient.jar AdviceCli
ent
java.rmi.RemoteException: CORBA BAD_OPERATION 0 No; nested exception is:
org.omg.CORBA.BAD_OPERATION: minor code: 0 completed: No
org.omg.CORBA.BAD_OPERATION: minor code: 0 completed: No
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc
eption(ReplyMessage_1_2.java:93)
at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException(
ClientResponseImpl.java:108)
at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli
entSC.java:132)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:454)
at headfirst._Advice_Stub.getAdvice(Unknown Source)
at AdviceClient.go(AdviceClient.java:20)
at AdviceClient.main(AdviceClient.java:9)
********************************************************


The structure of files is as mentioned in the book.
Where did I go wrong?
 
Chetan Sahasrabudhe
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

This is the problem faced by each and every one of us. I guess you are using Sun's Ref. Implementation, and hence you will get this error.

There is a known defect in RI, if your remote, home interface name and method name is within the interface is matching, and then you get this error.

Make sure that any of the method names are not same (any case) as that of interface names. Just add some prefix or postfix to the method name. Make sure you do the same change in your bean class, compile and deploy the bean again.

Mostly you will be able to run the code.
 
Subhash Bhushan C
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Such a simple reason for such a complex error I bet I would have gone about searching for days together before I found out the reason. Makes all the more reason to learn from people who have traversed the same path....

Thank you soo much Chetan. Kudos.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic