• 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
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller

Weblogic problem

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Has anybody tried javabean and jsp combination ?
I have placed the javabean in the server classes folder
the jndi naming code is in javabean.
The jsp instantiates the javabean , and javabean contacts EJB
Now when i call the jsp it gives error 500
about javax.naming.InitialContext
where as i am not using this
if i directly call eJB from jsp it works even when i import
this package
but with javabean it does not
why so
Any clues
 
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Shail,
There is a theory that i can give but there is no validation for the same. Here Goes : U see java beans are intra process components while as EJB's are Inter Process Components and in case u try to access JavaBean from a JSP page ( which is a WL Process component), the problem arises while as when u try to access the EJB there shud and is no problem.
HTH
Sahil
p.s:Names can be deceptive
 
Get off me! Here, read this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic