Future Ideas

  • Allow converters to be configured/plugged in somehow.
  • Implement Type in such a way that the object to create may be specified, say JDOPersistenceFactory, and that sub-properties may be set as bean properties.
  • Implement binding so that values may be stored in the system, making it Read/Write.
  • Implementing the list methods so you can see the values in a particular directory/properties file.
  • Searches. Consider implementing DirContext.
  • Switch to using Names in the system, with the String argument being turned to a Name based on delimiters specified in the jndi.properties. Allow more than one delimiter.
  • Other DataSource like things? JDO?
  • Allow the root to be a url, so properties can be found online
  • Make it nice to hook up Enhanced drivers from DbUtils??
  • Confirm that jars and zips may be used in the classpath protocol.
  • Add a jdbc implementation underneath for the configuration.
  • Allow the underlying Properties class to use [when applicable] to be specified.
  • multiple domains. ie) Configure org.osjava to use .properties over http, and org.osjava to use xml over classpath.
  • Implement a Name class which finds the lookup key separator and injects that inside the name values [a string array]
  • When a value is unbound, don't return to the default but instead make it so it throws an exception when you try to obtain that value [unless bound again].
  • Allow a map-delimiter so that something like bob.foo.thing#bah=fred uses bah as the key, and fred as the value.
  • Is there a way to specify the type of a List or Map, or must ArrayList and HashMap always be used?
  • Write a simple-jndi server/client setup. Maybe use beep4j
  • Enable BlahDS.url so you can see the url of a datasource. Block passwords.
  • Implement DataSource creation as a part of the converter.
  • Test DataSources in various situations. Given a lookup of java:/TestDS and a delimiter of /, a directory of java: and a file of TestDS.properties, it appears to still look for TestDS/url and not url. Basically the PropertiesDataSource is buggy in its lookup.
  • Implement satisfactory unit testing.
  • A way to federate over to another JNDIContext.
  • A JNDIResourceBundle class which loads resources from JNDI.