Error prone utilities: AbstractContentResource#getRequestContentNode() and #getRequestContentBean()

The two methods (AbstractContentResource#getRequestContentNode() and #getRequestContentBean()) are used often by JAX-RS Resource components.
Currently the two utility methods depend on a Node object which is stored by CXFJaxrsContentService.
Normally, this is no problem.
However, if you change current content through CMS Workflow API via REST API, then the stored node will not be valid any more. The identifier can be changed and so the pre-stored node is invalid.
Therefore, my suggestion would be to store the content node path only in CXFJaxrsContentService and the two utility method (AbstractContentResource#getRequestContentNode() and #getRequestContentBean()) should try to retrieve the content object by the path every time.
This will reduce this kind of errors and time to find the problems.