You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
You sometimes want to capture an existing Roxy app from a production server, for example to check whether what you locally have is identical. This requires capturing the modules of any type.
The text was updated successfully, but these errors were encountered:
I have added the ability to capture modules for any application type to ML7 and taken the protection off which will allow to capture modules for any application type in ML5,6, and 7. For ML7 if it’s a REST application, REST will still be used to capture since it’s faster and more comprehensive than the query based method. Pull request to follow.
alencruz
added a commit
to alencruz/roxy
that referenced
this issue
Jan 27, 2015
Currently Capture was only supporting capturing modules for
REST applications. I have added the ability to capture modules
for any application type to ML7 and taken the protection off
which will allow to capture modules for any application type in
ML5,6, and 7. For ML7 if it’s a REST application, REST will still be
used to perform the capture since it’s faster than the query
based method. The query based method used for ML5,6, and
ML7 (non-REST) only grabs text based files (xqy, html,…) it does
not correctly capture other types of files in the modules database
such as images since it’s doing an fn:doc on the URI to get the
content.
…Issue marklogic-community#298
Improved the fix for Issue marklogic-community#223 based on feedback received.
Also fixes Issue marklogic-community#298 since it protects against the error condition.
In addition some of the Capture help content was clarified to reflect the implementation.
You sometimes want to capture an existing Roxy app from a production server, for example to check whether what you locally have is identical. This requires capturing the modules of any type.
The text was updated successfully, but these errors were encountered: