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

Initial Context question

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We currently use WSAD 5.1 to do our development here but are moving off to Eclipse and JBoss. Our production environments will still be Websphere and we'd like to have one codebase that works in both.

One place that won't work with JBoss is creating the InitialContext with parameters (com.ibm.websphere.naming.WsnInitialContextFactory) as we currently do. In JBoss, we created an InitialContext with no parameters and it worked fine in WSAD as well on our local environments.

The question I have is why should I specify "com.ibm.websphere.naming.WsnInitialContextFactory" as the INITIAL_CONTEXT_FACTORY when creating the InitialContext? Do I lose anything by not doing this?

Thanks,

Jon
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jon,
Welcome to JavaRanch. This sounds like a WebSphere question, so I'm moving to our IBM/WebSphere forum for you.

Jeanne
Forum Bartender
 
reply
    Bookmark Topic Watch Topic
  • New Topic