This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 19904 - Writable JNDI lookup over system file system
Summary: Writable JNDI lookup over system file system
Alias: None
Product: platform
Classification: Unclassified
Component: Lookup (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Petr Hrebejk
Depends on:
Blocks: 17934
  Show dependency tree
Reported: 2002-01-29 15:09 UTC by Jaroslav Tulach
Modified: 2008-12-22 23:45 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2002-01-29 15:09:34 UTC
Implement SPI of InitialContext that will give access to objects provided by
DataObjects stored on system filesytem and allow others to modify the JNDI
contexts by binding there different objects.

When a binding (object) method is called an InstanceDataObject.create (...)
should be called to create the correct persistent file on a disk.
Comment 1 Vitezslav Stejskal 2002-02-28 11:07:17 UTC
Would it be possible to reuse this implementation on different filesystem than SFS? I would like to use 
JNDI for projects settings as well, but they will not live on the SFS.
Comment 2 Jaroslav Tulach 2002-02-28 11:48:29 UTC
That should be possible. The InitialContext can be constructed with a
Hashtable argument. In it we could provide a pair

("root", fileObject)

to mark the root of the JNDI namespace.
Comment 3 Vitezslav Stejskal 2002-03-03 17:15:23 UTC
I've put in CVS implementation of writable JNDI context, there are also some tests 
covering its functionality. Please, review it and decide what to do with this issue. 1.4 1.3 1.6 1.1 1.3
Comment 4 Peter Zavadsky 2002-10-01 16:40:07 UTC
Closing as fixed.
Comment 5 Jaroslav Tulach 2002-10-02 09:34:01 UTC
Same as ReadOnly JNDI, needs to be included in build process.
Comment 6 David Konecny 2003-03-19 16:32:04 UTC
Yarda, I do not see any reason for keeping this issue open. The issue
17934 should be used for tracking of part_of_the_regular_build or not.