Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Session beans, WSAD, and Servants  RSS feed

 
Kathy Smith
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anyone out there have any experience with EJBs using WSAD as the IDE? I have been testing EJBs and yesterday I started getting the error:
IWAD0402E Could not perform lookup with the JNDI name: Servant is not of the expected type.
Nothing has changed in my environment that I'm aware of, and I checked the usual culprits (generate and deployed with wrong jdk, jndi names incorrect, not deployed to server correctly, etc.) but everything seems to check out. I am at a loss to explain this sudden behaviour. Was hoping someone else has seen this and knows what it is.
 
Byron Estes
Ranch Hand
Posts: 313
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by codeparody:
Anyone out there have any experience with EJBs using WSAD as the IDE? I have been testing EJBs and yesterday I started getting the error:
IWAD0402E Could not perform lookup with the JNDI name: Servant is not of the expected type.
Nothing has changed in my environment that I'm aware of, and I checked the usual culprits (generate and deployed with wrong jdk, jndi names incorrect, not deployed to server correctly, etc.) but everything seems to check out. I am at a loss to explain this sudden behaviour. Was hoping someone else has seen this and knows what it is.

I use WSAD and I have found it to do some strange things at times, but I've never gotten the error you describe.
I believe the error comes from the Delegate class in CORBA. (org.omg.CORBA.portable --Class Delegate). I'm sure it's not your code, but probably the code WSAD creates for you when you deploy it to your container.
If I were you, I would try deleting all the generated code (...be careful not to remove your own home/remote interfaces, primary key/bean classes) and then regenerate/rmic.
I bet that will solve your problem.
Regards,
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Moving this to the WebSphere forum...
Also, "codeparody",
Thanks for joining JavaRanch, but could you just take a quick look at the naming policy and edit your profile accordingly.
Thanks!
Simon
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you have this problem testing the EJB within the WTE or with "a real" WebSphere.
Did you regenerate the RMIC code ?
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!