I've posted a similar topic in the Web Dynpro forum, but I'm posting a possible solution here since it's more applicable to normal Java coding....
I would like to build a generic framework to store user configuration information - things like preferences, last selections, that sort of thing. This information would be used to maintain state between user sessions. For example, storing the object id of the last item the user was working with, so tomorrow they could sign in and continue from where they left off...
I was thinking of constructing a set of database tables, and bulding an API around these tables. Pretty simple to implement a tree structure to manage user config.
Then I thought about JNDI, and how it's used to access the portal content directory - this is very similar to what I want to do: store artibrary, serializeable Java objects in a tree structure by user, and then have the ability to fetch these items from the tree using a standard api - JNDI. Searching isn't quite as important, since generally the application would know exactly what they were looking for.
Is this feasable, or is using JNDI for something like this completely overkill? I've never even remotely thought about using JNDI like this before, so I'm working from a blank slate. If someone has done something like this before (implement a JNDI Service Provider over a set of database tables), I'd love to hear from you.
Of course, comments telling me I'm nuts are appropriate as well. Perhaps not as welcome as real help tho
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.