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
Unfortunately, I think Jorge is the only one who can answer this issue. It's half a question about Cloud Feeds wadls & half a question about api validator.
I'm attempting to add a check to our wadls which are run by our api-validator. It's a long painful story, so I'll give you the short version, we can discuss in detail if required.
Within product.wadl, I'm adding a second rax:preprocess step after <rax:preprocess href="atom_hopper_pre.xsl"/> to perform a particular check and when I run this check, get the following error in the response (not an exception):
400
Bad Content: org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.
When I have my preprocess step before the atom_hopper_pre.xsl step, it works fine (but the check is too early and reports incorrect information).
Why does this happen? I'm stumped.
What's my check?
Our atom_hopper_pre.xsl step adds a category called "tid:[tenantid]" to the request. I want to ensure that the user does not submit a request with a category with "tid:[other value]". After our validator adds the tid-category, I want only one to exist. (We can't do this check before the tid-category is added because we currently have 2 validators and if the second validator is executed it will fail because the first validator already added the tid-category).
Here's the check (I commented out the logic to demonstrate the error condition.
RackerWilliams
changed the title
HIERARCHY_REQUEST_ERR when adding multiple preprocess rules
HIERARCHY_REQUEST_ERR when adding multiple preprocess
Jul 2, 2014
Greg reported the following:
On Jul 1, 2014, at 5:41 PM, Greg Sharek [email protected] wrote:
The text was updated successfully, but these errors were encountered: