Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [Teneo] Null Pointer Exception in HbDataStore ComputeReferers
| | | |
| Re: [Teneo] Null Pointer Exception in HbDataStore ComputeReferers [message #75194 is a reply to message #75177] |
Mon, 12 March 2007 14:44   |
 Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Are you initializing the hbdatastore with the same properties (suc as qualify entity names) as used
for generating the hbm.xml?
A few lines higher in hbdatastore you can see these lines:
final Property prop = (Property) propIt.next();
EClass eClass;
try{
eClass = getPersistenceOptions().getEClassNameStrategy().toEClass(pc. getEntityName(), getEPackages());
} catch (IllegalArgumentException e) {
// ignoring exception on purpose
eClass = null;
}
final EStructuralFeature ef = eClass == null ? null : StoreUtil.getEStructuralFeature(eClass,
prop.getName());
apparently eClass and/or ef is null. Can you check which or why? This can be related to the fact
that maybe your hibernate.hbm.xml was generated using qualify entity names, while you run the
hbdatastore while not using these options (or the other way around).
This part of the code computes the referers. The hbdatastore offers a (fairly unknown) method which
allows you to retrieve all the referers to a certain object. The computereferers method computes
which other types can refer to a certain type and pre-creates all the queries.
gr. Martin
Duncan ALexander wrote:
> The ecore for the Identifier component and its related
> PartialTargetIdentifier feature looks like:
>
> <eClassifiers xsi:type="ecore:EClass" name="PartialTargetIdentifier"
> eSuperTypes="base.ecore#//ComponentList">
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="MetadataStructure" lowerBound="1"
> eType="#//MetadataStructure" transient="true"
> eOpposite="#//MetadataStructure/PartialTargetIdentifier"/>
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="IdentifierComponent" lowerBound="1"
> upperBound="-1" eType="#//IdentifierComponent"
> eOpposite="#//IdentifierComponent/PartialTargetIdentifier"/ >
> </eClassifiers>
> <eClassifiers xsi:type="ecore:EClass" name="IdentifierComponent"
> eSuperTypes="base.ecore#//Component">
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="FullTargetIdentifier" lowerBound="1"
> eType="#//FullTargetIdentifier" transient="true"
> eOpposite="#//FullTargetIdentifier/IdentifierComponent"/>
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="PartialTargetIdentifier"
> upperBound="-1" eType="#//PartialTargetIdentifier"
> eOpposite="#//PartialTargetIdentifier/IdentifierComponent"/ >
> </eClassifiers>
>
>
>
>
> Duncan ALexander wrote:
>> It looks its an
>> org.hibernate.mapping.List(ref.IdentifierComponent.PartialTa rgetIdentifier).
>>
>>
>> From looking at my model, it may be that there is a slightly
>> unmanageable relationship here although Im not sure how to test if
>> that is true.
>>
>> What is this method doing, is it tracing through all the potential
>> references between the classes ?
>>
>> Duncan
>>
>> Martin Taal wrote:
>>> Can you see which efeature it is trying to report there (the name of
>>> the property is the same as the name of the efeature)?
>>> And is there anything special with this efeature?
>>>
>>> gr. Martin
>>>
>>> Duncan ALexander wrote:
>>>> Hi,
>>>> I have been attempting to intialize an HB Datastore however I am
>>>> hitting a Null Pointer
>>>> Exception in the computeReferers method of the HbDataStore. The full
>>>> stack trace is:
>>>>
>>>> java.lang.NullPointerException
>>>> at
>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.computeReferers( HbDataStore.java:742)
>>>>
>>>> at
>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.initialize(HbDat aStore.java:163)
>>>>
>>>> at
>>>> org.sdmx.registry.persistence.TestHibernateSessionManager.te stTeneoPersistence(TestHibernateSessionManager.java:471)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>
>>>> at
>>>> com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStar ter.java:32)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>
>>>> at
>>>> com.intellij.rt.execution.application.AppMain.main(AppMain.j ava:90)
>>>>
>>>>
>>>> Setup: Teneo 0.75, EMF 2.2, Hiberate 3.2, Java 1.5
>>>>
>>>> Other Info:
>>>>
>>>> Within my setup I am using a hibernate mapping file which I
>>>> generated with Teneo manually and force
>>>> its use through the USE_MAPPING_FILE persistence option.
>>>>
>>>> From tracing through the code it would appear that it is falling
>>>> over on this line below when it attempts to get the 'element' from
>>>> the property value and it is null. The property in question is an
>>>> org.hibernate.mapping.List.
>>>>
>>>> throw new HbMapperException("Type "+
>>>> ((Collection)prop.getValue()).getElement().getClass().getNam e()
>>>> + " not supported");
>>>>
>>>>
>>>> regards
>>>>
>>>> Duncan
>>>
>>>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Null Pointer Exception in HbDataStore ComputeReferers [message #75211 is a reply to message #75194] |
Mon, 12 March 2007 15:09 |
Duncan Alexander
Messages: 90
Registered: July 2009 |
Member |
|
|
Aha,
yes thats exactly what I was doing. I removed the entry for QUALIFY_ENTITY_NAME from the
persistence properties when I was creating the datastore as I thought it could have no effect at
this stage.
From tracing the code it was the eClass which was NULL.
I've now put the QUALIFY_ENTITY_NAME entry into the properties when creating the store and it has
created the Database. Excellent!!!
Have just spotted another error but Ill start another thread, this is a huge jump forward.
Thanks again Martin.
Duncan
Martin Taal wrote:
> Are you initializing the hbdatastore with the same properties (suc as
> qualify entity names) as used for generating the hbm.xml?
>
> A few lines higher in hbdatastore you can see these lines:
> final Property prop = (Property) propIt.next();
> EClass eClass;
> try{
> eClass =
> getPersistenceOptions().getEClassNameStrategy().toEClass(pc. getEntityName(),
> getEPackages());
> } catch (IllegalArgumentException e) {
> // ignoring exception on purpose
> eClass = null;
> }
>
> final EStructuralFeature ef = eClass == null ? null :
> StoreUtil.getEStructuralFeature(eClass, prop.getName());
>
> apparently eClass and/or ef is null. Can you check which or why? This
> can be related to the fact that maybe your hibernate.hbm.xml was
> generated using qualify entity names, while you run the hbdatastore
> while not using these options (or the other way around).
>
> This part of the code computes the referers. The hbdatastore offers a
> (fairly unknown) method which allows you to retrieve all the referers to
> a certain object. The computereferers method computes which other types
> can refer to a certain type and pre-creates all the queries.
>
> gr. Martin
>
> Duncan ALexander wrote:
>> The ecore for the Identifier component and its related
>> PartialTargetIdentifier feature looks like:
>>
>> <eClassifiers xsi:type="ecore:EClass" name="PartialTargetIdentifier"
>> eSuperTypes="base.ecore#//ComponentList">
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="MetadataStructure" lowerBound="1"
>> eType="#//MetadataStructure" transient="true"
>> eOpposite="#//MetadataStructure/PartialTargetIdentifier"/>
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="IdentifierComponent" lowerBound="1"
>> upperBound="-1" eType="#//IdentifierComponent"
>> eOpposite="#//IdentifierComponent/PartialTargetIdentifier"/ >
>> </eClassifiers>
>> <eClassifiers xsi:type="ecore:EClass" name="IdentifierComponent"
>> eSuperTypes="base.ecore#//Component">
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="FullTargetIdentifier" lowerBound="1"
>> eType="#//FullTargetIdentifier" transient="true"
>> eOpposite="#//FullTargetIdentifier/IdentifierComponent"/>
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="PartialTargetIdentifier"
>> upperBound="-1" eType="#//PartialTargetIdentifier"
>> eOpposite="#//PartialTargetIdentifier/IdentifierComponent"/ >
>> </eClassifiers>
>>
>>
>>
>>
>> Duncan ALexander wrote:
>>> It looks its an
>>> org.hibernate.mapping.List(ref.IdentifierComponent.PartialTa rgetIdentifier).
>>>
>>>
>>> From looking at my model, it may be that there is a slightly
>>> unmanageable relationship here although Im not sure how to test if
>>> that is true.
>>>
>>> What is this method doing, is it tracing through all the potential
>>> references between the classes ?
>>>
>>> Duncan
>>>
>>> Martin Taal wrote:
>>>> Can you see which efeature it is trying to report there (the name of
>>>> the property is the same as the name of the efeature)?
>>>> And is there anything special with this efeature?
>>>>
>>>> gr. Martin
>>>>
>>>> Duncan ALexander wrote:
>>>>> Hi,
>>>>> I have been attempting to intialize an HB Datastore however I
>>>>> am hitting a Null Pointer
>>>>> Exception in the computeReferers method of the HbDataStore. The
>>>>> full stack trace is:
>>>>>
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.computeReferers( HbDataStore.java:742)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.initialize(HbDat aStore.java:163)
>>>>>
>>>>> at
>>>>> org.sdmx.registry.persistence.TestHibernateSessionManager.te stTeneoPersistence(TestHibernateSessionManager.java:471)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>>
>>>>> at
>>>>> com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStar ter.java:32)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>>
>>>>> at
>>>>> com.intellij.rt.execution.application.AppMain.main(AppMain.j ava:90)
>>>>>
>>>>>
>>>>> Setup: Teneo 0.75, EMF 2.2, Hiberate 3.2, Java 1.5
>>>>>
>>>>> Other Info:
>>>>>
>>>>> Within my setup I am using a hibernate mapping file which I
>>>>> generated with Teneo manually and force
>>>>> its use through the USE_MAPPING_FILE persistence option.
>>>>>
>>>>> From tracing through the code it would appear that it is falling
>>>>> over on this line below when it attempts to get the 'element' from
>>>>> the property value and it is null. The property in question is an
>>>>> org.hibernate.mapping.List.
>>>>>
>>>>> throw new HbMapperException("Type "+
>>>>> ((Collection)prop.getValue()).getElement().getClass().getNam e()
>>>>> + " not supported");
>>>>>
>>>>>
>>>>> regards
>>>>>
>>>>> Duncan
>>>>
>>>>
>
>
|
|
| | | |
| Re: [Teneo] Null Pointer Exception in HbDataStore ComputeReferers [message #603527 is a reply to message #75177] |
Mon, 12 March 2007 14:44 |
Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Are you initializing the hbdatastore with the same properties (suc as qualify entity names) as used
for generating the hbm.xml?
A few lines higher in hbdatastore you can see these lines:
final Property prop = (Property) propIt.next();
EClass eClass;
try{
eClass = getPersistenceOptions().getEClassNameStrategy().toEClass(pc. getEntityName(), getEPackages());
} catch (IllegalArgumentException e) {
// ignoring exception on purpose
eClass = null;
}
final EStructuralFeature ef = eClass == null ? null : StoreUtil.getEStructuralFeature(eClass,
prop.getName());
apparently eClass and/or ef is null. Can you check which or why? This can be related to the fact
that maybe your hibernate.hbm.xml was generated using qualify entity names, while you run the
hbdatastore while not using these options (or the other way around).
This part of the code computes the referers. The hbdatastore offers a (fairly unknown) method which
allows you to retrieve all the referers to a certain object. The computereferers method computes
which other types can refer to a certain type and pre-creates all the queries.
gr. Martin
Duncan ALexander wrote:
> The ecore for the Identifier component and its related
> PartialTargetIdentifier feature looks like:
>
> <eClassifiers xsi:type="ecore:EClass" name="PartialTargetIdentifier"
> eSuperTypes="base.ecore#//ComponentList">
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="MetadataStructure" lowerBound="1"
> eType="#//MetadataStructure" transient="true"
> eOpposite="#//MetadataStructure/PartialTargetIdentifier"/>
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="IdentifierComponent" lowerBound="1"
> upperBound="-1" eType="#//IdentifierComponent"
> eOpposite="#//IdentifierComponent/PartialTargetIdentifier"/ >
> </eClassifiers>
> <eClassifiers xsi:type="ecore:EClass" name="IdentifierComponent"
> eSuperTypes="base.ecore#//Component">
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="FullTargetIdentifier" lowerBound="1"
> eType="#//FullTargetIdentifier" transient="true"
> eOpposite="#//FullTargetIdentifier/IdentifierComponent"/>
> <eStructuralFeatures xsi:type="ecore:EReference"
> name="PartialTargetIdentifier"
> upperBound="-1" eType="#//PartialTargetIdentifier"
> eOpposite="#//PartialTargetIdentifier/IdentifierComponent"/ >
> </eClassifiers>
>
>
>
>
> Duncan ALexander wrote:
>> It looks its an
>> org.hibernate.mapping.List(ref.IdentifierComponent.PartialTa rgetIdentifier).
>>
>>
>> From looking at my model, it may be that there is a slightly
>> unmanageable relationship here although Im not sure how to test if
>> that is true.
>>
>> What is this method doing, is it tracing through all the potential
>> references between the classes ?
>>
>> Duncan
>>
>> Martin Taal wrote:
>>> Can you see which efeature it is trying to report there (the name of
>>> the property is the same as the name of the efeature)?
>>> And is there anything special with this efeature?
>>>
>>> gr. Martin
>>>
>>> Duncan ALexander wrote:
>>>> Hi,
>>>> I have been attempting to intialize an HB Datastore however I am
>>>> hitting a Null Pointer
>>>> Exception in the computeReferers method of the HbDataStore. The full
>>>> stack trace is:
>>>>
>>>> java.lang.NullPointerException
>>>> at
>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.computeReferers( HbDataStore.java:742)
>>>>
>>>> at
>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.initialize(HbDat aStore.java:163)
>>>>
>>>> at
>>>> org.sdmx.registry.persistence.TestHibernateSessionManager.te stTeneoPersistence(TestHibernateSessionManager.java:471)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>
>>>> at
>>>> com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStar ter.java:32)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>
>>>> at
>>>> com.intellij.rt.execution.application.AppMain.main(AppMain.j ava:90)
>>>>
>>>>
>>>> Setup: Teneo 0.75, EMF 2.2, Hiberate 3.2, Java 1.5
>>>>
>>>> Other Info:
>>>>
>>>> Within my setup I am using a hibernate mapping file which I
>>>> generated with Teneo manually and force
>>>> its use through the USE_MAPPING_FILE persistence option.
>>>>
>>>> From tracing through the code it would appear that it is falling
>>>> over on this line below when it attempts to get the 'element' from
>>>> the property value and it is null. The property in question is an
>>>> org.hibernate.mapping.List.
>>>>
>>>> throw new HbMapperException("Type "+
>>>> ((Collection)prop.getValue()).getElement().getClass().getNam e()
>>>> + " not supported");
>>>>
>>>>
>>>> regards
>>>>
>>>> Duncan
>>>
>>>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Null Pointer Exception in HbDataStore ComputeReferers [message #603531 is a reply to message #75194] |
Mon, 12 March 2007 15:09 |
Duncan Alexander
Messages: 90
Registered: July 2009 |
Member |
|
|
Aha,
yes thats exactly what I was doing. I removed the entry for QUALIFY_ENTITY_NAME from the
persistence properties when I was creating the datastore as I thought it could have no effect at
this stage.
From tracing the code it was the eClass which was NULL.
I've now put the QUALIFY_ENTITY_NAME entry into the properties when creating the store and it has
created the Database. Excellent!!!
Have just spotted another error but Ill start another thread, this is a huge jump forward.
Thanks again Martin.
Duncan
Martin Taal wrote:
> Are you initializing the hbdatastore with the same properties (suc as
> qualify entity names) as used for generating the hbm.xml?
>
> A few lines higher in hbdatastore you can see these lines:
> final Property prop = (Property) propIt.next();
> EClass eClass;
> try{
> eClass =
> getPersistenceOptions().getEClassNameStrategy().toEClass(pc. getEntityName(),
> getEPackages());
> } catch (IllegalArgumentException e) {
> // ignoring exception on purpose
> eClass = null;
> }
>
> final EStructuralFeature ef = eClass == null ? null :
> StoreUtil.getEStructuralFeature(eClass, prop.getName());
>
> apparently eClass and/or ef is null. Can you check which or why? This
> can be related to the fact that maybe your hibernate.hbm.xml was
> generated using qualify entity names, while you run the hbdatastore
> while not using these options (or the other way around).
>
> This part of the code computes the referers. The hbdatastore offers a
> (fairly unknown) method which allows you to retrieve all the referers to
> a certain object. The computereferers method computes which other types
> can refer to a certain type and pre-creates all the queries.
>
> gr. Martin
>
> Duncan ALexander wrote:
>> The ecore for the Identifier component and its related
>> PartialTargetIdentifier feature looks like:
>>
>> <eClassifiers xsi:type="ecore:EClass" name="PartialTargetIdentifier"
>> eSuperTypes="base.ecore#//ComponentList">
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="MetadataStructure" lowerBound="1"
>> eType="#//MetadataStructure" transient="true"
>> eOpposite="#//MetadataStructure/PartialTargetIdentifier"/>
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="IdentifierComponent" lowerBound="1"
>> upperBound="-1" eType="#//IdentifierComponent"
>> eOpposite="#//IdentifierComponent/PartialTargetIdentifier"/ >
>> </eClassifiers>
>> <eClassifiers xsi:type="ecore:EClass" name="IdentifierComponent"
>> eSuperTypes="base.ecore#//Component">
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="FullTargetIdentifier" lowerBound="1"
>> eType="#//FullTargetIdentifier" transient="true"
>> eOpposite="#//FullTargetIdentifier/IdentifierComponent"/>
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="PartialTargetIdentifier"
>> upperBound="-1" eType="#//PartialTargetIdentifier"
>> eOpposite="#//PartialTargetIdentifier/IdentifierComponent"/ >
>> </eClassifiers>
>>
>>
>>
>>
>> Duncan ALexander wrote:
>>> It looks its an
>>> org.hibernate.mapping.List(ref.IdentifierComponent.PartialTa rgetIdentifier).
>>>
>>>
>>> From looking at my model, it may be that there is a slightly
>>> unmanageable relationship here although Im not sure how to test if
>>> that is true.
>>>
>>> What is this method doing, is it tracing through all the potential
>>> references between the classes ?
>>>
>>> Duncan
>>>
>>> Martin Taal wrote:
>>>> Can you see which efeature it is trying to report there (the name of
>>>> the property is the same as the name of the efeature)?
>>>> And is there anything special with this efeature?
>>>>
>>>> gr. Martin
>>>>
>>>> Duncan ALexander wrote:
>>>>> Hi,
>>>>> I have been attempting to intialize an HB Datastore however I
>>>>> am hitting a Null Pointer
>>>>> Exception in the computeReferers method of the HbDataStore. The
>>>>> full stack trace is:
>>>>>
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.computeReferers( HbDataStore.java:742)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.teneo.hibernate.HbDataStore.initialize(HbDat aStore.java:163)
>>>>>
>>>>> at
>>>>> org.sdmx.registry.persistence.TestHibernateSessionManager.te stTeneoPersistence(TestHibernateSessionManager.java:471)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>>
>>>>> at
>>>>> com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStar ter.java:32)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>>>
>>>>> at
>>>>> com.intellij.rt.execution.application.AppMain.main(AppMain.j ava:90)
>>>>>
>>>>>
>>>>> Setup: Teneo 0.75, EMF 2.2, Hiberate 3.2, Java 1.5
>>>>>
>>>>> Other Info:
>>>>>
>>>>> Within my setup I am using a hibernate mapping file which I
>>>>> generated with Teneo manually and force
>>>>> its use through the USE_MAPPING_FILE persistence option.
>>>>>
>>>>> From tracing through the code it would appear that it is falling
>>>>> over on this line below when it attempts to get the 'element' from
>>>>> the property value and it is null. The property in question is an
>>>>> org.hibernate.mapping.List.
>>>>>
>>>>> throw new HbMapperException("Type "+
>>>>> ((Collection)prop.getValue()).getElement().getClass().getNam e()
>>>>> + " not supported");
>>>>>
>>>>>
>>>>> regards
>>>>>
>>>>> Duncan
>>>>
>>>>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 09:24:34 GMT 2024
Powered by FUDForum. Page generated in 0.02609 seconds |
] 
Search
Help
Register
Login
Home
