On 26 June 2012 21:17, Hardy Ferentschik <hardy(a)hibernate.org> wrote:
On 26 Jun 2012, at 21:37, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> Ok that sounds all nice. But we need programmatic definition of
> annotations too, you remember Hibernate Search right?
How is that conceptually different than XML defined ones?
Not conceptually, but in practice, does Jandex support this directly
or should we add a thin layer of indirection?
Plus, you're suggesting we re-wire dependencies in other modules too
right? (like Search)
> The first point you make about the XClass abstraction sounds to me a
> good one, a good reason to use it. It doesn't have to be big and
> bloated, but if we have a simple way to abstract from the annotation
> reading
> - XML
> - Class definitions
> - programmatic overrides
That's where the Jandex index comes in. It can abstract all of this and once all the
right information is in the index we just use it to process the annotation (real or pseudo
ones).
> in a single API, that sounds like a good thing?
Right, that's what I want as well
> You mention this API
> is confusing, maybe we can improve on it?
Why, when there is a better approach?
> Sounds better than to have
> to deal with the three sources independently.
We won't have to.
--hardy