Hi,

I believe this is a common enough use case when people want to restrict 
additional properties in every layer of their schema. Currently,  I found 
that there is a way to do it to each individual object, but not directly 
for an object that may have nested objects and so forth.

Is there a reason this is not supported? If this is due to a lack of 
interest or something similar, I can help contribute :)

-- 
*Disclaimer: *This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to whom they 
are addressed. If you have received this email in error please notify the 
system manager. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee 
you should not disseminate, distribute or copy this e-mail. Please notify 
the sender immediately by e-mail if you have received this e-mail by 
mistake and delete this e-mail from your system. If you are not the 
intended recipient you are notified that disclosing, copying, distributing 
or taking any action in reliance on the contents of this information is 
strictly prohibited.

-- 
You received this message because you are subscribed to the Google Groups 
"jackson-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jackson-user/020a8a65-7227-43f3-85f3-e899f8bff9fan%40googlegroups.com.

Reply via email to