Dear Alex, Thank you for taking the time to look at this. I am using 7.0-2.2 server version on a desktop windows 8.1. and the attached version of xqmvc 0.1.3 build. Sample test files are included in the build. I have indeed tried a remote HTTP debugging session in accordance with your instructions and set breakpoints in the xqmvc.xqy file, the application controller files and application modules files. These module were opened from data source. Note that the files containing a breakpoint are not invoked by the main module but by intermediary modules (a hierarchical structure). Debugging seems only to work on files directly invoked by the main module, at least it does so on the xqmvc.xqy file, which is invoked by the main module (index.xqy). Frank From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Alex Jitianu Sent: 05 January 2015 15:46 To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Oxygen 16.1 - Marklogic debugging scenarios Hello Frank, Could you please tell me what MarkLogic Server version are you using? Also what xqmvc build? I want to test it myself and see what happens. It would help if you have any XQuery sample files that I could test with this framework. You are trying to do a remote HTTP debugging session, right? Attach from Oxygen and debug an HTTP request that was already started probably using the browser? I see that you've already studied in depth our resources about how to debug in MarkLogic but just in case it might help, the steps required for remote HTTP debugging are: - create a connection in Oxygen using an XDBC App server that has the same module configuration as the HTTP one - put the HTTP server in debug mode using the Data Source Explorer, right click on the HTTP App server and "Enable debug mode" - return to the browser and initiate the request - return to Oxygen and from the "Requests" container of the HTTP App server right click on the request and choose "Debug" After these steps the debugger will be up and running and no breakpoints are yet added. Do you get this far? The warning you are receiving complains about some breakpoints. Have you set any breakpoints? If you have, are they in the main module or in a library module? And if they are in a library module how was this library module opened? From the Data Source Explorer? I've tested the previous procedure on the Shakespeare Demo [1] application. Thank you for taking the time to help us shed some light on this situation. PS: A transformation scenario is used to transform/execute an XQuery file. A validation scenario is used to configure what engine should be used to validate an XQuery file (for example while you work on it - automatic validation). A validation scenario also help when working on library modules because you can specify the main module from which the validation can start. [1] http://developer.marklogic.com/code/bill Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 1/4/2015 9:15 AM, Frank Mortier wrote: Dear all: I acquired Friday Oxygen 16.1 in order to debug a Marklogic application. I have encountered the same problem as Jacob in http://www.oxygenxml.com/pipermail/oxygen-user/2013-June/004698.html. The ML application uses the xqmvc framework whereby the main file is index.xqy, but the routing is provided by another module xqmvc.xqy, importing controller files which import modules. See e.g.: http://www.marklogic.com/blog/founders-online-lesson-performance/ and https://code.google.com/p/xqmvc/ I have been unsuccessfully testing various debugging scenarios yesterday, amongst others including all xqy files. I was also not able to debug a module in the basic framework. Related: what is the difference between using a validation scenario or a transformation scenario. I notice a difference between the documentation and the demo at http://www.oxygenxml.com/demo/XQueryDebuggerforMarkLogic.html Any suggestions? Frank _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com<mailto:oXygen-user@oxygenxml.com> http://www.oxygenxml.com/mailman/listinfo/oxygen-user