• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Upward compatibility issue

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
I am having some problem with the code developed on 1.3.1 edition, and now running on 1.4.0
Actually i have a session bean and a client. The client gets the initialContext and then
performs a JNDI lookup for the bean. The code for JNDI lookup is as shown -
SessionHome home = (SessionHome)context.lookup(BEAN_JNDI_NAME);
Session remote = (Session)home.create();
where, 'SessionHome' is the Home interface for my bean
and 'Session' is the Remote interface.
While this ClassCasting is perfectly fine in 1.3.1, it gives error with the 1.4.0
The exception raised is ofcourse 'ClassCastException'. That means it's not allowing the casting
of bean object to its subclass home object.
The exception persist even with RMI-IIOP (PortableRemoteObject method).
This seems to be a loose-end in 1.3.1 which must have been fixed in 1.4.0
If it is so, then how to go ahead with JNDI lookup in 1.4.0 ?
Relevent Details:
Platform -> Solaris 7
EJB -> 2.0
regards,
Rushikesh
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic