First, lets just drop "Hibernate entity name" ;) We are talking about
Hibernate development; if we prefixed every Hibernate concept with
HibernateXYZ...
On Fri 06 Jul 2012 09:59:13 AM CDT, Strong Liu wrote:
> okay, let me summary it here and see if i get it correct
>
> 1. entitybinding is keye
okay, let me summary it here and see if i get it correct
1. entitybinding is keyed by (hibernate) entity name in metamodel
2. (hibernate) entity name should be FQN of the entity class (both hbm and
annotation?)
3. it is correct assumption to throw exception when needs to look up an
entitybinding
Ok, should have gone back to original question
Yes, you can name either Class name or entity-name, here. In fact thats
true of most of the Hibernate APIs. Its a historical thing. Before
Hibernate APIs were just like the JPA APIs in that you could only
reference entities by Class reference. W
Hei,
jeg har sommerferie og er tilbake i jobb mandag 30. juli.
Generelle henvendelser kan sendes til p...@hmskontoret.no. Du finner
ytterligere informasjon om hvordan du kontakter HMS Kontoret i ferien her:
www.hmskontoret.no.
God sommer!
___
hibe
In Hibernate terminology it is a special form of HQL import name.
However, it has a special meaning as well in that
javax.persistence.metamodel.EntityType#getName should return this value,
whereas that is not true of any explicit import names (in Hibernate you
can give an entity any number of i
>> In Hibernate you can map the same class multiple times using
>> different entity names. The map of entity bindings kept in Metadata
>> contains
>> all entity bindings keyed against these unique names. Trying to look
>> up a binding by class name is not unique and we would have to deal with
>>
On Jul 6, 2012, at 4:08 PM, Steve Ebersole wrote:
> We need JPA entity-name as a separate deal. There is a reason I added it ;)
Right. I know you keep saying this :-) It's just I have not seen this reason
yet. I guess if I would dig deeper into the code
I would find it somewhere
> Its not th
Hi,
here are some of my thoughts around this.
In Hibernate you can map the same class multiple times using different entity
names. The map of entity bindings kept in Metadata contains
all entity bindings keyed against these unique names. Trying to look up a
binding by class name is not unique
Hi,
first up some info regarding the xsd. We initially auto generated it from our
dtd and then made some adjustments to resolve
some conflicts. The outcome is for sure less than optimal.
> I have two question about this xsd:
>
> 1. why we use xs:string for attributes such as timeout, batch-size
Hi,
I have two question about this xsd:
1. why we use xs:string for attributes such as timeout, batch-size, is there a
specific reason?
I'm purposing this change https://gist.github.com/3059390
2. we used to have this with the dtd, but I doubt if it is still possible with
in the current xsd.
Hi,
having a question as $subject.
the return element (org.hibernate.internal.jaxb.mapping.hbm.JaxbReturnElement)
has both entity name and class name attributes, and we are supposed to use one
of them to get the target EntityBinding.
though look up entitybinding by entityname is easy, but I'm
11 matches
Mail list logo
