marklogic-community / demo-cat

An application to help SEs find good demos and record bugs and RFEs on them. AngularJS talks to the MarkLogic database via the REST API.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ml local deploy modules returns 404 error -- need to update url-rewriter property

opened this issue · comments

While attempting to install demo-cat locally with MarkLogic 8, I ran into a problem with the ml local deploy modules command, which was returning a 404 Not Found error.

I found the related Roxy issue #370.

I updated the following setting in my build.properties file.

# deploy/build.properties file
# The Roxy rewriter....
url-rewriter=/MarkLogic/rest-api/rewriter.xml

I then ran ml local bootstrap and ml local restart, and was then able to successfully complete the ml local deploy modules, and start up the application.

I think the above is isolated to ML8, so may just need an update to the readme instructions.

UPDATE: Strangely, when I tried to re-run ml local deploy modules, I began to receive a 500: RESTAPI-UNSUPPORTEDPROP error. I found related Roxy issue #336, and so removed the <error-format> line from rest-api/config/properties.xml file, and was able to then re-run deploy modules without issue.

I'm not sure why the first pass was successful, and subsequent runs picked up the <error-format> element.

commented

I think you ran against master branch. The latter issue with error-format was fixed in develop branch. The first wasn't fixed because we wanted to be able to deploy against both ML 8 and ML 7. You have to put that rewriter line in the env properties, for instance deploy/local.properties.

We'll consider making ML 8 the default once we have released the current develop branch into master..

Thanks Geert.

Yes, I see now that the <error-format> was removed from develop branch back in March. Sorry for the confusion.

Just wanted to log this, to help anyone else that might be struggling with ML 8.

I've added pull request #209 to update the comments in build.properties.

commented

Thanks for the PR!

Can we make this the default now? (I just ran into this issue and ate up some time figuring out what was going on.)

commented

Isn't it solved in develop branch yet? Latest Roxy will also auto-compensate. Maybe we should upgrade..