Modularized XML namespaces
Techniques to provide and use modularized XML namespaces are disclosed. In various embodiments, a resolution request associated with a first module is received. A resolution context associated with the first module is used to determine that a component made available by a second module is associated with the resolution request. Access to a shared instance of the component made available by the second module is provided.
1. A method, comprising:
receiving a resolution request associated with a first module, wherein the first module has corresponding metadata that includes an indication of a dependent namespace;
constructing a resolution context associated with the first module based at least in part on respective namespaces associated with components packaged with the first module and one or more exported namespaces indicated to be made available to the first module by one or more other modules;
using the resolution context associated with the first module to determine that a component made available by a second module is associated with the resolution request, wherein the second module has corresponding metadata that includes an indication of an exported namespace associated with the second module, and wherein the exported namespace associated with the second module is included in the resolution context associated with the first module; and
providing access to a shared instance of the component made available by the second module.
2. The method of claim 1 , wherein the resolution request comprises a qualified name of the component.
3. The method of claim 2 , wherein the qualified name of the component is associated with a target namespace associated with the second module.
4. The method of claim 1 , wherein the component is made available by the second module at least in part by including in the metadata associated with the second module an identification of a namespace with which the component is associated as the exported namespace.
5. The method of claim 1 , wherein the metadata corresponding to the first module is used to construct the resolution context associated with the first module.
6. The method of claim 5 , wherein the metadata corresponding to the first module is included in a package comprising the first module.
7. The method of claim 5 , wherein the metadata corresponding to the first module identifies the second module as a dependent module on which the first module depends.
8. The method of claim 5 , wherein the metadata corresponding to the first module identifies one or more versions of the second module.
9. The method of claim 1 , further comprising extracting a document from a package with which the second module is associated and using the document to store the shared instance of the component made available by the second module.
10. The method of claim 9 , further comprising associating the shared instance of the component made available by the second module with the second module.
11. The method of claim 9 , wherein the document is extracted and the shared instance of the component made available by the second module is stored based at least in part on an indication in metadata associated with the second module that the document is to be made available for use by other modules.
12. The method of claim 11 , wherein the indication comprises a namespace with which the document is associated.
13. The method of claim 1 , wherein a third module depends on the second module and a resolution context associated with the third module includes a namespace associated with the shared instance of the component made available by the second module.
14. The method of claim 1 , further comprising receiving a new version of the second module and determining based on metadata associated with the first module whether the new version of the second module satisfies a dependency on the second module as specified by the first module.
15. The method of claim 14 , further comprising replacing a prior version of the second module with the new version of the second module, without requiring any changes to the first module or documents comprising the first module, based at least in part on a determination that the new version of the second module satisfies a dependency on the second module as specified by the first module.
16. The method of claim 15 , wherein the new version of the second module is used to replace the prior version of the second module in the event that all modules that depend on the prior version of the second module are compatible with the new version of the second module.
17. The method of claim 1 , wherein the component is made available by the second module and separately is made available also by a third module, and further comprising applying a selection criteria to select the second module to provide the component.
18. The method of claim 17 , wherein the component is associated with a namespace identified by metadata associated with the first module as being required by the first module.
19. The method of claim 1 , wherein the component is identified as a resource required by the first component at least in part in a manner defined generically in OSGi specification.
20. The method of claim 1 , further comprising sharing, at run time, the same component made available by the second module, between the first module and a fourth module that has corresponding metadata that includes an indication of a dependent namespace associated with the component made available by the second module.
21. A computer system, comprising:
a memory; and
a processor couple to the memory and configured to:
receive a resolution request associated with a first module, wherein the first module has corresponding metadata that includes an indication of a dependent namespace;
construct a resolution context associated with the first module based at least in part on respective namespaces associated with components packaged with the first module and one or more exported namespaces indicated to be made available to the first module by one or more other modules;
use the resolution context associated with the first module to determine that a component made available by a second module is associated with the resolution request, wherein the second module has corresponding metadata that includes an indication of an exported namespace associated with the second module, and wherein the exported namespace associated with the second module is included in the resolution context associated with the first module; and
provide access to a shared instance of the component made available by the second module as stored in the memory.
22. The system of claim 21 , wherein the resolution request comprises a qualified name of the component.
23. The system of claim 22 , wherein the qualified name of the component is associated with a target namespace associated with the second module.
24. The system of claim 21 , wherein the component is made available by the second module at least in part by including in the metadata associated with the second module an identification of a namespace with which the component is associated as the exported namespace.
25. The system of claim 21 , wherein the processor is further configured to use the metadata corresponding to the first module to construct the resolution context associated with the first module.
26. A computer program product embodied in a tangible, non-transitory computer readable storage medium and comprising computer instructions configured to:
receive a resolution request associated with a first module, wherein the first module has corresponding metadata that includes an indication of a dependent namespace;
construct a resolution context associated with the first module based at least in part on respective namespaces associated with components packaged with the first module and one or more exported namespaces indicated to be made available to the first module by one or more other modules;
use the resolution context associated with the first module to determine that a component made available by a second module is associated with the resolution request, wherein the second module has corresponding metadata that includes an indication of an exported namespace associated with the second module, and wherein the exported namespace associated with the second module is included in the resolution context associated with the first module; and
provide access to a shared instance of the component made available by the second module.