What do you think about collapsing these into a single spi contract, rather
than broken out (e.g., more akin to jdk reflection)? Specifically in
regards to ClassDescriptor and InterfaceDescriptor
On Mon, Jun 2, 2014 at 12:47 PM, Gail Badner <gbadner(a)redhat.com> wrote:
Hi Steve,
I haven't had much of a chance to use it yet, but I like what I've seen so
far. When I get back to Envers (later this week), there are places that use
the Jandex index that I will change to use reflite. I'll have more feedback
then.
Gail
----- Original Message -----
> From: "Steve Ebersole" <steve(a)hibernate.org>
> To: "hibernate-dev" <hibernate-dev(a)lists.jboss.org>
> Sent: Monday, June 2, 2014 9:36:09 AM
> Subject: [hibernate-dev] Reflite
>
> I am curious about people's take on "reflite" now that some of
y'all have
> had a chance to see it in action.
>
> Some specific points I am curious about (although certainly feel free to
> comment on any parts):
>
> 1) What do you think of the split in JavaTypeDescriptor into distinct
> sub-contracts? For example, the split between say ClassDescriptor and
> InterfaceDescriptor? TBH, I am starting to rethink that one. What about
> primitive versus non-primitive descriptors? Etc...
>
> 2) Overall what do you think about the API itself? Don't worry about the
> internal details. For example, the need to access the ClassLoader (to
walk
> the fields/methods) is hopefully going away with some additions to
Jandex.
> But in terms of the exposed contracts
> (org.hibernate.metamodel.reflite.spi)...
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>