System and method for performing lookups across namespace domains using universal resource locators

• US 20050210033A1
• Filed: 05/18/2005
• Published: 09/22/2005
• Est. Priority Date: 04/15/2002
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Vignola, Christopher P., Newcombe, Russell L.
• Application Number:
  US11/131,842
• Publication Number:
  US 20050210033A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A system and method for performing a lookup in a second namespace, the lookup being performed from a first namespace, whereby a component performing the lookup is not required to be configured for performing a lookup in the second namespace, the system and method further comprising: parsing a first lookup request for a URL tag, the first lookup request for an object located in the second namespace, the lookup request including a symbolic name corresponding to a target location in the second namespace, the URL tag corresponding to a URL context; searching the URL context for a provider URL corresponding to the symbolic name; and creating a second lookup request, the second lookup comprising the provider URL and the object'"'"'s name.

Claims

1. A method of federating at least two namespaces, said two namespaces being enabled for JNDI communication, wherein said first and second namespaces may be disparate namespaces, comprising:

a JNDI context factory creating a regular naming context in response to receiving a first lookup request from a component in a first of said two namespaces, said first lookup request for an object located in a second of said two namespaces;

said regular naming context driving a java URL context factory in response to a java URL tag, said java URL tag being derived from said first lookup request;

said java URL context factory creating a java URL naming context, said java URL naming context receiving said first lookup request from said regular naming context;

a URL naming context driving a JNDI naming context in response to a provider URL, said provider URL being derived from said first lookup request, said provider URL indicative of a target location in said second namespace.

2. The method of claim 1 wherein:

said java URL naming context drives a URL context factory in response to a URL tag indicative of said second namespace.

3. The method of claim 2 wherein:

said URL context factory creates a URL naming context corresponding to said URL tag, said URL naming context receiving said first lookup request from said java URL naming context.

4. The method of claim 1 wherein:

said JNDI context factory creating an initial context including said provider URL, said initial context having a provider URL value set to said provider URL.

5. The method of claim 4 wherein:

said second namespace receiving a second lookup request from said initial context, said second lookup request including said object and said target location of said object.