Thank you for explaining. There is way to achieve what you want but not in the way you are currently doing it.
The module.xml is a static resource which is loaded by the module infrastructure and doesn''t support loading resources directly because it is actually loaded before the address space comes into life based directly on it''s contents (chicken and egg) There it would not be possible to import like functionality in it.
However using the mapper overlay is probably the way to go. This allows for a dynamic mapping definition (loaded from a resource) to define the interfaces of many endpoints. By generating the mapper definition dynamically using XRL or XSLT it would be easy load all the common grammar or regex parts from the same location to avoid replication and to ensure consistency.
Cheers, Tony
The module.xml is a static resource which is loaded by the module infrastructure and doesn''t support loading resources directly because it is actually loaded before the address space comes into life based directly on it''s contents (chicken and egg) There it would not be possible to import like functionality in it.
However using the mapper overlay is probably the way to go. This allows for a dynamic mapping definition (loaded from a resource) to define the interfaces of many endpoints. By generating the mapper definition dynamically using XRL or XSLT it would be easy load all the common grammar or regex parts from the same location to avoid replication and to ensure consistency.
Cheers, Tony