<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
Unfortunately if a query is submitted through xdmp:eval you can't
give a base URI for resolving any relative imports that that query
might have. Or can you? So I kind of require a mix between
xdmp:invoke and xdmp:eval. The "module URI"->"updated module
content" mapping to be passed to the xdmp:invoke was my idea of such
a mix. The server first looks for a module in the Modules database?
And are you suggesting that I create a temporary structure in the
Modules database in which the server will find my updated version of
the modules before finding them in their real location?<br>
<br>
Thanks,<br>
Alex<br>
<br>
On 3/1/2012 5:12 PM, <a class="moz-txt-link-abbreviated" href="mailto:general-request@developer.marklogic.com">general-request@developer.marklogic.com</a> wrote:
<blockquote
cite="mid:mailman.4683.1330614720.2018.general@developer.marklogic.com"
type="cite">
<pre wrap="">xdmp:eval has the static-check option too. You could send the module to it as a string.
Beyond that, the Modules database makes a dandy persistent uri->content repository. You could have a hierarchy of temp files, perhaps something like <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>sync.ro<span class="moz-txt-tag">/</span></i>.sessions/{$SESSION}/{$RELATIVE-PATH}. Use a scheduled task to clean out anything older than N hours or days.
-- Mike
</pre>
</blockquote>
<br>
</body>
</html>