[uportal-dev] Is JNDIManager used?

[Eric Dalquist]

While going through and fixing bugs I ran across the following class. It appears to attempt to maintain a JNDI tree of all current services, users by id and sessions including an outline of each user's layout. This tree is never updated once the user is logged in (layout changes are not reflected in the tree). Nothing in the uPortal code base uses this code other than to create and destroy data on the tree when users log in and out.

-Eric



/**
* JNDIManager.
*
* uPortal's JNDI tree has the following basic structure:
* <tt>
* root context
*    |
*    +--services--*[service name]*...
*    |
*    +--users--*[userID]*
*    |             |
*    |             +--layouts--*[layoutId]*
*    +             |               |
* sessions         |               +--channel-ids
*    |             |               |      |
* *[sessionId]*    |               |      +--*[fname]*--[chanId]
*                  |               |
*                  |               +--sessions--*[sessionId]*
*                  |
*                  |
*                  +--sessions--*[sessionId]*
*                                    |
*                                    +--channel-obj--*[chanId]*...
*                                    |
*                                    +--[layoutId]
* </tt>
* Notation:
*  [something] referes to a value of something
*  *[something]* refers to a set of values
*  ... refers to a subcontext
*
*
* @author Bernie Durfee, [EMAIL PROTECTED]
* @author Peter Kharchenko, [EMAIL PROTECTED]
* @version $Revision: 42472 $
*/
public class JNDIManager

Can this class be outright removed from uPortal 3? If not I would plan on deprecating it as there are other ways to access this information directly versus going through a JNDI tree.

smime.p7s
Description: S/MIME Cryptographic Signature