I'm not an expert but as far as I know the endpoint is associated to the binding, so it is difficult to get the endpoint in the calling component.
A thought can be to create a Custom Message Composer that gets the the endpoint from the BindingData and put it in an Exchange header, so that you can use it in the component to compose the message to the client.
It is difficult to explain, but I think it could work. If you watch the forums, there are references on how to do it.
Hope it helps.
The info is likely getting clipped in our gateway or the RESTEasy client layer. If you are up for debugging, I would set a breakpoint here and see how the error is mapped into RESTEasyBindingData (I suspect something is lost there):
Or if you want to attach a reproducer we can have a look. If the error details make it into RESTEasyBindingData, then you can grab them in a custom message composer. If not, then it's a bug and component code fix.
The RESTEasyBindingData object never gets instantiated on line 292 when either HTTP 404 or 500 related problems occur.
Instead, the thread of execution errors outs on the line just prior (291) when trying to process the original HTTP error code and message.
Subsequently, what's left in the stack trace is only a message such as: Error status 404 Not Found returned
Want me to create a BZ on this ?
Yes, please do! Thanks, Jeff.
Sorry for jumping in again, but while the JIRA gets solved, and so, probably doing as I mentioned can, at least get you the URL back to your component, so you can create a more meaningful message in the meanwhile.
Due to the exception, the message never gets composed, but it gets decomposed, so you can insert into the Exchange a property with the actual URL invoked that you can retrieve in your component.
If I'm totally lost, just skip this message and don't hit at me, I'm trying to help, and been bitten a lot lately.
You may be on to something. I'm going to experiment with this. thanks!