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, by one or more processors, a resolution request associated with a first module, wherein the first module has corresponding metadata that includes an indication of a dependent namespace;
constructing, by the one or more processors, a resolution context associated with the first module based at least in part on one or more respective namespaces associated with components packaged with the first module;
determining, by the one or more processors, that both a second module and a third module export the dependent namespace;
selecting, by the one or more processors, from among the second module and the third module a selected module to provide the dependent namespace;
determining, by the one or more processors, that a component made available by the selected module is associated with the resolution request;
wherein the selected module has corresponding metadata that includes an indication of an exported namespace associated with the selected module, and wherein the exported namespace associated with the selected module is included in the resolution context associated with the first module; and
providing, by the one or more processors, access to a shared instance of the component made available by the selected module.
2. The method of claim 1 , wherein the selected module is selected based at least in part on a constraint defined in the first module.
3. The method of claim 2 , wherein the constraint is defined as part of the corresponding metadata of the first module.
4. The method of claim 1 , wherein the selected module is selected based at least in part on a rule for how relationships are captured across XML documents.
5. The method of claim 1 , wherein the first module defines a physical dependency to the dependent namespace.
6. The method of claim 1 , wherein the first module declares a logical dependency on the selected module.
7. The method of claim 1 , wherein the corresponding metadata of the first module is used to construct the resolution context associated with the first module.
8. A computer system, comprising:
a memory; and
one or more processors coupled 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 one or more respective namespaces associated with components packaged with the first module;
determine that both a second module and a third module export the dependent namespace;
select from among the second module and the third module a selected module to provide the dependent namespace;
determine that a component made available by the selected module is associated with the resolution request;
wherein the selected module has corresponding metadata that includes an indication of an exported namespace associated with the selected module, and wherein the exported namespace associated with the selected 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 selected module as stored in the memory.
9. The computer system of claim 8 , wherein the selected module is selected based at least in part on a constraint defined in the first module.
10. The computer system of claim 9 , wherein the constraint is defined as part of the corresponding metadata of the first module.
11. The computer system of claim 8 , wherein the selected module is selected based at least in part on a rule for how relationships are captured across XML documents.
12. The computer system of claim 8 , wherein the first module defines a physical dependency to the dependent namespace.
13. The computer system of claim 8 , wherein the first module declares a logical dependency on the selected module.
14. The computer system of claim 8 , wherein the corresponding metadata of the first module is used to construct the resolution context associated with the first module.
15. A computer program product embodied in a tangible, non-transitory computer readable storage medium and storing 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 one or more respective namespaces associated with components packaged with the first module;
determine that both a second module and a third module export the dependent namespace;
select from among the second module and the third module a selected module to provide the dependent namespace;
determine that a component made available by the selected module is associated with the resolution request;
wherein the selected module has corresponding metadata that includes an indication of an exported namespace associated with the selected module, and wherein the exported namespace associated with the selected 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 selected module.
16. The computer program product of claim 15 , wherein the selected module is selected based at least in part on a constraint defined in the first module.
17. The computer program product of claim 16 , wherein the constraint is defined as part of the corresponding metadata of the first module.
18. The computer program product of claim 15 , wherein the selected module is selected based at least in part on a rule for how relationships are captured across XML documents.
19. The computer program product of claim 15 , wherein the first module defines a physical dependency to the dependent namespace.
20. The computer program product of claim 15 , wherein the first module declares a logical dependency on the selected module.