Improve @JsonView flexibility

[stickfigure]

I'm struggling with a problem that is probably common for people that extensively use @JSONVIEW. Since only one view can be active at any one time, and jsonview classes are singly-inherited, the facility is very tightly constrained. There are a lot of cases where I need to define multiple views: "Show me the properties relevant to green administrators and the fields relevant to blue administrators", where these are not perfect subsets.

From an API perspective, one solution would be to allow json views to be defined by interfaces and thus enable multiple inheritance. Alternatively, just allow multiple views to be specified - although this raises the question of AND vs OR.

P.S. Thank you thank you THANK YOU for moving development to github!

[cowtowncoder]

Ok, quick note: this particular issue is related to databind (https://github.com/FasterXML/jackson-databind). Could you re-create it there? (I havent found move button at github's issue tracker yet... :-/ )

[stickfigure]

Done!

[cowtowncoder]

Great, thanks! I will add comments there. And thank you for starting discussions here over at github, I agree in that move here should be a very good thing; and one way to speed up transition is to move things.