Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [Teneo] Problem mapping an EMF relationship in Teneo
[Teneo] Problem mapping an EMF relationship in Teneo [message #648096] Tue, 11 January 2011 08:41 Go to next message
Fer Missing name is currently offline Fer Missing nameFriend
Messages: 24
Registered: September 2009
Junior Member
Hello all,

First of all, Happy New Year!!

I'm having problems when trying to save the following relationship in H2 database using Teneo 1.1.2 + Hibernate 3.6. Please, see the EMF relationship below. When the relationship checkedElement is removed work fine.

EMF relationship (image):
http://yuml.me/diagram/scruffy/class/[DatasetCheckAnnotation] 0..* checkAnnotations-++0..1 checkedElement  [ICheckeableElement]
, [DatasetCheckAnnotation]^[DataSetCheckIssue]
, [ICheckeableElement]^[ICommonElement]


Part of ecore:
...
<eClassifiers xsi:type="ecore:EClass" name="ICommonElement" abstract="true" interface="true">
    <eAnnotations source="http://www.vsd-project.org/vsee/annotation/stereotype">
      <details key="name" value="Interface"/>
    </eAnnotations>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="name" unique="false" eType="#//String"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="unique_identifier" unique="false"
        eType="#//String" iD="true"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="deleted" unique="false"
        eType="#//Boolean" defaultValueLiteral="false"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="locked" unique="false"
        eType="#//Boolean" defaultValueLiteral="false"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="owner" unique="false" eType="#//String"/>
  </eClassifiers>
<eSubpackages name="datasetchecking" nsURI="http://www.vsd-project.org/qudv/datasetchecking/1.0"
      nsPrefix="datasetchecking">
    <eClassifiers xsi:type="ecore:EClass" name="DataSetCheckIssue" eSuperTypes="#//datasetchecking/DataSetCheckAnnotation">
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="issue" unique="false"
          eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="featureId" unique="false"
          eType="#//StructuralFeatureId" defaultValueLiteral="-1"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="indicatingCheckId" unique="false"
          eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="indicatingCheckDescription"
          unique="false" eType="#//String"/>
    </eClassifiers>
    <eClassifiers xsi:type="ecore:EClass" name="DataSetCheckAnnotation" abstract="true">
      <eStructuralFeatures xsi:type="ecore:EReference" name="checkedElement" eType="#//datasetchecking/ICheckableElement"
          eOpposite="#//datasetchecking/ICheckableElement/checkAnnotations"/>
    </eClassifiers>
    <eClassifiers xsi:type="ecore:EClass" name="ICheckableElement" abstract="true"
        interface="true" eSuperTypes="#//ICommonElement">
      <eAnnotations source="http://www.vsd-project.org/vsee/annotation/stereotype">
        <details key="name" value="Interface"/>
      </eAnnotations>
      <eStructuralFeatures xsi:type="ecore:EReference" name="checkAnnotations" upperBound="-1"
          eType="#//datasetchecking/DataSetCheckAnnotation" containment="true" eOpposite="#//datasetchecking/DataSetCheckAnnotation/checkedElement"/>
    </eClassifiers>
  </eSubpackages>
<eSubpackages name="file" nsURI="http://www.vsd-project.org/vsd/file/1.0" nsPrefix="vsee.file">
    <eClassifiers xsi:type="ecore:EClass" name="EngineeringDataFile" eSuperTypes="#//ICommonElement #//datasetmerging/IMergeableElement #//datasetchecking/ICheckableElement">
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="description" unique="false"
          eType="#//String">
        <eAnnotations source="http://www.vsd-project.org/vsee/annotation/technical">
          <details key="isMultiLine" value="true"/>
        </eAnnotations>
      </eStructuralFeatures>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="category" unique="false"
          eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="MIMEType" unique="false"
          eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="author" unique="false"
          eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="date" unique="false"
          eType="#//Date"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="size" unique="false"
          eType="#//Integer" defaultValueLiteral="0"/>
      <eStructuralFeatures xsi:type="ecore:EAttribute" name="url" unique="false" eType="#//String"/>
      <eStructuralFeatures xsi:type="ecore:EReference" name="relatedItem" upperBound="-1"
          eType="#//EngineeringDataItem" eOpposite="#//EngineeringDataItem/relatedFile"/>
    </eClassifiers>
    <eClassifiers xsi:type="ecore:EClass" name="FileModel" eSuperTypes="#//ICommonElement #//datasetmerging/IMergeableElement #//datasetchecking/ICheckableElement">
      <eStructuralFeatures xsi:type="ecore:EReference" name="file" upperBound="-1"
          eType="#//file/EngineeringDataFile" containment="true"/>
    </eClassifiers>
  </eSubpackages>
...


I have tested two cases in H2 database:

The first case is when the relationship checkedElement is present:

Since the table datasetcheckannotation has a foreign key with all tables that derive from classes implementing ICheckableElement (i.e. see FileModel above), this means that when a new row is inserted in datasetcheckannotation the value of the field datasetcheckannotation_checkedelement_unique_identifier has to be found in all tables, engineeringannotationitem, constraintmodel, filemodel, etc (and the list is veeery long). This is conceptually impossible, of course.

The second case is when the relationship checkedElement is not present, removing the association from DatasetCheckAnnotation to ICheckablelement:

In this case, the table datasetcheckannotation is provided with a lot of fields representing the relationship to each particular table implementing the ICheckableElement interface.

The actual problem is the association between DataSetCheckAnnotation and ICheckableElement. For some reason, when this association is present Teneo chooses to change the implementation from several fields to only one field with lots of FKs.

Thanks in advance.

Fernando
Re: [Teneo] Problem mapping an EMF relationship in Teneo [message #648208 is a reply to message #648096] Tue, 11 January 2011 18:51 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Fernando,
By listing the ICheckableElement as the last supertype it is not reflected in the table structure, so therefore you get
all these fields. I guess that "#//datasetchecking/ICheckableElement/checkAnnotations" is a multiple ereference, this
means that for this association the foreign key column has to be placced in the DataSetCheckAnnotation table, resulting
in a column for each implementation of ICheckableElement.
The best solution is if you can make ICheckableElement the main supertype which drives the db schema, then you will only
get one join column in DataSetCheckAnnotation:

See here:
http://wiki.eclipse.org/Teneo/Hibernate/ModelRelational/Inhe ritance_Mapping#Multiple_Inheritance_Support

That one column has multiple fk's is wrong but difficult to prevent as the efeature is defined in the interface. You can
override the column name by adding attribute override annotations to each subtype of ICheckableElement, but that's very
tedious...

gr. Martin

On 01/11/2011 09:41 AM, Fer wrote:
> Hello all,
>
> First of all, Happy New Year!!
>
> I'm having problems when trying to save the following relationship in H2 database using Teneo 1.1.2 + Hibernate 3.6.
> Please, see the EMF relationship below. When the relationship checkedElement is removed work fine.
>
> EMF relationship (image):
> http://yuml.me/diagram/scruffy/class/[DatasetCheckAnnotation] 0..* checkAnnotations-++0..1 checkedElement
> [ICheckeableElement]
> , [DatasetCheckAnnotation]^[DataSetCheckIssue]
> , [ICheckeableElement]^[ICommonElement]
>
> Part of ecore:
>
> ...
> <eClassifiers xsi:type="ecore:EClass" name="ICommonElement" abstract="true" interface="true">
> <eAnnotations source="http://www.vsd-project.org/vsee/annotation/stereotype">
> <details key="name" value="Interface"/>
> </eAnnotations>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name" unique="false" eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="unique_identifier" unique="false"
> eType="#//String" iD="true"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="deleted" unique="false"
> eType="#//Boolean" defaultValueLiteral="false"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="locked" unique="false"
> eType="#//Boolean" defaultValueLiteral="false"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="owner" unique="false" eType="#//String"/>
> </eClassifiers>
> <eSubpackages name="datasetchecking" nsURI="http://www.vsd-project.org/qudv/datasetchecking/1.0"
> nsPrefix="datasetchecking">
> <eClassifiers xsi:type="ecore:EClass" name="DataSetCheckIssue" eSuperTypes="#//datasetchecking/DataSetCheckAnnotation">
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="issue" unique="false"
> eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="featureId" unique="false"
> eType="#//StructuralFeatureId" defaultValueLiteral="-1"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="indicatingCheckId" unique="false"
> eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="indicatingCheckDescription"
> unique="false" eType="#//String"/>
> </eClassifiers>
> <eClassifiers xsi:type="ecore:EClass" name="DataSetCheckAnnotation" abstract="true">
> <eStructuralFeatures xsi:type="ecore:EReference" name="checkedElement" eType="#//datasetchecking/ICheckableElement"
> eOpposite="#//datasetchecking/ICheckableElement/checkAnnotations "/>
> </eClassifiers>
> <eClassifiers xsi:type="ecore:EClass" name="ICheckableElement" abstract="true"
> interface="true" eSuperTypes="#//ICommonElement">
> <eAnnotations source="http://www.vsd-project.org/vsee/annotation/stereotype">
> <details key="name" value="Interface"/>
> </eAnnotations>
> <eStructuralFeatures xsi:type="ecore:EReference" name="checkAnnotations" upperBound="-1"
> eType="#//datasetchecking/DataSetCheckAnnotation" containment="true"
> eOpposite="#//datasetchecking/DataSetCheckAnnotation/checkedElement "/>
> </eClassifiers>
> </eSubpackages>
> <eSubpackages name="file" nsURI="http://www.vsd-project.org/vsd/file/1.0" nsPrefix="vsee.file">
> <eClassifiers xsi:type="ecore:EClass" name="EngineeringDataFile" eSuperTypes="#//ICommonElement
> #//datasetmerging/IMergeableElement #//datasetchecking/ICheckableElement">
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="description" unique="false"
> eType="#//String">
> <eAnnotations source="http://www.vsd-project.org/vsee/annotation/technical">
> <details key="isMultiLine" value="true"/>
> </eAnnotations>
> </eStructuralFeatures>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="category" unique="false"
> eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="MIMEType" unique="false"
> eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="author" unique="false"
> eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="date" unique="false"
> eType="#//Date"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="size" unique="false"
> eType="#//Integer" defaultValueLiteral="0"/>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="url" unique="false" eType="#//String"/>
> <eStructuralFeatures xsi:type="ecore:EReference" name="relatedItem" upperBound="-1"
> eType="#//EngineeringDataItem" eOpposite="#//EngineeringDataItem/relatedFile"/>
> </eClassifiers>
> <eClassifiers xsi:type="ecore:EClass" name="FileModel" eSuperTypes="#//ICommonElement
> #//datasetmerging/IMergeableElement #//datasetchecking/ICheckableElement">
> <eStructuralFeatures xsi:type="ecore:EReference" name="file" upperBound="-1"
> eType="#//file/EngineeringDataFile" containment="true"/>
> </eClassifiers>
> </eSubpackages>
> ...
>
>
> I have tested two cases in H2 database:
>
> The first case is when the relationship checkedElement is present:
>
> Since the table datasetcheckannotation has a foreign key with all tables that derive from classes implementing
> ICheckableElement (i.e. see FileModel above), this means that when a new row is inserted in datasetcheckannotation the
> value of the field datasetcheckannotation_checkedelement_unique_identifier has to be found in all tables,
> engineeringannotationitem, constraintmodel, filemodel, etc (and the list is veeery long). This is conceptually
> impossible, of course.
> The second case is when the relationship checkedElement is not present, removing the association from
> DatasetCheckAnnotation to ICheckablelement:
>
> In this case, the table datasetcheckannotation is provided with a lot of fields representing the relationship to each
> particular table implementing the ICheckableElement interface.
>
> The actual problem is the association between DataSetCheckAnnotation and ICheckableElement. For some reason, when this
> association is present Teneo chooses to change the implementation from several fields to only one field with lots of FKs.
>
> Thanks in advance.
>
> Fernando
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
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] Problem mapping an EMF relationship in Teneo [message #648296 is a reply to message #648208] Wed, 12 January 2011 10:15 Go to previous messageGo to next message
Fer Missing name is currently offline Fer Missing nameFriend
Messages: 24
Registered: September 2009
Junior Member
Dear Martin,

Thanks a lot for your answer.

> I guess that "#//datasetchecking/ICheckableElement/checkAnnotations" is a multiple ereference, this
> means that for this association the foreign key column has to be placced in the DataSetCheckAnnotation table, resulting
> in a column for each implementation of ICheckableElement.

You are right, "#//datasetchecking/ICheckableElement/checkAnnotations" is a 0-to-many association.

Actually, we are OK with having lots of fields in DataSetCheckAnnotation, instead of only one. Everything works fine. But we achieve this only when the association "#//datasetchecking/DataSetCheckAnnotation/checkedElement" does not exist.

Unfortunately that association is needed in the model, and if it is added then all the fields in the table collapse into one (we get the one join column in DataSetCheckAnnotation you refer to) and all our save operations fail due to the FKs.

Is there a way to avoid that all the fields collapse into one even if the association exists?

> You can
> override the column name by adding attribute override annotations to each subtype of ICheckableElement, but that's very
> tedious...

Sorry, I do not fully understand the effects of overriding the column name. But in any case the number of classes that implement ICheckableElement is big (around 60) and the model is changing (and therefore the generated Java classes), so doing this work manually could create a bottleneck for the development.

Note: The inheritance relationship between ICheckableElement and ICommonElement is optional. Removing it the problem still happens.

Any help is appreciated!

Thank you very much.

Fernando


Re: [Teneo] Problem mapping an EMF relationship in Teneo [message #648341 is a reply to message #648296] Wed, 12 January 2011 14:04 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Fernando,
One way is to override the column naming logic so it creates unique columns names for each owning eclass. See here:
http://wiki.eclipse.org/Teneo/Hibernate/Extensions#SqlNameSt rategy_ExtensionPoint_.28org.eclipse.emf.teneo.mapping.strat egy.SQLNameStrategy.29

But it can make sense to send me the complete ecore then I can debug to see what happens. To give better advice on what
can be done.

gr. Martin

On 01/12/2011 11:15 AM, Fer wrote:
> Dear Martin,
>
> Thanks a lot for your answer.
>
>> I guess that "#//datasetchecking/ICheckableElement/checkAnnotations" is a multiple ereference, this means that for
>> this association the foreign key column has to be placced in the DataSetCheckAnnotation table, resulting in a column
>> for each implementation of ICheckableElement.
>
> You are right, "#//datasetchecking/ICheckableElement/checkAnnotations" is a 0-to-many association.
>
> Actually, we are OK with having lots of fields in DataSetCheckAnnotation, instead of only one. Everything works fine.
> But we achieve this only when the association "#//datasetchecking/DataSetCheckAnnotation/checkedElement" does not exist.
>
> Unfortunately that association is needed in the model, and if it is added then all the fields in the table collapse into
> one (we get the one join column in DataSetCheckAnnotation you refer to) and all our save operations fail due to the FKs.
>
> Is there a way to avoid that all the fields collapse into one even if the association exists?
>
>> You can override the column name by adding attribute override annotations to each subtype of ICheckableElement, but
>> that's very tedious...
>
> Sorry, I do not fully understand the effects of overriding the column name. But in any case the number of classes that
> implement ICheckableElement is big (around 60) and the model is changing (and therefore the generated Java classes), so
> doing this work manually could create a bottleneck for the development.
>
> Note: The inheritance relationship between ICheckableElement and ICommonElement is optional. Removing it the problem
> still happens.
>
> Any help is appreciated!
>
> Thank you very much.
>
> Fernando
>
>
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
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] Problem mapping an EMF relationship in Teneo [message #648508 is a reply to message #648341] Thu, 13 January 2011 10:23 Go to previous messageGo to next message
Fer Missing name is currently offline Fer Missing nameFriend
Messages: 24
Registered: September 2009
Junior Member
Hi Martin,

I have tried using the ClassicSQLNameStrategy and TeneoNewSQLNameStrategy but no work. I always get the same error:

Quote:

2011-01-13 11:10:35 ERROR org.hibernate.util.JDBCExceptionReporter.logExceptions(234) ===> Violación de una restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?, "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
2011-01-13 11:10:35 WARN org.hibernate.util.JDBCExceptionReporter.logExceptions(233) ===> SQL Error: 23002, SQLState: 23002
2011-01-13 11:10:35 ERROR org.hibernate.util.JDBCExceptionReporter.logExceptions(234) ===> Violación de una restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?, "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
2011-01-13 11:10:35 ERROR org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(324) ===> Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateCo nverter.java:96)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExce ptionHelper.java:66)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:275)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:114)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:109)
at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(Abs tractBatcher.java:244)
at org.hibernate.persister.collection.AbstractCollectionPersist er.recreate(AbstractCollectionPersister.java:1179)
at org.hibernate.action.CollectionRecreateAction.execute(Collec tionRecreateAction.java:58)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:27 3)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:265)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:188)
at org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(De faultFlushEventListener.java:51)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1216)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java :383)
at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransac tion.java:133)
at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:145)
at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
Caused by: org.h2.jdbc.JdbcBatchUpdateException: Violación de una restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?, "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
at org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedS tatement.java:1098)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBa tcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:268)
... 22 more
2011-01-13 11:10:35 ERROR es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(148) ===> commitTransaction
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateCo nverter.java:96)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExce ptionHelper.java:66)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:275)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:114)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:109)
at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(Abs tractBatcher.java:244)
at org.hibernate.persister.collection.AbstractCollectionPersist er.recreate(AbstractCollectionPersister.java:1179)
at org.hibernate.action.CollectionRecreateAction.execute(Collec tionRecreateAction.java:58)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:27 3)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:265)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:188)
at org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(De faultFlushEventListener.java:51)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1216)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java :383)
at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransac tion.java:133)
at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:145)
at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
Caused by: org.h2.jdbc.JdbcBatchUpdateException: Violación de una restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?, "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
at org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedS tatement.java:1098)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBa tcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:268)
... 22 more
2011-01-13 11:10:35 ERROR es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(93) ===> save
es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:149)
at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
2011-01-13 11:10:35 INFO org.hibernate.impl.SessionFactoryImpl.close(925) ===> closing
2011-01-13 11:10:35 INFO org.hibernate.connection.DriverManagerConnectionProvider.clo se(170) ===> cleaning up connection pool: jdbc:h2:tcp://localhost/C:/SSRDB_database/br0ds01;CACHE_SIZE=262144;DEFAULT_LOCK_TIMEOUT=120000
2011-01-13 11:10:36 ERROR es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(1952) ===> commitDataSet
es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:99)
at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
2011-01-13 11:10:36 ERROR es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( 804) ===> commitDataSet
es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1953)
at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)



