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

Roxy Deployer doesn't work with ML7 due to change in eval.xqy #110

Closed
peterskim12 opened this issue Jun 20, 2013 · 5 comments
Closed

Roxy Deployer doesn't work with ML7 due to change in eval.xqy #110

peterskim12 opened this issue Jun 20, 2013 · 5 comments
Assignees
Labels

Comments

@peterskim12
Copy link
Contributor

It looks like engineering renamed the /Apps/qconsole/endpoints/eval.xqy to evaler.xqy and also changed the endpoint definition. Roxy uses this service to execute adhoc XQuery prior to the existence of a defined application.

I took a look at what's needed to fix this. I think there's a bug in the endpoint definition in that it expects named parameters such as resulttype, action, querytype but at the same time, it also expects the ad-hoc query to be submitted via the request body. I've sent an email to engineering for more info.

@ghost ghost assigned peterskim12 Jun 20, 2013
@peterskim12
Copy link
Contributor Author

For now, maybe we just do what it takes to get this to work but I wonder if a better long-term solution for this is to rely on the Configuration Manager and Packaging functionality in MarkLogic to apply configuration. I know this is closely tied to the MarkLogic server versions... Have we ever considered creating different Roxy branches that are associated with major MarkLogic versions?

@paxtonhare
Copy link
Contributor

The packaging API has been woefully inadequate at allowing bootstrapping. I'm happy to discuss why over IM. 

​--Paxton 


Sent from Mailbox for iPhone

On Fri, Jun 21, 2013 at 10:54 AM, Peter Kim notifications@github.com
wrote:

For now, maybe we just do what it takes to get this to work but I wonder if a better long-term solution for this is to rely on the Configuration Manager and Packaging functionality in MarkLogic to apply configuration. I know this is closely tied to the MarkLogic server versions... Have we ever considered creating different Roxy branches that are associated with major MarkLogic versions?

Reply to this email directly or view it on GitHub:
#110 (comment)

@dmcassel
Copy link
Collaborator

The packaging API falls short of what bootstrapping does, which means we would still need to use the same strategy for a lot of what Roxy does. Given that, it hasn't made sense to work in the packaging API yet. If that API got to the point where we could completely replace deploy/lib/xquery/setup.xqy, I think it would be time to branch and use that approach.

@peterskim12
Copy link
Contributor Author

Ok, sounds good.

I think this would be a good opportunity to get more involved with engineering to talk about what the gaps are and see if some of what's implemented in Roxy should also be addressed in the packaging API (if you guys haven't tried doing that already)...

dmcassel added a commit that referenced this issue Jul 24, 2013
…ccomodate the change in the endpoint. Back-tested for ML5 and ML6.
@dmcassel
Copy link
Collaborator

Requires ML 7.0-20130725 or later.

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

No branches or pull requests

3 participants