-
Notifications
You must be signed in to change notification settings - Fork 43
FAQ
Captain-P-Goldfish edited this page Nov 16, 2019
·
3 revisions
this has a strategic reason. This framework allows defining resource types dynamically and the operations are handled on extensions of the ResourceNode class. So if a developer decides to use the same ResourceHandler implementation for all or at least for several resource types it is necessary to know what type of resource is currently handled and this information is added to the meta-attribute just before the create or update method is called. so resetting the meta-attribute would remove the resourceType attribute from meta what would eventually result in a DocumentValidationException.