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

Deployer isn't working with ML7 EA1 #93

Closed
dmcassel opened this issue May 2, 2013 · 1 comment
Closed

Deployer isn't working with ML7 EA1 #93

dmcassel opened this issue May 2, 2013 · 1 comment
Assignees
@dmcassel
Labels
bug

Comments

@dmcassel
Copy link
Collaborator

dmcassel commented May 2, 2013

I have reports that it works for Windows, but on Linux I get an error.
@ghost ghost assigned dmcassel May 2, 2013
dmcassel added a commit that referenced this issue May 15, 2013
@dmcassel
#93 Fixed. In previous versions, we were able to send commands to /qc…
125aaca 
…onsole/endpoints/eval.xqy on port 8002, even though qconsole actually lives on port 8000. In ML7, we get a redirect. The deployer now honors that redirect.
@dmcassel
Copy link
Collaborator Author

Alternatives to the fix were to introduce another property (manage-port) or to rewrite deploying to work with what's available through the Manage app on port 8002. The second approach doesn't work because role and user management isn't available through that API, which means I'd still need to hit eval. I didn't like the first approach because would complicate the properties. As is, the solution is transparent to the user.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dmcassel dmcassel

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dmcassel