Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Deploy modules while using filesystem will give an error #204

Closed
peetkes opened this issue Apr 16, 2014 · 4 comments
Closed

Deploy modules while using filesystem will give an error #204

peetkes opened this issue Apr 16, 2014 · 4 comments
Milestone

Comments

@peetkes
Copy link
Contributor

peetkes commented Apr 16, 2014

When you prefer using the filesystem for developing on your local system, you will get an error as soon as you try to create rest extensions and deploy them to the database.
In local.properties I have:
app-modules-db=filesystem
modules-root=location of roxy/src/ folder
All works like it should,until you create a rest extension and deploy it with ml local deploy modules

The error message I got is:

Loading REST extensions from /Users/pkester/Development/git/kb-test/rest-api/ext

ERROR: 500 "Internal Server Error"
ERROR: <rapi:error xmlns:rapi="http://marklogic.com/rest-api">rapi:status-code500/rapi:status-coderapi:statusINTERNAL ERROR/rapi:statusrapi:message-codeXDMP-UPDATEFUNCTIONFROMQUERY/rapi:message-coderapi:messageXDMP-UPDATEFUNCTIONFROMQUERY: xdmp:apply(function() as item()*) -- Cannot apply an update function from a query. See the MarkLogic server error log for further detail./rapi:message/rapi:error

@paxtonhare
Copy link
Contributor

If you are using rest extension you have to use a modules database. Even if we were to deploy the rest extensions to the modules db it would not work because the appserver is pointing to the filesystem.

@dmcassel
Copy link
Collaborator

Worth detecting when this is being tried and reporting an error? If app-type=rest or hybrid, and app-modules-db=filesystem, @logger.error("Ain't gonna happen").

@paxtonhare
Copy link
Contributor

Yeah. Good idea.

On Apr 17, 2014, at 6:06 PM, David Cassel notifications@github.com wrote:

Worth detecting when this is being tried and reporting an error? If app-type=rest or hybrid, and app-modules-db=filesystem, @logger.error("Ain't gonna happen").


Reply to this email directly or view it on GitHub.

@paxtonhare
Copy link
Contributor

fixed in dev

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants