Not much discussed again today:
[10:11] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-06-03-14.45.html
[10:11] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-06-03-14.45.txt
[10:1
The point is to delay accessing ClassLoader. The reason being runtime
enhancement. If we load Classes at this point we wont be able to enhance
them later when JPA hooks allow us to.
On Tue, Jun 3, 2014 at 8:33 AM, Gunnar Morling wrote:
> Hi,
>
> I haven't followed the discussion around "refli
Hi,
I haven't followed the discussion around "reflite" closely, so I'm just
going to add some thoughts/questions coming to my mind after exploring the
model a bit:
* Is there some sort of design document which describes at a higher level
the purpose and the benefit of the model? If not, e.g. Java
I just want to make sure this is consistent across uses. What are the
rules for Audited, MappedSuperclass and Entity? IMO, that is what should
happen for Audited, MappedSuperclass and Embeddable as well. Are those
consistent?
Adam, what specifically is complicated by supporting AO paths? Is it
Not exactly sure what you mean by "favoured" it. I'm the one who wrote it
all for sure, if that's what you mean. But I was just trying something.
The java.lang.Class model has pros and cons to it. I had just wanted to
investigate alternative models to see whether those pros/cons could be
improv
On 2 Jan 2014, at 18:36, Steve Ebersole wrote:
> 1) What do you think of the split in JavaTypeDescriptor into distinct
> sub-contracts? For example, the split between say ClassDescriptor and
> InterfaceDescriptor?
Didn’t we have this discussion before. If I remember correctly you were the on
