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

• US 20030195870A1
• Filed: 04/15/2002
• Published: 10/16/2003
• Est. Priority Date: 04/15/2002
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Vignola, Christopher P., Newcombe, Russell L.
• Granted Patent: US 6,947,925 B2
• 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 for performing a lookup in a second namespace, said lookup being performed from a first namespace, wherein said first and second namespaces may be disparate namespaces comprising:

parsing a first lookup request for a URL tag, said lookup request targeting an object located in said second namespace, said lookup request including a symbolic name corresponding to a target location in said second namespace, said URL tag corresponding to a URL context;

searching said URL context for a provider URL corresponding to said symbolic name; and

creating a second lookup request, said second lookup comprising said provider URL and said object name.

2. A method as in claim 1 wherein said first namespace and said second namespace are enabled for communication with each other.

3. A method as in claim 2 wherein said first namespace and said second namespace are disparate namespaces.

4. A method as in claim 2 wherein said first namespace and said second namespace are not configured as a federated domain.

5. A method as in claim 2 wherein said first namespace and said second namespace are enabled with JNDI for communication with each other.

6. A method as in claim 5 wherein said first namespace and said second namespace are disparate namespaces.

7. A method as in claim 5 wherein said first namespace and said second namespace are not configured as a federated domain.

8. 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 javaURL context factory in response to a java URL tag, said javaURL tag being derived from said first lookup request;

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

said javaURL naming context driving a URL context factory in response to a URL tag indicative of said second namespace, said federation URL tag being derived from said first lookup request;

said URL context factory creating a URL naming context corresponding to said URL tag, said URL naming context receiving said first lookup request from said javaURL naming context;

said URL naming context driving said 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;

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; and

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.

9. A system for federating at least two namespaces, wherein said two namespaces may be disparate namespaces, comprising:

at least two namespaces, said two namespaces being configured for communication with each other;

a regular naming context, said regular naming context being created by a regular naming context factory in response to said regular naming context factory receiving a lookup request from a component in a first of said two namespaces for an object in a second of said two namespaces, said regular naming context parsing said lookup request for a first URL tag, said first URL tag being indicative of said second namespace; and

a URL naming context, said URL naming context being created by a URL naming context factory in response to said regular naming said lookup request and in response to a second URL tag being included in said lookup request, said URL naming context parsing said lookup request for a symbolic name indicative of a provider URL, said provider URL being indicative of a target location in said second namespace;

10. An article of manufacture comprising:

a computer useable medium having computer readable program code embodied therein for performing a lookup in a second namespace, said lookup being performed from a first namespace, wherein said first and second namespaces are disparate namespaces, comprising;

computer readable program code for parsing a first lookup request for a URL tag, said lookup request for an object located in said second namespace, said lookup request including a symbolic name corresponding to a target location in said second namespace, said URL tag corresponding to a URL context;

computer readable program code for searching said URL context for a provider URL corresponding to said symbolic name; and

computer readable program code for creating a second lookup request, said second lookup comprising said provider URL and said object name.