Re: [hibernate-dev] [SEARCH] 6.0: what if we flipped our metadata definition upside down?

2017-03-27 Thread Yoann Rodiere
> Independently from which one we read from first, won't there always be > a risk of forgetting the other input processing blocks? With that in mind: yes, even if what I propose, there will still be a risk of forgetting to add a feature to one API or the other, but I think the risk will be lower i

Re: [hibernate-dev] [SEARCH] 6.0: what if we flipped our metadata definition upside down?

2017-03-27 Thread Sanne Grinovero
I don't mean this to be a strict "No", but I'm not convinced for now on the benefits such an exercise in refactoring brings.. In a nutshell the goal is reading from {Annotations, ProgrammaticAPI} -> Actual applied Metadata. Independently from which one we read from first, won't there always be a

[hibernate-dev] [SEARCH] 6.0: what if we flipped our metadata definition upside down?

2017-03-27 Thread Yoann Rodiere
Hello, Currently, the medata definition mechanisms in Search work this way: - the primary way to define metadata is using annotations - the secondary way to define metadata is programmatic, *but it only instantiates annotations,* simulating annotated entities - classes needing to acce