Method and system to provide access to factories in a naming system

• US 20050278223A1
• Filed: 05/27/2004
• Published: 12/15/2005
• Est. Priority Date: 05/27/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Petev, Petio, Pancheva, Elitsa, Blohm, Henning
• Granted Patent: US 7,721,256 B2
• Time in Patent Office: Days
• US Class Current: 705/22
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06Q 20/203 Inventory monitoring

Abstract

A method and system to provide easy access to factories in a naming service. The system receives an indication that a factory is needed by a client. A plurality of resolvers are checked in turn to find the factory indicated. If a resolver that can provide the factory is found, the factory is returned to the client. In one embodiment, resolvers register with a resolver manager that performs the checking in response to a naming operation. Because the resolver manager can access all registered resolvers, access to the factories is independent of a class path of the user.

Claims

1. A method comprising:

receiving an indication that a factory is needed;

iterating through a plurality of resolvers to identify a source for the factory; and

returning the factory if the source is identified.

2. The method of claim 1 further comprising:

associating a factory builder with a naming manager.

3. The method of claim 2 wherein associating comprises:

registering the factory builder with a Java naming and directory interface (JNDI) manager.

4. The method of claim 1 further comprising:

delegating a call from a naming manager to a resolver manager.

5. The method of claim 4 wherein delegating comprises:

instantiating a dispatcher state factory from the naming manager;

invoking a method in the resolver manager from the dispatcher state factory.

6. The method of claim 5 further comprising:

indentifying the dispatcher factory from an environment property of an argument of the call; and

identifying a desired state factory from a nonstandard environment property of the argument.

7. The method of claim 4 wherein delegating comprises:

delegating the call from a naming manager to a registered object factory builder; and

delegating the call from the registered object factory builder to the resolver manager.

8. The method of claim 1 wherein iterating comprises:

invoking a method to find one of an object factory, an initial context factory, a state factory and a uniform resource locator (URL) factory in each of the plurality of resolvers until the factory is found or all resolvers have been checked.

9. The method of claim 1 further comprising:

returning a default initial context instance;

checking for a scheme responsive to a first naming operation over the default initial context; and

resolving the scheme if found; and

checking environment properties for an initial context factory name if no scheme is found.

10. The method of claim 1 wherein iterating comprises:

inquiring if a resolver can provide the factory; and

receiving a null response if the resolver cannot provide the factory.

11. A system comprising:

a naming interface to receive naming requests;

a naming manager to handle naming requests received by the naming interface;

at least one factory builder registered with the naming manager to receive naming requests from the naming manager and to delegate the naming requests; and

a resolver manager to iterate a plurality of resolvers to find a factory when delegated a naming request.

12. The system of claim 11 wherein the resolver manager comprises:

a hash table of resolvers against class instances.

13. The system of claim 11 wherein each resolver comprises:

at least one find method for at least one factory.

14. The system of claim 13 wherein the at least one factory is at least one of:

an initial context factory;

an object factory;

a uniform resource locator (URL) factory; and

a state factory.

15. The system of claim 11 further comprising:

the plurality of resolvers registered with the resolver manager.

16. The system of claim 11 wherein the naming interface is a Java naming and directory interface (JNDI) application programming interface (API) and the naming manager is one of a javax.naming.spi.NamingManager and a javax.naming.spi.DirectoryManager.

17. The system of claim 11 further comprising:

a dispatcher factory recognized by the naming manager.

18. A machine-accessible medium containing instructions that, when executed, cause a machine to:

receive an indication that a factory is needed;

iterate through a plurality of resolvers to identify a source for the factory; and

return the factory if the source is identified.

19. The machine accessible median of claim 18 wherein instructions further cause the machine to:

associate a factory builder with a naming manager.

20. The machine accessible median of claim 19 wherein instructions causing the machine to associate comprise instructions to cause the machine to:

register the factory builder a Java naming and directory interface (JNDI) manager.

21. The machine accessible median of claim 19 wherein instructions further cause the machine to:

redirect a call to a JNDI application programming interface (API) to the factory builder.

22. The machine accessible median of claim 18 wherein instructions further cause the machine to:

delegate a call from a naming manager to a resolver manager.

23. The machine accessible median of claim 18 wherein instructions causing the machine to iterate comprise instructions to cause the machine to:

invoke a method to find one of an object factory, an initial context factory, a state factory and a uniform resource locator (URL) factory in each of the plurality of resolvers until the factory is found or all resolvers have been checked.

24. The machine accessible median of claim 18 wherein instructions further cause the machine to:

return a default initial context instance;

check for a scheme responsive to a first naming operation over the default initial context; and

resolve the scheme if found; and

check environment properties for an initial context factory name if no scheme is found.

25. The machine accessible median of claim 18 wherein instructions causing the machine to iterate comprise instructions to cause the machine to:

inquire if a resolver can provide the factory; and

receive a null response if the resolver cannot provide the factory.

26. A system comprising:

means for receiving naming operations; and

means for finding a factory to service the naming operation independent of a class path of a source of the naming operation.

27. The system of claim 26 further comprising:

means for returning a factory responsive to the naming operation.

28. The system of claim 26 wherein the means for finding comprises:

means for listing resolver against class names.