-
Notifications
You must be signed in to change notification settings - Fork 37
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
SML error details should be propagated better to the outside world #268
Comments
When trying to register a participant identifier to the SML that is already reserved by another SMP the REST API responds with a 500 error with a generic message like The logs from phoss-smp in these cases are something like this
While investigating the issue and calling the SML with another SOAP implementation I was able to extract the raw response from the SML.
Note: The participant identifier 0000:123456 is a fictional one. |
This depends on phax/peppol-commons#48 |
The problem is, that the SML currently does not act standard compliant. It returns SOAP 1.1 faults with an HTTP Status Code different to 500 which the underlying JAXWS implementation doesn't like at all. |
To make better differentiations
The text was updated successfully, but these errors were encountered: