The important part is this: > The location is interpreted as if it were an 'at "xxx"' in your app,
Imagine you look up the module namespace in the group settings, and find a module location string. Now paste that string into the query with "at" before it, and re-execute the query. That's how the feature behaves. In other words, it uses the modules DB set up for the query that is executing the import. John On 21/09/15 15:43, Florent Georges wrote: > Hi David, > > Thank you for your response. I think I understand very well the > concept :-) But I still fail to see how the location part is resolved > to an actual module (in case of a group.) > > In the case of an app server, it is well defined: if the modules for > the app server are on the file system, then the location is resolved > against the root directory for the modules, if the modules are in a > database, the location is resolved against the module root in the same > database. > > But in case of a group, we do not have modules, do we? There is no > module database, nor module directory on the file system. > > I guess another way of asking the question is: "Given the library > module with namespace XYZ, that I want to make available to all > modules in all app servers in the group G, without requiring any 'at' > location hint, where should I put it, and what would be the > corresponding value to put in the 'location' field for the 'module > location' feature?" > > Regards, > -- John Snelson, Lead Engineer http://twitter.com/jpcs MarkLogic Corporation http://www.marklogic.com _______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
