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, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ On 21 September 2015 at 03:31, David Lee wrote: > See the admin GUI, Groups -> <name> -> Module Locations page > > ( a link on my box is > http://c66-2:8001/module-location-admin.xqy?section=group&group=17894219543765835212&mode=group > ) > > This is a small addition that got in V7 or V8 sometime. > It allows you to add additional 'module paths' mapping namespace->Location at > a group level. > > The location is interpreted as if it were an 'at "xxx"' in your app, > That sounds potentially complicated as its dependant on your app and module > etc ... but the main purpose was intended for 'system libraries' -- ( say > funtx.xqy ) as like a global system classpath or a 'xml catalog' so your > code doesnt have to maintain that -- or care if its a 'built in' or 'addon' > libary.' > > > > ----------------------------------------------------------------------------- > David Lee > Lead Engineer > MarkLogic Corporation > [email protected] > Phone: +1 812-482-5224 > Cell: +1 812-630-7622 > www.marklogic.com > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Florent Georges > Sent: Sunday, September 20, 2015 6:48 PM > To: MarkLogic Developer Discussion <[email protected]> > Subject: Re: [MarkLogic Dev General] Group module location > > Thank you, Geert. > > Well, yeah, I understand module locations. And it is very clear how it gets > resolved in case of app server module locations. But I could not find any > definition how it gets resolved in case of *group* module locations. > Especially because there is no such thing as group module database. > > I can test and have one example right, but I would just like to be sure I > have the whole story about group module location resolution. > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > > > On 20 September 2015 at 21:06, Geert Josten wrote: >> I think it is pretty straight-forward. If you have an xqy or such that >> does an import without an `at`, it looks for a module location for the >> given namespace in app-server define module locations, or group-level >> module locations. With that path it attempts to resolve as if that path >> was written with an `at` behind the import line. >> >> E.g. current modules-database() first, then Modules/ inside the ML >> installation dir. And I¹d expect app-server module locations to take >> priority over group-level ones.. >> >> Cheers >> >> On 9/20/15, 8:30 PM, "[email protected] on behalf of >> Florent Georges" <[email protected] on behalf of >> [email protected]> wrote: >> >>>Hi, >>> >>>I can't find what "group module locations" are resolved against. Is >>>it defined somewhere? Must they be in a specific location on disk? >>>In a database? >>> >>>Regards, >>> >>>-- >>>Florent Georges >>>http://fgeorges.org/ >>>http://h2oconsulting.be/ >>>_______________________________________________ >>>General mailing list >>>[email protected] >>>Manage your subscription at: >>>http://developer.marklogic.com/mailman/listinfo/general >> >> _______________________________________________ >> General mailing list >> [email protected] >> Manage your subscription at: >> http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
