Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
IncomingRequestPreHandled interceptor Method does not identify the resource for @Validate Method #297
Logging as an issue to keep track as per James
James Agnew email@example.com
to me, HAPI
I had a look at this, and I am able to reproduce it.
The cause looks to be the fact that as of DSTU2, validate is an "extended operation" and it looks like resource doesn't get populated for any operation. I have a working unit test at least, so hopefully this can be fixed in the current development cycle. If you wanted to file a bug to track progress, that would be great.
On Thu, Feb 11, 2016 at 4:27 PM, firstname.lastname@example.org wrote:
This Ravi Kuchi from FMCNA development team.
The incomingRequestPreHandled method in the IServerInterceptor interface does return all the Objects sent in the body for @create and @update methods. I have been very successful in trapping the requests and responses using the interceptor so that I can write them into the AuditEvent record for trouble shooting and security audits. However one problem I could not overcome is that the interceptor does not inject the Object into the incomingRequestPreHandled when we use the @Validate Method. There is a use case for me to write a log for all the requests that come into my FHIR webservice via the @Validate method so that we can see the values the user has entered via the UI and respond back saying what errors he had made in providing the input.
Please let me know if I am overlooking something here.