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