The ecore model is a little big and I can't to attach files in this message. Can I send the ecore file to your e-mail?


Best Regards,

Fernando
Re: [Teneo] Problem mapping an EMF relationship in Teneo [message #648516 is a reply to message #648508] Thu, 13 January 2011 10:46 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Fernando,
Yes you need to override the naming strategy with your own implementation, overriding the relevant method. But let me
first check the ecore model, you can send it here:
mtaal (at) elver.org

gr. Martin

On 01/13/2011 11:23 AM, Fer wrote:
> Hi Martin,
>
> I have tried using the ClassicSQLNameStrategy and TeneoNewSQLNameStrategy but no work. I always get the same error:
>
> Quote:
>> 2011-01-13 11:10:35 ERROR org.hibernate.util.JDBCExceptionReporter.logExceptions(234) ===> Violación de una
>> restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
>> Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
>> update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?,
>> "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
>> 2011-01-13 11:10:35 WARN org.hibernate.util.JDBCExceptionReporter.logExceptions(233) ===> SQL Error: 23002, SQLState:
>> 23002
>> 2011-01-13 11:10:35 ERROR org.hibernate.util.JDBCExceptionReporter.logExceptions(234) ===> Violación de una
>> restricción de Integridad Referencial: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
>> Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
>> update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?,
>> "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
>> 2011-01-13 11:10:35 ERROR org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(324) ===> Could not
>> synchronize database state with session
>> org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
>> at org.hibernate.exception.SQLStateConverter.convert(SQLStateCo nverter.java:96)
>> at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExce ptionHelper.java:66)
>> at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:275)
>> at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:114)
>> at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:109)
>> at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(Abs tractBatcher.java:244)
>> at org.hibernate.persister.collection.AbstractCollectionPersist er.recreate(AbstractCollectionPersister.java:1179)
>> at org.hibernate.action.CollectionRecreateAction.execute(Collec tionRecreateAction.java:58)
>> at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:27 3)
>> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:265)
>> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:188)
>> at org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(AbstractFlushingEventListener.java:321)
>> at org.hibernate.event.def.DefaultFlushEventListener.onFlush(De faultFlushEventListener.java:51)
>> at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1216)
>> at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java :383)
>> at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransac tion.java:133)
>> at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:145)
>> at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
>> at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
>> at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
>> at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
>> Caused by: org.h2.jdbc.JdbcBatchUpdateException: Violación de una restricción de Integridad Referencial:
>> "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"")
>> REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
>> Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
>> update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?,
>> "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
>> at org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedS tatement.java:1098)
>> at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBa tcher.java:70)
>> at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:268)
>> ... 22 more
>> 2011-01-13 11:10:35 ERROR es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(148) ===> commitTransaction
>> org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
>> at org.hibernate.exception.SQLStateConverter.convert(SQLStateCo nverter.java:96)
>> at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExce ptionHelper.java:66)
>> at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:275)
>> at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:114)
>> at org.hibernate.jdbc.AbstractBatcher.prepareStatement(Abstract Batcher.java:109)
>> at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(Abs tractBatcher.java:244)
>> at org.hibernate.persister.collection.AbstractCollectionPersist er.recreate(AbstractCollectionPersister.java:1179)
>> at org.hibernate.action.CollectionRecreateAction.execute(Collec tionRecreateAction.java:58)
>> at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:27 3)
>> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:265)
>> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue. java:188)
>> at org.hibernate.event.def.AbstractFlushingEventListener.perfor mExecutions(AbstractFlushingEventListener.java:321)
>> at org.hibernate.event.def.DefaultFlushEventListener.onFlush(De faultFlushEventListener.java:51)
>> at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1216)
>> at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java :383)
>> at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransac tion.java:133)
>> at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:145)
>> at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
>> at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
>> at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
>> at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
>> Caused by: org.h2.jdbc.JdbcBatchUpdateException: Violación de una restricción de Integridad Referencial:
>> "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN KEY(""datasetcheckannotation_checkedelement_e_id"")
>> REFERENCES PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"
>> Referential integrity constraint violation: "FKFFFAF2BF4CA4F96B: PUBLIC.""datasetcheckannotation"" FOREIGN
>> KEY(""datasetcheckannotation_checkedelement_e_id"") REFERENCES
>> PUBLIC.""constraintmodel""(""icommonelement_unique_identifier "")"; SQL statement:
>> update "datasetcheckannotation" set "datasetcheckannotation_checkedelement_e_id"=?,
>> "engineeringdataitem_checkannotations_idx"=? where e_id=? [23002-131]
>> at org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedS tatement.java:1098)
>> at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBa tcher.java:70)
>> at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatc her.java:268)
>> ... 22 more
>> 2011-01-13 11:10:35 ERROR es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(93) ===> save
>> es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
>> at es.gmv.vsd.ssrdb.common.dao.impl.GeneralDAO.commitTransactio n(GeneralDAO.java:149)
>> at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:88)
>> at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
>> at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
>> at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
>> 2011-01-13 11:10:35 INFO org.hibernate.impl.SessionFactoryImpl.close(925) ===> closing
>> 2011-01-13 11:10:35 INFO org.hibernate.connection.DriverManagerConnectionProvider.clo se(170) ===> cleaning up
>> connection pool: jdbc:h2:tcp://localhost/C:/SSRDB_database/br0ds01;CACHE_SIZE=262144;DEFAULT_LOCK_TIMEOUT=120000
>> 2011-01-13 11:10:36 ERROR es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(1952) ===>
>> commitDataSet es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
>> at es.gmv.vsd.ssrdb.common.dao.impl.ds.DataSetVSEEDAO.save(Data SetVSEEDAO.java:99)
>> at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1943)
>> at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
>> at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
>> 2011-01-13 11:10:36 ERROR es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( 804) ===> commitDataSet
>> es.gmv.vsd.ssrdb.exception.impl.SSRDBException: Could not execute JDBC batch update
>> at es.gmv.vsd.ssrdb.common.dao.impl.cm.ConfigManagementDAO.comm itDataSet(ConfigManagementDAO.java:1953)
>> at es.gmv.vsd.ssrdb.cm.impl.ConfigManagementImpl.commitDataSet( ConfigManagementImpl.java:787)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:51)
>> at es.gmv.vsd.ssrdb.check.facade.impl.CheckFacadeImpl.runConsis tencyChecks(CheckFacadeImpl.java:1)
>> at es.gmv.vsd.ssrdb.auditing.impl.AuditingImpl.runChecks(Auditi ngImpl.java:53)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.executeMethod(ManagerI mpl.java:496)
>> at es.gmv.vsd.ssrdb.mmi.impl.ManagerImpl.run(ManagerImpl.java:1 25)
>
>
> The ecore model is a little big and I can't to attach files in this message. Can I send the ecore file to your e-mail?
>
>
> Best Regards,
>
> Fernando


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
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] Problem mapping an EMF relationship in Teneo [message #662330 is a reply to message #648516] Wed, 30 March 2011 09:25 Go to previous messageGo to next message
Fer Missing name is currently offline Fer Missing nameFriend
Messages: 24
Registered: September 2009
Junior Member
Dear Martin,

Do you have any news about this topic? We have not been able to solve this problem yet.

Thank you very much.

Best Regards,

Fernando
Re: [Teneo] Problem mapping an EMF relationship in Teneo [message #662580 is a reply to message #662330] Thu, 31 March 2011 08:30 Go to previous message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Fer,
No not yet, been very busy and had hoped that this problem had disappeared (but they never do...).

Will check it early next week. Just send me emails directly if you want to get an update or remind me (I am quite
overloaded, so just bug me that really helps.. :-).

gr. Martin

On 03/30/2011 11:25 AM, Fer wrote:
> Dear Martin,
>
> Do you have any news about this topic? We have not been able to solve this problem yet.
>
> Thank you very much.
>
> Best Regards,
>
> Fernando
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
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
Previous Topic:How to integrate a new metamodel in EMF ?
Next Topic:Loading XML with a schema that extends via substitutionGroup
Goto Forum:
  


Current Time: Sat Oct 19 17:53:04 GMT 2019

Powered by FUDForum. Page generated in 0.01869 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top