• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

I have seen crazy things, but this takes the cake!!!!

 
Ahmad, Usman
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi. I am using WebSphere 4.0.2 to get some hands on experience with EJBs. I THINK I got all the concepts and stuff about EJBs in general. It's my first venture so bear with me....
I have an EJB (stateless) all coded with just one public function (remember, I am venturing in unknown territory). I now have two probs...
1) What has EJB Spec 1.1 recommended in place of java.rmi.RemoteException?
2) When all is said and done(Generated RMIC code and all with any errors) and I 'Run On Server' my EJB Bean, it only detects the Home interface but not the public method! I looked at all the example EJBs I could find but I can't seem to see what I may be(or may ot be) doing. The Remote Interface has the proper function declared also. Any ideas, anyone?
 
Tim Holloway
Saloon Keeper
Posts: 18300
56
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1. EJB1.1 did not replace the RemoteException, it simply removed it from the exceptions that you declare your bean methods from throwing. If your method needs to throw an exception, just use one of the EJB exceptions (such as NotFound) if it's applicable or create a new class based on java.lang.Exception and throw an instance of it.
When you deploy into WebSphere 4 you shouldn't have to manually run an RMIC unless I'm greatly mistaken. My understanding is that the RMIC and other interfacing code is handled by WebSphere itself using the DeploymentDescriptor you provided with the EJB. But the best place to get an answer is to ask in the JavaRanch's WebSphere forum.
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good idea - moving this to the Websphere forum...
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ahmad,
My understanding is that you are using WSAD with WTE (not WebSphere). Please correct me if I'm wrong.
The problem you describe seems to be within the EJB test client, right ?
The methods of your remote interface cannot be invoked before the create method of the home interface is executed. What occurs when you do that ? Check the WTE log for any error message...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic