• 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

JNDI & JSR 168

 
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My first question is..if we are exposeing java objects through jndi how can we access it from any other workstation(login mechanism etc)..and second how stable JSR168 is, how much industry support is available...should i go for JSR168 for portal design or should i think of some alternatives
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
(1) The objects stored in JNDI should generally either be remote or serializable. However, I don't actually recommend storing things in JNDI...

(2) JSR 168 is gaining acceptance quickly, and has wide industry support, but it is limited in what you can do with it. For instance, only about half the features of WebSphere Portal Server are accessible through the JSR 168-compliant API provided with WPS.

Kyle
 
reply
    Bookmark Topic Watch Topic
  • New Topic