• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

AdviceApp from HeadFirstEJB

 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After having tried to get the AdviceApp running on the new J2EE 1.4 for some time, I gave up frustrated. Making the application run on 1.3.1 was then really no problem, just a matter of some minutes if you follow the steps in the book...and if you know how to fix the corba bad operation exception.
Just out of curiosity: has anybody successfully deployed and run the application on J2EE 1.4??? I always got a javax.naming.CommunicationException: Can't find SerialContextProvider and couldn�t find anything on the net that helped solving the problem.
---------------------------------------------------------------------------
SCJP (96%)
SCJD (154/156)
 
Ranch Hand
Posts: 188
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to get the Advice application running and I am running into the above mentioned CORBA BAD_OPERATION Exception when I run the client.
Can someone enlighten me as to how I can get around this, what is the cause, etc. ?
Thanks in advance !

-James
 
James Adams
Ranch Hand
Posts: 188
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Once I found the topic thread the steps we're pretty straight forward. Now I have a nifty little program which gives me advice.
Is this a bug peculiar to the RI and not the default spec behavior ? Will we always have to avoid the use of getX() in EJB X's bean and component classes ?

-James
 
Ranch Hand
Posts: 277
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey James,

Originally posted by James Adams:
Is this a bug peculiar to the RI and not the default spec behavior ? Will we always have to avoid the use of getX() in EJB X's bean and component classes ?


The bug is particular to the RI. The spec does not make such a naming restriction.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic