That's right.  I only haven't managed so far to correctly include the
library modules (neither the complete path
http://10.0.1.88:8000/stats/functions.xqy nor a relative path like
./functions.xqy seem to work.

Maybe the Oxygen support can help.

thanks,
Jakob.

On Fri, Jun 26, 2009 at 20:49, Kelly Stirman<[email protected]> wrote:
> I believe oXygen allows you to step through the code because it has an 
> integration with the MarkLogic debugger API:
>
> http://www.oxygenxml.com/MarkLogic_support.html
>
> Kelly
>
>
> Message: 1
> Date: Fri, 26 Jun 2009 11:05:57 +0200
> From: Geert Josten <[email protected]>
> Subject: RE: [MarkLogic Dev General] how to debug?
> To: General Mark Logic Developer Discussion
>        <[email protected]>
> Message-ID:
>        <0260356c6dfe754ba6fa48e659a14338269a8fd...@helios.olympus.borgus.nl>
> Content-Type: text/plain; charset="Windows-1252"
>
>> As stuff gets more complex (modules, etc.), cq seems to hit
>> its limits (or is it me?). I therefore hoped that OxygenXML
>> would let me debug easily, but there as well the debugger
>> cannot find a module that is referenced like this in the main module:
>>
>> import module namespace utils = "http://myorg.org/utils"; at
>> "./functions.xqy";
>
> You have to keep in mind that the xqueries are executed on the server, even 
> when using Oxygen. It depends on the server settings where it is looking for 
> your modules. If it is configured to look in the Modules database, you will 
> have to upload all your modules to be able to run it.
>
> CQ itself is usually running from file-system. This means that if you are 
> referring to modules, it is looking for them among the CQ files. Not that 
> very nice to have your files mixed like that, so I usually create a separate 
> HTTP server rooted on file-system, using a plain text editor to change the 
> files and use the HTTP interface to execute the queries. You can create a 
> separate test xquery and call that through HTTP to test specific things.
>
> By the way, I usually go a step further. After checking syntax by calling the 
> modules from file-system, I upload them into the Modules database. Using the 
> trace functionality, you can add debug logging, which can be usefull for 
> debugging production environments.
>
>> How and using which tools do you develop Xquery apps for Mark Logic?
>
> I personally just use a text editor with syntax highlighting. Lots of 
> colleagues of mine are fond of Oxygen. I am not aware of an editor that 
> allows stepping through xquery code..
>
> HTH.
>
> Kind regards,
> Geert
>
>
> Drs. G.P.H. Josten
> Consultant
>
>
> http://www.daidalos.nl/
> Daidalos BV
> Source of Innovation
> Hoekeindsehof 1-4
> 2665 JZ Bleiswijk
> Tel.: +31 (0) 10 850 1200
> Fax: +31 (0) 10 850 1199
> http://www.daidalos.nl/
> KvK 27164984
> _______________________________________________
> General mailing list
> [email protected]
> http://xqzone.com/mailman/listinfo/general
>
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to