Locating modules for MarkLogic on app server
I have an XQuery file running on MarkLogic which includes a module. import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ; When I run this using ML's App Server it locates this module in the same directory as the master file. But when I try to run the xquery from within Oxygen it cant find the module. Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ? ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee@epocrates.com <mailto:dlee@epocrates.com> 812-482-5224
Lee, David wrote: Hi,
import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ;
Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ?
That's the problem of using "at hints" instead of using only the namespace URIs and relying on a resolving mechanism. Hope EXPath packaging would help improving this situation ;-) If you can access the module as a resource on the ML HTTP server, you should be able to use an XML Catalog mapping "common.xquery" to that location (for instance http://the-ml-server/dir/common.xql). (not tested though) Regards, -- Florent Georges http://www.fgeorges.org/
Hello, The MarkLogic server should resolve the path "common.xquery" relative to the root location of the server that listens on the port that was set for the MarkLogic connection in Preferences -> Data Sources. In the configuration of the server on the server machine look for the module directory root and the database that contains application modules. Regards, Sorin Lee, David wrote:
I have an XQuery file running on MarkLogic which includes a module.
import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ;
When I run this using ML’s App Server it locates this module in the same directory as the master file.
But when I try to run the xquery from within Oxygen it cant find the module.
Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ?
Which server is it using ? Would this be the root of the XDBC Server ? My problem is that this file is stored in the App server root ... but maybe if I copied it to the XDBC server it might work ? -----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache Sent: Thursday, November 19, 2009 10:19 AM To: oXygen-user@oxygenxml.com Subject: Re: [oXygen-user] Locating modules for MarkLogic on app server Hello, The MarkLogic server should resolve the path "common.xquery" relative to the root location of the server that listens on the port that was set for the MarkLogic connection in Preferences -> Data Sources. In the configuration of the server on the server machine look for the module directory root and the database that contains application modules. Regards, Sorin Lee, David wrote:
I have an XQuery file running on MarkLogic which includes a module.
import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ;
When I run this using ML's App Server it locates this module in the
same
directory as the master file.
But when I try to run the xquery from within Oxygen it cant find the module.
Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ?
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Oxygen communicates with an XDBC server. The server port that is set for the Oxygen connection must be displayed in the list of servers in the Web administration interface of MarkLogic. In the MarkLogic Web interface the module directory root location should be displayed in the details of that server. Make sure the module exists in that location on the server. Regards, Sorin Lee, David wrote:
Which server is it using ? Would this be the root of the XDBC Server ? My problem is that this file is stored in the App server root ... but maybe if I copied it to the XDBC server it might work ?
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache Sent: Thursday, November 19, 2009 10:19 AM To: oXygen-user@oxygenxml.com Subject: Re: [oXygen-user] Locating modules for MarkLogic on app server
Hello,
The MarkLogic server should resolve the path "common.xquery" relative to
the root location of the server that listens on the port that was set for the MarkLogic connection in Preferences -> Data Sources. In the configuration of the server on the server machine look for the module directory root and the database that contains application modules.
Regards, Sorin
Lee, David wrote:
I have an XQuery file running on MarkLogic which includes a module.
import module namespace common = "http://schemas.epocrates.com/schemas/marklogic/common" at "common.xquery" ;
When I run this using ML's App Server it locates this module in the
same
directory as the master file.
But when I try to run the xquery from within Oxygen it cant find the module.
Is there a way to tell Oxygen to somehow tell marklogic where this common module resides so it would behave the same as if it were executed from the App server ?
I am not sure if this should go directly to Sebastian, but just in case ... I start out with validated TEI-P5 and run the first translation, the XSL-translation into a FO-file without problems. Here however problems appear with the next step, generating PDF with a FO-processor: "SEVERE: Exception net.sf.saxon.trans.XPathException: org.apache.fop.fo.ValidationException: file:/home/lokalespen/BF/Forlag/BBv20esoarb.fo_fo:183:-1: Error(183/-1): For fo:block, fo:marker must be declared before initial-property-set? (#PCDATA|%inline;|%block;). at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)" This is concerning this part of the FO-file: "<fo:block keep-with-next.within-page="always" id="d23e62" text-align="left" font-family="Times" font-size="18pt" font-weight="bold" space-after="6pt" space-before.optimum="12pt" text-indent="0em"> <inline xmlns="http://www.w3.org/1999/XSL/Format" font-style="italic" >Forord</inline> <fo:marker marker-class-name="section1"/> <--- Line 183 <fo:marker marker-class-name="section2"/> <fo:marker marker-class-name="section3"/> <fo:marker marker-class-name="section4"/> <fo:marker marker-class-name="section5"/> <fo:marker marker-class-name="section0">Forord</fo:marker> </fo:block>" This happens when I have set the parameter 'divRunninheads" to 'true', and there are no problems if 'divRunningheads' is set to 'false'. All the best, Espen Ore
participants (4)
-
Espen S. Ore -
Florent Georges -
Lee, David -
Sorin Ristache