Hi Douglass and everybody who contributed, thanks to Franklin Salonga of ML I managed to resolve my issue yesterday.
My mistake was a simple configuration error: i.e. to not point the modules directory to my database, but leave it at "file system". Also, the document database was set to Documents instead of my database: "stats". Making these two changes to all servers (http, xdbc, webdav) made it possible to debug Mark Logic from within OxygenXML -- even though OxygenXML hangs now and again and needs to be restarted ... it shows here and there that Xquery is still in its "toothing stage". thanks again for everybody's input, very much appreciated! Jakob. On Mon, Jun 29, 2009 at 14:37, Glidden, Douglass A<[email protected]> wrote: > Jakob, > > What is the URL you use to access CQ? If CQ and your modules are on the same > HTTP server (I'm assuming they are, since a relative path would not work if > they are not), make sure that your "relative" path is actually relative to > the location of CQ. For instance, on my server, CQ is located at > http://marklogic:8002/cq/. So to access a module at > http://marklogic:8002/stats/functions.xqy, I would have two choices for the > module import: > > import module namespace utils = "http://myorg.org/utils"; at > "../stats/functions.xqy"; > import module namespace utils = "http://myorg.org/utils"; at > "/stats/functions.xqy"; > > The first of these is the relative path and the second is the absolute > path--bearing in mind that "absolute" is from the perspective of the HTTP > server, not the filesystem, so if the HTTP server is based at > /opt/MarkLogic/test, then absolute paths will start at this point and > relative paths will never be able to go above this point. Based on my > experience, either of these should work in CQ. I've never tried importing a > library from a complete URL before, so I don't know if that works or not. > > Also, this is probably obvious, but make sure that the user your MarkLogic > server process is running as has at least read permission on the files you > are trying to import. > > Hope this helps, > > Doug Glidden > (703) 317-7523 > http://dougglidden.blog.boeing.com > > -----Original Message----- > From: Jakob Fix [mailto:[email protected]] > Sent: Friday, June 26, 2009 15:12 > To: General Mark Logic Developer Discussion > Subject: Re: [MarkLogic Dev General] RE: how to debug > > 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 > _______________________________________________ > General mailing list > [email protected] > http://xqzone.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
