I had forgotten that I actually had already wired this in... The
contract you want is
org.hibernate.metamodel.spi.AdditionalJaxbRootProducer:
public interface AdditionalJaxbRootProducer {
/**
* Produce and return the list of additional mappings to be processed.
*
It wont be via Integrator. This is the same discussion you and I had
with Max wrt tooling. I'll ping you when Jandex is available for use by
Envers (I'll take care of all the wiring). Hopefully should be done
tomorrow or the day after.
On 09/08/2012 05:37 AM, Łukasz Antoniak wrote:
> Hello H
Hello Hardy,
Thank you for the clarification. This is what I thought initially by
looking at the code. I have reviewed the relevant mailing list topic,
and would agree that Jandex repository should be passed to integrator
somehow. Other Hibernate extensions probably introduce custom
annotations as
Should have mentioned to look at Index, ClassInfo and AnnotationInstance to get
a feel for the Jandex API. You find the Jandex project on Github -
https://github.com/jbossas/jandex. I don't think there is a project website yet.
--hardy
On 7 Sep 2012, at 22:05, Łukasz Antoniak wrote:
> Hello
Hi Lukasz,
The metamodel branch makes use of Jandex which is a sort of a annotation
repository/index (used also by AS). All annotated classes get added to this
index. I would expect that Envers uses this as well. Either by creating its own
Jandex index (probably not so good idea) or by reusing
Hello Steve,
Just wanted to let you know that I am trying to migrate Envers to new
metamodel. I have asked below question on IRC, but without any
response. At the moment Envers locates its annotations (for example
@Audited) using ReflectionManager. What would be the preferable way of
achieving thi
Lukasz, as always, any help you can give is appreciated! Whenever you
have time. We have a temporary solution that will isolate needed
changes to just Envers. Basically the changes at some point will be
using the JAXB binding model rather than DOM.
On Fri 24 Aug 2012 01:55:55 AM CDT, Łukasz
Hello Steve,
I think I could start working on metamodel branch at the beginning of
September. Is it acceptable for you? I don't want to
postpone 4.1.7 release. JIRA task has been already registered:
https://hibernate.onjira.com/browse/HHH-7490.
Best Regards,
Lukasz
__ Information fro
Honestly, I'd prefer it build a JAXB model. As is there would be
unnecessary overhead to bind the DOM model to the JAXB model. Plus, on
the producer side (envers) it gives type-safety.
But of course this requires changing how envers builds its metamodel.
Adam, Lukasz, is this something y'all
On Aug 22, 2012, at 8:11 AM, Steve Ebersole wrote:
> Also, I think how you were expecting beforeMetadataProcessing to happen can't
> really happen, but I suspect it is the more direct way to port envers.
>
> I *think* what you were thinking is to have envers pass along its extra
> EntitySourc
10 matches
Mail list logo
