-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No valid parse found" exceptions are not reported correctly when installing embedded components #218
Comments
I've created a test for this case (it didn't exists), but is working as expected. I'm investigating. |
@aarranz How to upgrade my recently developed https://wirecloud.conwet.fi.upm.es/ns/template# based widget ? -- Update |
@markrey Yeah, that's the command :). The only thing to take into account is that you have to use WireCloud 0.9.0 or bellow for being able to convert old description files ;-). |
We have deployed WireCloud 1.0 on FIWARE Lab. For the moment, there are not errors related to this error message, so I'm going to close this ticket. |
New exception from FIWARE Lab:
|
Everytime a "No parse found" exception is raised while installing embedded responses, WireCloud responds with an internal server error response. WireCloud should respond with a 400 error response and with a proper error message.
Moreover, WireCloud should use a better error message for end-users (instead of the "No valid parse found" message). Something like, "Unable to process the component description file". And something like "The description file used by this component is not longer supported" if we detect that the component is using the old
http://wirecloud.conwet.fi.upm.es/ns/template#
description format.Stack Trace (from FIWARE Lab, version 0.9.2):
The text was updated successfully, but these errors were encountered: