I forgot to mention that this is largely still incubating. I realized that overall we need to re-think how we do class loading and reflection (in terms of field/method discovery).
I do not mean just this specific part. I mean throughout bootstrapping. This view might change as we redesign annotation binding. This discussion is probably worth its own subject, so I will follow up. On Wed, Jun 3, 2015 at 9:00 AM Steve Ebersole <st...@hibernate.org> wrote: > I hinted at this in the 'Envers ReflectionTools' email, but wanted to > follow up with some details. Part of the work to move away from the last > bits of TCCL-based classloading was completely > redesigning PropertyAccessorFactory/PropertyAccessor (work which is long > overdue anyway). Just a heads up that this is no longer a straight-forward > migration item. > > I took advantage of the opportunity to apply the package split here. > > I also took this as a chance to add another strategy allowing a mix of > Field and Method based access. We talk about this strategy in > documentation and other places, so it always made sense to me to provide > it. At the moment however I am looking for names for this in terms of > specifying it in mappings/annotations. <property ... access="???"/>. > "mixed"? > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
