Eclipse Community Forums: EMF » [CDO] Exception on commit

Home » Modeling » EMF » [CDO] Exception on commit

[CDO] Exception on commit [message #502807]

Wed, 09 December 2009 13:42

Eclipse User

Hi,

I am playing with the CDO Server. I have loaded some packages which are a *very* early cut of our model and it is really not complete or stable, so I expect to have issues. I was not expecting the exception below however. I expect that the exception is being thrown because one or more of the references that are marked as required="true" are not set. Does that sound logical? If so, how does one go about debugging these issues as there is no indication of the real issue? If not, what is likely to be causing the problem?

Btw, I can commit some objects, i.e. certain classes, to the repository, so it is not a general issue.

I am using 3.5 SR1.

Cheers,
Joel

[ERROR] NullPointerException
java.lang.NullPointerException
	at org.eclipse.emf.cdo.common.model.CDOClassifierRef.<init>(CDOClassifierRef.java:53)
	at org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.readCDOClassifierRef(CDODataInputImpl.java:129)
	at org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.readCDOClassifierRefAndResolve(CDODataInputImpl.java:134)
	at org.eclipse.emf.cdo.internal.common.revision.delta.CDORevisionDeltaImpl.<init>(CDORevisionDeltaImpl.java:102)
	at org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.readCDORevisionDelta(CDODataInputImpl.java:295)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicatingCommit(CommitTransactionIndication.java:301)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicating(CommitTransactionIndication.java:197)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicating(CommitTransactionIndication.java:140)
	at org.eclipse.net4j.signal.IndicationWithMonitoring.indicating(IndicationWithMonitoring.java:84)
	at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedInput(IndicationWithResponse.java:90)
	at org.eclipse.net4j.signal.Signal.doInput(Signal.java:312)
	at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:63)
	at org.eclipse.net4j.signal.IndicationWithMonitoring.execute(IndicationWithMonitoring.java:63)
	at org.eclipse.net4j.signal.Signal.runSync(Signal.java:239)
	at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)

Re: [CDO] Exception on commit [message #502826 is a reply to message #502807]

Wed, 09 December 2009 14:52

Eclipse User

Hi Joel,

I will assume you are using CDO 2.0.0, as you pointed that you are using
Eclipse 3.5 SR1.

Is this exception systematically reproducible? From what I understand
from your words, it seems to be happening every time your commit an
instance of certain EClass, right? Could you provide a better
description of that class? If its not possible you to share that model,
could you come out with a dummy model that at least resembles the
problematic one?

By looking at the code, it seems CDOClassifierRef could not retrieve the
URI for the EPackage of the problematic EClass (a null value is
returned instead) and therefore, while manipulating that URI, the NPE is
thrown.

Some quick questions (just to get to know a bit more about your use-case
scenario):

- Have you generated your models code? If so, is it "cdo-aware"?
(extends CDOObjectImpl)
- Do you have your namespace URIs properly defined (not empty)? Are the
referenced EClasses under the same EPackage or different EPackage?

Not sure what might be causing this, but I'll try to reproduce it with
our test models and see if it's really related with the "required"
attribute.

Cheers,
Víctor.

Joel Rosi-Schwartz escribió:
> Hi,
>
> I am playing with the CDO Server. I have loaded some packages which are
> a *very* early cut of our model and it is really not complete or stable,
> so I expect to have issues. I was not expecting the exception below
> however. I expect that the exception is being thrown because one or more
> of the references that are marked as required="true" are not set. Does
> that sound logical? If so, how does one go about debugging these issues
> as there is no indication of the real issue? If not, what is likely to
> be causing the problem?
>
> Btw, I can commit some objects, i.e. certain classes, to the repository,
> so it is not a general issue.
> I am using 3.5 SR1.
>
> Cheers,
> Joel
>
>
>
> [ERROR] NullPointerException
> java.lang.NullPointerException
> at
> org.eclipse.emf.cdo.common.model.CDOClassifierRef.<init>(CDOClassifierRef.java:53)
>
> at
> org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.read CDOClassifierRef(CDODataInputImpl.java:129)
>
> at
> org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.read CDOClassifierRefAndResolve(CDODataInputImpl.java:134)
>
> at
> org.eclipse.emf.cdo.internal.common.revision.delta.CDORevisi onDeltaImpl. <init>(CDORevisionDeltaImpl.java:102)
>
> at
> org.eclipse.emf.cdo.internal.common.io.CDODataInputImpl.read CDORevisionDelta(CDODataInputImpl.java:295)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:301)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:197 )
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:140 )
>
> at
> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:84)
>
> at
> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:312)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>
> at
> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
>
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:239)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:637)
>

Re: [CDO] Exception on commit [message #502835 is a reply to message #502826]

Wed, 09 December 2009 15:49

Eclipse User

        https://dev.eclipse.org/svnroot/technology/org.eclipse.ormf/trunk/design/org.eclipse.ormf.design.model

To reproduce:

1. start a transaction
2. create a resource
3. add a Project at the root
4. add a Folder as child to the Project
5. save the resource

As I said in the original message, the model is really not ready for this. I had it in my workspace when I brought up my first CDO server, so I figured I would give it whirl.

>> By looking at the code, it seems CDOClassifierRef could not retrieve the
>> URI for the EPackage of the problematic EClass (a null value is
>> returned instead) and therefore, while manipulating that URI, the NPE is
>> thrown.

>> Some quick questions (just to get to know a bit more about your use-case
>> scenario):

>> - Have you generated your models code? If so, is it "cdo-aware"?
>> (extends CDOObjectImpl)
>> - Do you have your namespace URIs properly defined (not empty)? Are the
>> referenced EClasses under the same EPackage or different EPackage?

Yes everything is being generated fresh as CDO aware objects. I think I have the EMF correct, but you can see when you checkout the project. In the example above the EClasses are both in the same EPackage. I do have four packages though in the model.

>> Not sure what might be causing this, but I'll try to reproduce it with
>> our test models and see if it's really related with the "required"
>> attribute.

Many thanks for the assistance,
Joel

Re: [CDO] Exception on commit [message #502853 is a reply to message #502826]

Wed, 09 December 2009 18:27

Eclipse User

Hi Victor,

>> I will assume you are using CDO 2.0.0, as you pointed that you are using
>> Eclipse 3.5 SR1.

Yes that is correct.

>> Is this exception systematically reproducible? From what I understand
>> from your words, it seems to be happening every time your commit an
>> instance of certain EClass, right? Could you provide a better
>> description of that class? If its not possible you to share that model,
>> could you come out with a dummy model that at least resembles the
>> problematic one?

Yes it is reproducible 100%.

Yes it is on certain classes only and always on these. So far it appears to be any Class with a reference, but this is has not been tested thoroughly yet.

You can check out the entire model from the ORMF Eclipse project SVN repository at:

https://dev.eclipse.org/svnroot/technology/org.eclipse.ormf/ trunk/design/org.eclipse.ormf.design.model

To reproduce:

- start session
- register packages from project
- start a transaction
- create a resource
- add a Project at the root
- add a Folder as child to the Project
- save the resource

As I said in the original message, the model is really not ready for this. I had it in my workspace when I brought up my first CDO server, so I figured I would give it whirl.

>> By looking at the code, it seems CDOClassifierRef could not retrieve the
>> URI for the EPackage of the problematic EClass (a null value is
>> returned instead) and therefore, while manipulating that URI, the NPE is
>> thrown.

>> Some quick questions (just to get to know a bit more about your use-case
>> scenario):

>> - Have you generated your models code? If so, is it "cdo-aware"?
>> (extends CDOObjectImpl)
>> - Do you have your namespace URIs properly defined (not empty)? Are the
>> referenced EClasses under the same EPackage or different EPackage?

Yes everything is being generated fresh as CDO aware objects. I think I have the EMF correct, but you can see when you checkout the project. In the example above the EClasses are both in the same EPackage. I do have four packages though in the model.

>> Not sure what might be causing this, but I'll try to reproduce it with
>> our test models and see if it's really related with the "required"
>> attribute.

I have noticed that there are no member fields generated. I assume (from looking at the code) that is because CDO does everything dynamically. Is this correct?

Many thanks for the assistance,
Joel

[Updated on: Wed, 09 December 2009 18:31] by Moderator

Re: [CDO] Exception on commit [message #502901 is a reply to message #502835]

Thu, 10 December 2009 03:18

Eclipse User

Hi Joel and Vik,

I could eventually imagine a problem in CDO with committing objects from
multiple new packages at once (forward references). But I'd really
prefer to dig down into CDO only if the used packages *all* validate
successfully. Can you please ensure this first?

If we can reproduce the problem in 2.0 we should do that in 3.0, too,
because I vaguely remember that we did something regarding commits of
multiple packages. I can not remember anymore when this took place, though.

In either case Joel should file a bugzilla.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> Hi Victor,
>
>>> I will assume you are using CDO 2.0.0, as you pointed that you are
>>> using Eclipse 3.5 SR1.
>
> Yes that is correct.
>
>>> Is this exception systematically reproducible? From what I
>>> understand from your words, it seems to be happening every time your
>>> commit an instance of certain EClass, right? Could you provide a
>>> better description of that class? If its not possible you to share
>>> that model, could you come out with a dummy model that at least
>>> resembles the problematic one?
>
> Yes it is reproducible 100%.
>
> Yes it is on certain classes only and always on these. So far it
> appears to be any Class with a reference, but this is has not been
> tested thoroughly yet.
>
> You can check out the entire model from the ORMF Eclipse project SVN
> repository at:
>
> https://dev.eclipse.org/svnroot/technology/org.eclipse.ormf/ trunk/design/org.eclipse.ormf.design.model
>
>
>
> To reproduce:
>
> 1. start a transaction
> 2. create a resource
> 3. add a Project at the root
> 4. add a Folder as child to the Project
> 5. save the resource
>
> As I said in the original message, the model is really not ready for
> this. I had it in my workspace when I brought up my first CDO server,
> so I figured I would give it whirl.
>
>>> By looking at the code, it seems CDOClassifierRef could not retrieve
>>> the URI for the EPackage of the problematic EClass (a null value
>>> is returned instead) and therefore, while manipulating that URI, the
>>> NPE is thrown.
>
>>> Some quick questions (just to get to know a bit more about your
>>> use-case scenario):
>
>>> - Have you generated your models code? If so, is it "cdo-aware"?
>>> (extends CDOObjectImpl)
>>> - Do you have your namespace URIs properly defined (not empty)? Are
>>> the referenced EClasses under the same EPackage or different EPackage?
>
> Yes everything is being generated fresh as CDO aware objects. I think
> I have the EMF correct, but you can see when you checkout the project.
> In the example above the EClasses are both in the same EPackage. I do
> have four packages though in the model.
>
>>> Not sure what might be causing this, but I'll try to reproduce it
>>> with our test models and see if it's really related with the
>>> "required" attribute.
>
> Many thanks for the assistance,
> Joel
>

Re: [CDO] Exception on commit [message #502911 is a reply to message #502901]

Thu, 10 December 2009 04:56

Eclipse User

Hi Eike,

This morning I decided to move over to the standard Extended Library (org.eclipse.emf.examples.library) example. I was very surprised to find that an exception is still being thrown when I commit a transaction, see below. The exception is quite different, but all the same I am concerned that I am doing something aberrant to cause these problem, but I do not see what that could be.

Before I file a Bugzilla can we do a sanity check on what I am doing please.

I have an out of the box eclipse-modeling-galileo-SR1
OS X 10.6.2
Java 6
checked out org.eclipse.emf.cdo.server.product from the CDO repository
started with a standard EMF model, mine and then the extended library
used the CDO Migration tool to convert the Genmodel for CDO
generated new model source using the genmodel
launched the CDO server
opened a CDO session
loaded the workspace packages
created a resource
committed the new resource
add a new root object (either my Project or the Library)
committed the new root
got exception

Is there anything I have forgotten to do?

Cheers,
Joel

[ERROR] Unrecognized CDOType: FEATURE_MAP_ENTRY
org.eclipse.net4j.util.ImplementationError: Unrecognized CDOType: FEATURE_MAP_ENTRY
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.createValueMapping(AbstractMappingStrategy.java:451)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractListTableMapping.initTable(AbstractListTableMapping.java:117)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractListTableMapping.<init>(AbstractListTableMapping.java:95)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AuditListTableMapping.<init>(AuditListTableMapping.java:42)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.HorizontalAuditMappingStrategy.doCreateListMapping(HorizontalAuditMappingStrategy.java:35)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.createListMapping(AbstractMappingStrategy.java:457)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractHorizontalClassMapping.createListMappings(AbstractHorizontalClassMapping.java:133)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractHorizontalClassMapping.initFeatures(AbstractHorizontalClassMapping.java:106)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractHorizontalClassMapping.<init>(AbstractHorizontalClassMapping.java:74)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.HorizontalAuditClassMapping.<init>(HorizontalAuditClassMapping.java:63)
	at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.HorizontalAuditMappingStrategy.doCreateClassMapping(HorizontalAuditMappingStrategy.java:29)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.createClassMapping(AbstractMappingStrategy.java:355)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.mapClasses(AbstractMappingStrategy.java:325)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.mapPackageInfos(AbstractMappingStrategy.java:314)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.mapPackageUnits(AbstractMappingStrategy.java:336)
	at org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappingStrategy.createMapping(AbstractMappingStrategy.java:297)
	at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.writePackageUnits(DBStoreAccessor.java:496)
	at org.eclipse.emf.cdo.spi.server.StoreAccessor.write(StoreAccessor.java:129)
	at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.access$4(DBStoreAccessor.java:1)
	at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.runLoop(DBStoreAccessor.java:80)
	at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.runLoop(DBStoreAccessor.java:1)
	at org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(ProgressDistributor.java:96)
	at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write(DBStoreAccessor.java:294)
	at org.eclipse.emf.cdo.internal.server.TransactionCommitContextImpl.write(TransactionCommitContextImpl.java:269)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication$1.runLoop(CommitTransactionIndication.java:73)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication$1.runLoop(CommitTransactionIndication.java:1)
	at org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(ProgressDistributor.java:96)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicatingCommit(CommitTransactionIndication.java:325)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicating(CommitTransactionIndication.java:198)
	at org.eclipse.emf.cdo.internal.server.protocol.CommitTransactionIndication.indicating(CommitTransactionIndication.java:140)
	at org.eclipse.net4j.signal.IndicationWithMonitoring.indicating(IndicationWithMonitoring.java:84)
	at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedInput(IndicationWithResponse.java:90)
	at org.eclipse.net4j.signal.Signal.doInput(Signal.java:312)
	at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:63)
	at org.eclipse.net4j.signal.IndicationWithMonitoring.execute(IndicationWithMonitoring.java:63)
	at org.eclipse.net4j.signal.Signal.runSync(Signal.java:239)
	at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)

Eike Stepper wrote on Thu, 10 December 2009 08:18

[Updated on: Thu, 10 December 2009 05:02] by Moderator

Re: [CDO] Exception on commit [message #502922 is a reply to message #502911]

Thu, 10 December 2009 05:33

Eclipse User

Hi Joel,

Comments below...

Joel Rosi-Schwartz schrieb:
> Hi Eike,
>
> This morning I decided to move over to the standard Extended Library
> (org.eclipse.emf.examples.library) example.
This example is not expected to work with CDO out of the box. There are
some @generated NOT annotations that prevent the needed CDO code to be
generated. Please try the examples in CDO (test models in 2.0,
examples.company in 3.0)

> I was very surprised to find that an exception is still being thrown
> when I commit a transaction, see below.
Yes, the library example employs feature maps and I'm currently unsure
if they really work well in CDO 2.0. We fixed a lot about them in CDO
3.0. Just for getting more information, could you test your setup with
CDO 3.0? Other users reported that it works quite well with Platform 3.5.

> The exception is quite different, but all the same I am concerned that
> I am doing something aberrant to cause these problem, but I do not see
> what that could be.
>
> Before I file a Bugzilla can we do a sanity check on what I am doing
> please.
>
>
> I have an out of the box eclipse-modeling-galileo-SR1
> OS X 10.6.2
> Java 6
> checked out org.eclipse.emf.cdo.server.product from the CDO repository
> started with a standard EMF model, mine and then the extended library
> used the CDO Migration tool to convert the Genmodel for CDO
> generated new model source using the genmodel
> launched the CDO server
> opened a CDO session
> loaded the workspace packages
What does "loaded" mean?

> created a resource
> committed the new resouce
> add a new root object (either my Project or the Library) committed the
> new root
> got exception
>
>
> Is there anything I have forgotten to do?
Nothing obvious. I suspect that the feature map bugs have not been fixed
in 2.0 since that required significant change in some APIs.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

>
> Cheers,
> Joel
>
>
> [ERROR] Unrecognized CDOType: FEATURE_MAP_ENTRY
> org.eclipse.net4j.util.ImplementationError: Unrecognized CDOType:
> FEATURE_MAP_ENTRY
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createValueMapping(AbstractMappingStrategy.java:4 51)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractListTableMapping.initTable(AbstractListTableMapping.ja va:117)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractListTableMapping. <init>(AbstractListTableMapping.java:95)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Au ditListTableMapping. <init>(AuditListTableMapping.java:42)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditMappingStrategy.doCreateListMapping(HorizontalA uditMappingStrategy.java:35)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createListMapping(AbstractMappingStrategy.java:45 7)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping.createListMappings(AbstractHori zontalClassMapping.java:133)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping.initFeatures(AbstractHorizontal ClassMapping.java:106)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping. <init>(AbstractHorizontalClassMapping.java:74)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditClassMapping. <init>(HorizontalAuditClassMapping.java:63)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditMappingStrategy.doCreateClassMapping(Horizontal AuditMappingStrategy.java:29)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createClassMapping(AbstractMappingStrategy.java:3 55)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapClasses(AbstractMappingStrategy.java:325)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapPackageInfos(AbstractMappingStrategy.java:314)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapPackageUnits(AbstractMappingStrategy.java:336)
>
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createMapping(AbstractMappingStrategy.java:297)
>
> at
> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write PackageUnits(DBStoreAccessor.java:496)
>
> at
> org.eclipse.emf.cdo.spi.server.StoreAccessor.write(StoreAcce ssor.java:129)
>
> at
> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.acces s$4(DBStoreAccessor.java:1)
>
> at
> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.run Loop(DBStoreAccessor.java:80)
>
> at
> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.run Loop(DBStoreAccessor.java:1)
>
> at
> org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(Pr ogressDistributor.java:96)
>
> at
> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:294)
>
> at
> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:269)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication$1.runLoop(CommitTransactionIndication.java:73)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication$1.runLoop(CommitTransactionIndication.java:1)
>
> at
> org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(Pr ogressDistributor.java:96)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:325)
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:198 )
>
> at
> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:140 )
>
> at
> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:84)
>
> at
> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:312)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>
> at
> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
>
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:239)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:637)
>
>
>
>
> Eike Stepper wrote on Thu, 10 December 2009 08:18
>> Hi Joel and Vik,
>>
>> I could eventually imagine a problem in CDO with committing objects
>> from multiple new packages at once (forward references). But I'd
>> really prefer to dig down into CDO only if the used packages *all*
>> validate successfully. Can you please ensure this first?
>>
>> If we can reproduce the problem in 2.0 we should do that in 3.0, too,
>> because I vaguely remember that we did something regarding commits of
>> multiple packages. I can not remember anymore when this took place,
>> though.
>>
>> In either case Joel should file a bugzilla.
>>
>> Cheers
>> /Eike
>> >
>
>

Re: [CDO] Exception on commit [message #502931 is a reply to message #502922]

Thu, 10 December 2009 06:05

Eclipse User

Hi,

My plan is to create a simple multi-package example that is complete and which reproduces the exception. When I accomplish that I will file a Bugzilla against it.

Comments below...

Eike Stepper wrote on Thu, 10 December 2009 10:33

Okay. That makes me feel better. I will check out the CDO examples.

Quote:

> I was very surprised to find that an exception is still being thrown
> when I commit a transaction, see below.
Yes, the library example employs feature maps and I'm currently unsure
if they really work well in CDO 2.0. We fixed a lot about them in CDO
3.0. Just for getting more information, could you test your setup with
CDO 3.0? Other users reported that it works quite well with Platform 3.5.

First I want to get something simple running in 2.0. Then I will give 3.0 a go.

Quote:

> opened a CDO session
> loaded the workspace packages
What does "loaded" mean?

Re: [CDO] Exception on commit [message #502936 is a reply to message #502922]

Thu, 10 December 2009 06:18

Eclipse User

Eike, Joel,

FeatureMaps was committed to 2.0 maintenance branch on the 25 of September.

According to:

http://www.eclipse.org/eclipse/development/plans/freeze_plan _3_5_1.php

Galileo SR1 was released before 25 of September, so this feature is
probably no included.

Theoretically, FeatureMaps is working, according to our test-cases.

The fixed bug:

289360: [DB] Support FeatureMaps
https://bugs.eclipse.org/bugs/show_bug.cgi?id=289360

Joel, you might try to download all the CDO sources from the
R2_0_maintenance branch and see whether this feature is working or not.

Cheers,
Víctor.

Eike Stepper escribió:
> Hi Joel,
>
> Comments below...
>
>
> Joel Rosi-Schwartz schrieb:
>> Hi Eike,
>>
>> This morning I decided to move over to the standard Extended Library
>> (org.eclipse.emf.examples.library) example.
> This example is not expected to work with CDO out of the box. There are
> some @generated NOT annotations that prevent the needed CDO code to be
> generated. Please try the examples in CDO (test models in 2.0,
> examples.company in 3.0)
>
>> I was very surprised to find that an exception is still being thrown
>> when I commit a transaction, see below.
> Yes, the library example employs feature maps and I'm currently unsure
> if they really work well in CDO 2.0. We fixed a lot about them in CDO
> 3.0. Just for getting more information, could you test your setup with
> CDO 3.0? Other users reported that it works quite well with Platform 3.5.
>
>> The exception is quite different, but all the same I am concerned that
>> I am doing something aberrant to cause these problem, but I do not see
>> what that could be.
>>
>> Before I file a Bugzilla can we do a sanity check on what I am doing
>> please.
>>
>>
>> I have an out of the box eclipse-modeling-galileo-SR1
>> OS X 10.6.2
>> Java 6
>> checked out org.eclipse.emf.cdo.server.product from the CDO repository
>> started with a standard EMF model, mine and then the extended library
>> used the CDO Migration tool to convert the Genmodel for CDO
>> generated new model source using the genmodel
>> launched the CDO server
>> opened a CDO session
>> loaded the workspace packages
> What does "loaded" mean?
>
>> created a resource
>> committed the new resouce
>> add a new root object (either my Project or the Library) committed the
>> new root
>> got exception
>>
>>
>> Is there anything I have forgotten to do?
> Nothing obvious. I suspect that the feature map bugs have not been fixed
> in 2.0 since that required significant change in some APIs.
>
> Cheers
> /Eike
>
> ----
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>>
>> Cheers,
>> Joel
>>
>>
>> [ERROR] Unrecognized CDOType: FEATURE_MAP_ENTRY
>> org.eclipse.net4j.util.ImplementationError: Unrecognized CDOType:
>> FEATURE_MAP_ENTRY
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createValueMapping(AbstractMappingStrategy.java:4 51)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractListTableMapping.initTable(AbstractListTableMapping.ja va:117)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractListTableMapping. <init>(AbstractListTableMapping.java:95)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Au ditListTableMapping. <init>(AuditListTableMapping.java:42)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditMappingStrategy.doCreateListMapping(HorizontalA uditMappingStrategy.java:35)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createListMapping(AbstractMappingStrategy.java:45 7)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping.createListMappings(AbstractHori zontalClassMapping.java:133)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping.initFeatures(AbstractHorizontal ClassMapping.java:106)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ab stractHorizontalClassMapping. <init>(AbstractHorizontalClassMapping.java:74)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditClassMapping. <init>(HorizontalAuditClassMapping.java:63)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.Ho rizontalAuditMappingStrategy.doCreateClassMapping(Horizontal AuditMappingStrategy.java:29)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createClassMapping(AbstractMappingStrategy.java:3 55)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapClasses(AbstractMappingStrategy.java:325)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapPackageInfos(AbstractMappingStrategy.java:314)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.mapPackageUnits(AbstractMappingStrategy.java:336)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.mapping.AbstractMappi ngStrategy.createMapping(AbstractMappingStrategy.java:297)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write PackageUnits(DBStoreAccessor.java:496)
>>
>> at
>> org.eclipse.emf.cdo.spi.server.StoreAccessor.write(StoreAcce ssor.java:129)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.acces s$4(DBStoreAccessor.java:1)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.run Loop(DBStoreAccessor.java:80)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor$1.run Loop(DBStoreAccessor.java:1)
>>
>> at
>> org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(Pr ogressDistributor.java:96)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:294)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:269)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication$1.runLoop(CommitTransactionIndication.java:73)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication$1.runLoop(CommitTransactionIndication.java:1)
>>
>> at
>> org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(Pr ogressDistributor.java:96)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:325)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:198 )
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:140 )
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:84)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>>
>> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:312)
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
>>
>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:239)
>> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
>>
>> at java.lang.Thread.run(Thread.java:637)
>>
>>
>>
>>
>> Eike Stepper wrote on Thu, 10 December 2009 08:18
>>> Hi Joel and Vik,
>>>
>>> I could eventually imagine a problem in CDO with committing objects
>>> from multiple new packages at once (forward references). But I'd
>>> really prefer to dig down into CDO only if the used packages *all*
>>> validate successfully. Can you please ensure this first?
>>>
>>> If we can reproduce the problem in 2.0 we should do that in 3.0, too,
>>> because I vaguely remember that we did something regarding commits of
>>> multiple packages. I can not remember anymore when this took place,
>>> though.
>>>
>>> In either case Joel should file a bugzilla.
>>>
>>> Cheers
>>> /Eike
>>> >
>>
>>

Re: [CDO] Exception on commit [message #502963 is a reply to message #502936]

Thu, 10 December 2009 08:05

Eclipse User

Thanks for that Victor it is good to know as I may well have need for FeatureMaps in our model. However for now it is a bit tangential to my main concern which is to ascertain why my model does not commit without exception.

Cheers,
Joel

Victor Roldan Betancort wrote on Thu, 10 December 2009 11:18

Re: [CDO] Exception on commit [message #502976 is a reply to message #502901]

Thu, 10 December 2009 08:46

Eclipse User

Eike,

I've fetched ORMF's model and it seems to validate correctly.

Our model2 test model has EClasses with references to model1... Do we
have test-cases using it?

Eike Stepper escribió:
> Hi Joel and Vik,
>
> I could eventually imagine a problem in CDO with committing objects from
> multiple new packages at once (forward references). But I'd really
> prefer to dig down into CDO only if the used packages *all* validate
> successfully. Can you please ensure this first?
>
> If we can reproduce the problem in 2.0 we should do that in 3.0, too,
> because I vaguely remember that we did something regarding commits of
> multiple packages. I can not remember anymore when this took place, though.
>
> In either case Joel should file a bugzilla.
>
> Cheers
> /Eike
>
> ----
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
> Joel Rosi-Schwartz schrieb:
>> Hi Victor,
>>
>>>> I will assume you are using CDO 2.0.0, as you pointed that you are
>>>> using Eclipse 3.5 SR1.
>>
>> Yes that is correct.
>>
>>>> Is this exception systematically reproducible? From what I
>>>> understand from your words, it seems to be happening every time your
>>>> commit an instance of certain EClass, right? Could you provide a
>>>> better description of that class? If its not possible you to share
>>>> that model, could you come out with a dummy model that at least
>>>> resembles the problematic one?
>>
>> Yes it is reproducible 100%.
>>
>> Yes it is on certain classes only and always on these. So far it
>> appears to be any Class with a reference, but this is has not been
>> tested thoroughly yet.
>>
>> You can check out the entire model from the ORMF Eclipse project SVN
>> repository at:
>>
>> https://dev.eclipse.org/svnroot/technology/org.eclipse.ormf/ trunk/design/org.eclipse.ormf.design.model
>>
>>
>>
>> To reproduce:
>>
>> 1. start a transaction
>> 2. create a resource
>> 3. add a Project at the root
>> 4. add a Folder as child to the Project
>> 5. save the resource
>>
>> As I said in the original message, the model is really not ready for
>> this. I had it in my workspace when I brought up my first CDO server,
>> so I figured I would give it whirl.
>>
>>>> By looking at the code, it seems CDOClassifierRef could not retrieve
>>>> the URI for the EPackage of the problematic EClass (a null value
>>>> is returned instead) and therefore, while manipulating that URI, the
>>>> NPE is thrown.
>>
>>>> Some quick questions (just to get to know a bit more about your
>>>> use-case scenario):
>>
>>>> - Have you generated your models code? If so, is it "cdo-aware"?
>>>> (extends CDOObjectImpl)
>>>> - Do you have your namespace URIs properly defined (not empty)? Are
>>>> the referenced EClasses under the same EPackage or different EPackage?
>>
>> Yes everything is being generated fresh as CDO aware objects. I think
>> I have the EMF correct, but you can see when you checkout the project.
>> In the example above the EClasses are both in the same EPackage. I do
>> have four packages though in the model.
>>
>>>> Not sure what might be causing this, but I'll try to reproduce it
>>>> with our test models and see if it's really related with the
>>>> "required" attribute.
>>
>> Many thanks for the assistance,
>> Joel
>>

Re: [CDO] Exception on commit [message #502980 is a reply to message #502922]

Thu, 10 December 2009 09:14

Eclipse User

I have checked out the test models from the CDO CVS repository. Problems is that the HEAD have all been converted to 3.0 dependencies and there do not seem to be any Branches or Versions available in the anonymous version of the Modeling repository. Recall that recently Matt spit out all of the anonymous repositories to snapshots in order to improve performance. I do not know if this is a general issue or Modeling specific that historical checkouts are not available. Are you aware of this or should I send a note off to Matt?

Eike Stepper wrote on Thu, 10 December 2009 10:33

> This morning I decided to move over to the standard Extended Library
> (org.eclipse.emf.examples.library) example.
This example is not expected to work with CDO out of the box. There are
some @generated NOT annotations that prevent the needed CDO code to be
generated. Please try the examples in CDO (test models in 2.0,
examples.company in 3.0)

>

[Updated on: Thu, 10 December 2009 09:15] by Moderator

Re: [CDO] Exception on commit [message #502985 is a reply to message #502980]

Thu, 10 December 2009 09:18

Eclipse User

Joel,

I had the same problems while fetching R2_0_maintenance sources once.
I believe you can download HEAD sources and then perform a "Switch to
another Branch or Version" action. Then you select the "Select the tag
from the following list" option and then refresh the "Branches"
category, the R2_0_maintenance branch shall appear there.

Hope it helps,
Víctor.

Joel Rosi-Schwartz escribió:
> I have checked out the test models from the CDO CVS repository. Problems
> is that the HEAD have all been converted to 3.0 dependencies and there
> do not seem to be any Branches or Versions available in the anonymous
> version of the Modeling repository. Recall the recently Matt spit out
> all of the anonymous repositories to snapshots in order to improve
> performance. I do not know if this is a general issue or Modeling
> specific that historical checkouts are not available. Are you aware of
> this or should I send a note off to Matt?
>
>
> Eike Stepper wrote on Thu, 10 December 2009 10:33
>> > This morning I decided to move over to the standard Extended Library
>> > (org.eclipse.emf.examples.library) example. This example is not
>> expected to work with CDO out of the box. There are some @generated
>> NOT annotations that prevent the needed CDO code to be generated.
>> Please try the examples in CDO (test models in 2.0, examples.company
>> in 3.0)
>>
>> >
>
>

Re: [CDO] Exception on commit [message #502996 is a reply to message #502985]

Thu, 10 December 2009 09:39

Eclipse User

This appears to have worked, but I am not sure it actually does work. Even though I have switched to the Root_R2_0_maintenance (Version), the Manifest still indicates bundle-version="[3.0.0,4.0.0)" for the CDO plugins. So is this CVS acting up or has your R2_0_maintenance converted to 3.0 bundles accidentally?

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-SymbolicName: org.eclipse.emf.cdo.tests;singleton:=true
Bundle-Version: 3.0.0.qualifier
Bundle-Name: %pluginName
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Bundle-ActivationPolicy: lazy
Bundle-Activator: org.eclipse.emf.cdo.tests.bundle.OM$Activator
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Bundle-ClassPath: .
Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.4.0,4.0.0)",
 org.eclipse.emf.ecore.xmi;bundle-version="[2.4.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.jvm;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.net4j.tcp;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.common;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.server;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.mango;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model1;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model2;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model3;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model4;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model4interfaces;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.tests.model5;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.defs;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
 org.junit;bundle-version="[3.8.0,4.0.0)";visibility:=reexport
Export-Package: base;version="3.0.0",
 base.impl;version="3.0.0",
 base.util;version="3.0.0",
 derived;version="3.0.0",
 derived.impl;version="3.0.0",
 derived.util;version="3.0.0",
 interface_;version="3.0.0",
 interface_.impl;version="3.0.0",
 interface_.util;version="3.0.0",
 org.eclipse.emf.cdo.tests;version="3.0.0",
 org.eclipse.emf.cdo.tests.bugzilla;version="3.0.0",
 org.eclipse.emf.cdo.tests.bundle;version="3.0.0",
 org.eclipse.emf.cdo.tests.config;version="3.0.0",
 org.eclipse.emf.cdo.tests.config.impl;version="3.0.0",
 org.eclipse.emf.cdo.tests.defs;version="3.0.0",
 org.eclipse.net4j.tests;version="3.0.0",
 reference;version="3.0.0",
 reference.impl;version="3.0.0",
 reference.util;version="3.0.0"
Eclipse-BuddyPolicy: dependent

Victor Roldan Betancort wrote on Thu, 10 December 2009 14:18

Re: [CDO] Exception on commit [message #503086 is a reply to message #502996]

Thu, 10 December 2009 09:54

Eclipse User

Joel Rosi-Schwartz schrieb:
> This appears to have worked, but I am not sure it actually does work.
> Even though I have switched to the Root_R2_0_maintenance (Version),
Please use the branch tag: R2_0_maintenance

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

> the Manifest still indicates bundle-version="[3.0.0,4.0.0)" for the
> CDO plugins. So is this CVS acting up or has your R2_0_maintenance
> converted to 3.0 bundles accidentally?
>
>
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-SymbolicName: org.eclipse.emf.cdo.tests;singleton:=true
> Bundle-Version: 3.0.0.qualifier
> Bundle-Name: %pluginName
> Bundle-Vendor: %providerName
> Bundle-Localization: plugin
> Bundle-ActivationPolicy: lazy
> Bundle-Activator: org.eclipse.emf.cdo.tests.bundle.OM$Activator
> Bundle-RequiredExecutionEnvironment: J2SE-1.5
> Bundle-ClassPath: .
> Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.4.0,4.0.0)",
> org.eclipse.emf.ecore.xmi;bundle-version="[2.4.0,3.0.0)";visibility:=reexport,
>
> org.eclipse.net4j.jvm;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
>
> org.eclipse.net4j.tcp;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
>
> org.eclipse.emf.cdo.common;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
>
> org.eclipse.emf.cdo.server;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
>
> org.eclipse.emf.cdo;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
> org.eclipse.emf.cdo.tests.mango;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model1;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model2;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model3;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model4;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model4interfaces;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.tests.model5;bundle-version="[3.0.0,4.0.0) ";visibility:=reexport,
>
> org.eclipse.emf.cdo.defs;bundle-version="[3.0.0,4.0.0)";visibility:=reexport,
>
> org.junit;bundle-version="[3.8.0,4.0.0)";visibility:=reexport
> Export-Package: base;version="3.0.0",
> base.impl;version="3.0.0",
> base.util;version="3.0.0",
> derived;version="3.0.0",
> derived.impl;version="3.0.0",
> derived.util;version="3.0.0",
> interface_;version="3.0.0",
> interface_.impl;version="3.0.0",
> interface_.util;version="3.0.0",
> org.eclipse.emf.cdo.tests;version="3.0.0",
> org.eclipse.emf.cdo.tests.bugzilla;version="3.0.0",
> org.eclipse.emf.cdo.tests.bundle;version="3.0.0",
> org.eclipse.emf.cdo.tests.config;version="3.0.0",
> org.eclipse.emf.cdo.tests.config.impl;version="3.0.0",
> org.eclipse.emf.cdo.tests.defs;version="3.0.0",
> org.eclipse.net4j.tests;version="3.0.0",
> reference;version="3.0.0",
> reference.impl;version="3.0.0",
> reference.util;version="3.0.0"
> Eclipse-BuddyPolicy: dependent
>
>
>
> Victor Roldan Betancort wrote on Thu, 10 December 2009 14:18
>> Joel,
>>
>> I had the same problems while fetching R2_0_maintenance sources once.
>> I believe you can download HEAD sources and then perform a "Switch to
>> another Branch or Version" action. Then you select the "Select the
>> tag from the following list" option and then refresh the "Branches"
>> category, the R2_0_maintenance branch shall appear there.
>>
>> Hope it helps,
>> Víctor.
>> >
>
>

Re: [CDO] Exception on commit [message #503087 is a reply to message #502976]

Thu, 10 December 2009 09:54

Eclipse User

Víctor Roldán Betancort schrieb:
> Eike,
>
> I've fetched ORMF's model and it seems to validate correctly.
>
> Our model2 test model has EClasses with references to model1... Do we
> have test-cases using it?
I think so. This is the only purpose of this particular test model :P

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

>
> Eike Stepper escribió:
>> Hi Joel and Vik,
>>
>> I could eventually imagine a problem in CDO with committing objects
>> from multiple new packages at once (forward references). But I'd
>> really prefer to dig down into CDO only if the used packages *all*
>> validate successfully. Can you please ensure this first?
>>
>> If we can reproduce the problem in 2.0 we should do that in 3.0, too,
>> because I vaguely remember that we did something regarding commits of
>> multiple packages. I can not remember anymore when this took place,
>> though.
>>
>> In either case Joel should file a bugzilla.
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>>
>> Joel Rosi-Schwartz schrieb:
>>> Hi Victor,
>>>
>>>>> I will assume you are using CDO 2.0.0, as you pointed that you are
>>>>> using Eclipse 3.5 SR1.
>>>
>>> Yes that is correct.
>>>
>>>>> Is this exception systematically reproducible? From what I
>>>>> understand from your words, it seems to be happening every time
>>>>> your commit an instance of certain EClass, right? Could you
>>>>> provide a better description of that class? If its not possible
>>>>> you to share that model, could you come out with a dummy model
>>>>> that at least resembles the problematic one?
>>>
>>> Yes it is reproducible 100%.
>>>
>>> Yes it is on certain classes only and always on these. So far it
>>> appears to be any Class with a reference, but this is has not been
>>> tested thoroughly yet.
>>>
>>> You can check out the entire model from the ORMF Eclipse project SVN
>>> repository at:
>>>
>>> https://dev.eclipse.org/svnroot/technology/org.eclipse.ormf/ trunk/design/org.eclipse.ormf.design.model
>>>
>>>
>>>
>>> To reproduce:
>>>
>>> 1. start a transaction
>>> 2. create a resource
>>> 3. add a Project at the root
>>> 4. add a Folder as child to the Project
>>> 5. save the resource
>>>
>>> As I said in the original message, the model is really not ready for
>>> this. I had it in my workspace when I brought up my first CDO
>>> server, so I figured I would give it whirl.
>>>
>>>>> By looking at the code, it seems CDOClassifierRef could not
>>>>> retrieve the URI for the EPackage of the problematic EClass (a
>>>>> null value is returned instead) and therefore, while manipulating
>>>>> that URI, the NPE is thrown.
>>>
>>>>> Some quick questions (just to get to know a bit more about your
>>>>> use-case scenario):
>>>
>>>>> - Have you generated your models code? If so, is it "cdo-aware"?
>>>>> (extends CDOObjectImpl)
>>>>> - Do you have your namespace URIs properly defined (not empty)?
>>>>> Are the referenced EClasses under the same EPackage or different
>>>>> EPackage?
>>>
>>> Yes everything is being generated fresh as CDO aware objects. I
>>> think I have the EMF correct, but you can see when you checkout the
>>> project. In the example above the EClasses are both in the same
>>> EPackage. I do have four packages though in the model.
>>>
>>>>> Not sure what might be causing this, but I'll try to reproduce it
>>>>> with our test models and see if it's really related with the
>>>>> "required" attribute.
>>>
>>> Many thanks for the assistance,
>>> Joel
>>>

Re: [CDO] Exception on commit [message #503088 is a reply to message #502931]

Thu, 10 December 2009 09:54

Eclipse User

Hi Joel,

Please note that you should only register packages manually if they're
not already committed to the repository, in which case they would be
automatically registered (and possibly loaded from the repo).

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> Hi,
>
> My plan is to create a simple multi-package example that is complete
> and which reproduces the exception. When I accomplish that I will file
> a Bugzilla against it.
>
> Comments below...
>
> Eike Stepper wrote on Thu, 10 December 2009 10:33
>> Hi Joel,
>>
>> Comments below...
>>
>>
>> Joel Rosi-Schwartz schrieb:
>> > Hi Eike,
>> >
>> > This morning I decided to move over to the standard Extended
>> Library > (org.eclipse.emf.examples.library) example. This example is
>> not expected to work with CDO out of the box. There are some
>> @generated NOT annotations that prevent the needed CDO code to be
>> generated. Please try the examples in CDO (test models in 2.0,
>> examples.company in 3.0)
>
>
> Okay. That makes me feel better. I will check out the CDO examples.
>
> Quote:
>> > I was very surprised to find that an exception is still being
>> thrown > when I commit a transaction, see below. Yes, the library
>> example employs feature maps and I'm currently unsure if they really
>> work well in CDO 2.0. We fixed a lot about them in CDO 3.0. Just for
>> getting more information, could you test your setup with CDO 3.0?
>> Other users reported that it works quite well with Platform 3.5.
>
>
> First I want to get something simple running in 2.0. Then I will give
> 3.0 a go.
>
> Quote:
>> > opened a CDO session
>> > loaded the workspace packages
>> What does "loaded" mean?
>
>
> Register workspace packages would have been more accurate.
>
> Thanks,
> Joel
>

Re: [CDO] Exception on commit [message #503106 is a reply to message #503088]

Thu, 10 December 2009 16:10

Eclipse User

Eike Stepper wrote on Thu, 10 December 2009 14:54

What is the consequence of registering a package that is already in the repository?

Re: [CDO] Exception on commit [message #503109 is a reply to message #503106]

Thu, 10 December 2009 16:33

Eclipse User

Hi,

I have been a able to reproduce the problem in a concise model. Tomorrow morning I will reduce this to as minimalistic a model as possible while still tripping the exception. I will then create a Bugzilla and report it back here.

Briefly what seems to be happening is this. If there are two packages with a class (A) in the second package inheriting from a super class (B) from the first package with B having a reference to a third class C in the first package, then an exception is thrown when the A is added as child to another object from the second package. If that is not clear then best to wait for the model tomorrow as it is difficult to draw diagrams here Wink

Cheers,
Joel

Re: [CDO] Exception on commit [message #503143 is a reply to message #503109]

Fri, 11 December 2009 01:40

Eclipse User

Hi Joel,

Are you talking about packages with cyclic references? I thought about
such a case when I saw that you have a single GenModel for multiple
ecore files. I'll look at the CDO code to see if this case is handöled
properly, but from what I vaguely recall we do not deal with forward
references but rather rely on package ordering on commit. That mihgt
have to be changed.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> Hi,
>
> I have been a able to reproduce the problem in a concise model.
> Tomorrow morning I will reduce this to as minimalistic a model as
> possible while still tripping the exception. I will then create a
> Bugzilla and report it back here.
>
> Briefly what seems to be happening is this. If there are two packages
> with a class (A) in the second package inheriting from a super class
> (B) from the first package with B having a reference to a third class
> C in the first package, then an exception is thrown when the A is
> added as child to another object from the second package. If that is
> not clear then best to wait for the model tomorrow as it is difficult
> to draw diagrams here ;)
>
> Cheers,
> Joel

Re: [CDO] Exception on commit [message #503157 is a reply to message #503143]

Fri, 11 December 2009 03:54

Eclipse User

No not cyclic. I will have the model in this morning and it will be easier to talk about when we can all see it visually.

Joel

Eike Stepper wrote on Fri, 11 December 2009 06:40

Re: [CDO] Exception on commit [message #503182 is a reply to message #502807]

Fri, 11 December 2009 05:13

Eclipse User

Hi,

I have opened Bugzilla 297567 I have included a project with a model that demonstrates the issue, as well as two class diagrams that should help to elucidate and clearify our conversation.

I am looking forward to your thoughts on this.

Cheers,
Joel

Re: [CDO] Exception on commit [message #503247 is a reply to message #503086]

Fri, 11 December 2009 10:22

Eclipse User

Eike Stepper wrote on Thu, 10 December 2009 14:54

Hi Eike,

I have now switched to the tests to the R2_0_maintenance Branch and it is much improved. Two test plugins still do not build because I am missing a few of the db bundles [hsqldb,mysql,h2,postgres] in the Manifest. How do I correct this?

Thanks Joel

Require-Bundle: org.eclipse.emf.cdo.tests;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.server.db;bundle-version="[2.0.0,3.0.0) ";visibility:=reexport,
org.eclipse.net4j.db.hsqldb;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.derby;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
org.eclipse.net4j.db.mysql;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.h2;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.postgresql;bundle-version="2.0.1";visibility:=reexport

[Updated on: Fri, 11 December 2009 10:35] by Moderator

Re: [CDO] Exception on commit [message #503300 is a reply to message #503247]

Fri, 11 December 2009 12:22

Eclipse User

I found in another forum thread that the third party net4j.db plugins had to be taken from the Net4j and CDO Plus Updates site on SourceForge using the update site URL of <http://net4j.sourceforge.net/update>. Unfortunately the installation fails with the Eclipse install new software wizard as per below. Do I have the site wrong or is the update site broken.

Cheers,
Joel

An error occurred while collecting items to be installed
  session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
  Artifact not found: osgi.bundle,org.hibernate,3.3.1.200907301129.
  http://net4j.sourceforge.net/update/plugins/org.hibernate_3.3.1.200907301129.jar
  Artifact not found: org.eclipse.update.feature,org.hibernate,3.3.1.200907301129.
  http://net4j.sourceforge.net/update/features/org.hibernate_3.3.1.200907301129.jar

Joel Rosi-Schwartz wrote on Fri, 11 December 2009 15:22

Eike Stepper wrote on Thu, 10 December 2009 14:54

Require-Bundle: org.eclipse.emf.cdo.tests;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.emf.cdo.server.db;bundle-version="[2.0.0,3.0.0) ";visibility:=reexport,
org.eclipse.net4j.db.hsqldb;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.derby;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
org.eclipse.net4j.db.mysql;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.h2;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
 org.eclipse.net4j.db.postgresql;bundle-version="2.0.1";visibility:=reexport

Re: [CDO] Exception on commit [message #503358 is a reply to message #503300]

Sat, 12 December 2009 03:22

Eclipse User

Hi Joel,

Martin changed the Hibernate version for later Teneo versions. Maybe
that screwed up the update site or some caches. If you don't need CDO
Hibernate it's best not to install it. Hibernate itself should also not
be pulled in then.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> I found in another forum thread that the third party net4j.db plugins
> had to be taken from the Net4j and http://net4j.sourceforge.net/ site
> on SourceForge using the update site URL of
> <http://net4j.sourceforge.net/update>. Unfortunately the installation
> fails with the Eclipse install new software wizard as per below. Do I
> have the site wrong or is the update site broken.
>
> Cheers,
> Joel
>
>
> An error occurred while collecting items to be installed
> session context was:(profile=epp.package.jee,
> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
> operand=, action=).
> Artifact not found: osgi.bundle,org.hibernate,3.3.1.200907301129.
> http://net4j.sourceforge.net/update/plugins/org.hibernate_3. 3.1.200907301129.jar
>
> Artifact not found:
> org.eclipse.update.feature,org.hibernate,3.3.1.200907301129.
> http://net4j.sourceforge.net/update/features/org.hibernate_3 .3.1.200907301129.jar
>
>
>
>
> Joel Rosi-Schwartz wrote on Fri, 11 December 2009 15:22
>> Eike Stepper wrote on Thu, 10 December 2009 14:54
>> > Joel Rosi-Schwartz schrieb:
>> > > This appears to have worked, but I am not sure it actually does
>> work. > > Even though I have switched to the Root_R2_0_maintenance
>> (Version),
>> > Please use the branch tag: R2_0_maintenance
>>
>>
>> Hi Eike,
>>
>> I have now switched to the tests to the R2_0_maintenance Branch and
>> it is much improved. Two test plugins still do not build because I am
>> missing a few of the db bundles [hsqldb,mysql,h2,postgres] in the
>> Manifest. How do I correct this?
>>
>> Thanks Joel
>>
>>
>> Require-Bundle:
>> org.eclipse.emf.cdo.tests;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
>>
>> org.eclipse.emf.cdo.server.db;bundle-version="[2.0.0,3.0.0)
>> ";visibility:=reexport,
>> org.eclipse.net4j.db.hsqldb;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
>>
>> org.eclipse.net4j.db.derby;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
>>
>> org.eclipse.net4j.db.mysql;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
>>
>> org.eclipse.net4j.db.h2;bundle-version="[2.0.0,3.0.0)";visibility:=reexport,
>>
>> org.eclipse.net4j.db.postgresql;bundle-version="2.0.1";visibility:=reexport
>>
>
>

Re: [CDO] Exception on commit [message #503366 is a reply to message #503358]

Sat, 12 December 2009 02:30

Eclipse User

Eike Stepper wrote on Sat, 12 December 2009 08:22

Martin changed the Hibernate version for later Teneo versions. Maybe
that screwed up the update site or some caches. If you don't need CDO
Hibernate it's best not to install it. Hibernate itself should also not
be pulled in then.

Hi Eike,

I can get the install to complete by removing Hibernate as you suggest. However, the build is still broken as per below. I am wondering if the drivers are for CDO 2.0 or 3.0? I am still at 2.0 so perhaps that is why the bundles still do not resolve. I have checked the PDE platform target and indeed these packages are still not there.

Thanks,
Joel

Description	Resource	Path	Location	Type
Bundle 'org.eclipse.net4j.db.h2' cannot be resolved	MANIFEST.MF	/org.eclipse.emf.cdo.tests.db/META-INF	line 17	Plug-in Problem
Bundle 'org.eclipse.net4j.db.hsqldb' cannot be resolved	MANIFEST.MF	/org.eclipse.emf.cdo.tests.db/META-INF	line 14	Plug-in Problem
Bundle 'org.eclipse.net4j.db.mysql' cannot be resolved	MANIFEST.MF	/org.eclipse.emf.cdo.tests.db/META-INF	line 16	Plug-in Problem
Bundle 'org.eclipse.net4j.db.postgresql' cannot be resolved	MANIFEST.MF	/org.eclipse.emf.cdo.tests.db/META-INF	line 18	Plug-in Problem
H2Adapter cannot be resolved to a type	AllTestsDBH2.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 73	Java Problem
H2Adapter cannot be resolved to a type	AllTestsDBH2NonAudit.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 102	Java Problem
HSQLDBAdapter cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 77	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 61	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 83	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 83	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 84	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 85	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 89	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 96	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 133	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 140	Java Problem
HSQLDBDataSource cannot be resolved to a type	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 148	Java Problem
MYSQLAdapter cannot be resolved to a type	AllTestsDBMysql.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 74	Java Problem
PostgreSQLAdapter cannot be resolved to a type	AllTestsDBPsql.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 108	Java Problem
The import org.eclipse.net4j.db.h2 cannot be resolved	AllTestsDBH2.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 17	Java Problem
The import org.eclipse.net4j.db.h2 cannot be resolved	AllTestsDBH2NonAudit.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 23	Java Problem
The import org.eclipse.net4j.db.hsqldb cannot be resolved	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 21	Java Problem
The import org.eclipse.net4j.db.hsqldb cannot be resolved	AllTestsDBHsqldb.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 22	Java Problem
The import org.eclipse.net4j.db.mysql cannot be resolved	AllTestsDBMysql.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 19	Java Problem
The import org.eclipse.net4j.db.postgresql cannot be resolved	AllTestsDBPsql.java	 /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db	line 27	Java Problem

[Updated on: Sat, 12 December 2009 02:31] by Moderator

Re: [CDO] Exception on commit [message #503388 is a reply to message #503366]

Sat, 12 December 2009 08:20

Eclipse User

Hi Joel,

I'm confused, are you installing (into TP) or building (from WS)?

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> Eike Stepper wrote on Sat, 12 December 2009 08:22
>> Martin changed the Hibernate version for later Teneo versions. Maybe
>> that screwed up the update site or some caches. If you don't need CDO
>> Hibernate it's best not to install it. Hibernate itself should also
>> not be pulled in then.
>
>
> Hi Eike,
>
> I can get the install to complete by removing Hibernate as you
> suggest. However, the build is still broken as per below. I am
> wondering if the drivers are for CDO 2.0 or 3.0? I am still at 2.0 so
> perhaps that is why the bundles still do not resolve. I have checked
> the PDE platform target and indeed these packages are still not there.
>
> Thanks,
> Joel
>
> [CODE
> Description Resource Path Location Type
> Bundle 'org.eclipse.net4j.db.h2' cannot be resolved MANIFEST.MF
> /org.eclipse.emf.cdo.tests.db/META-INF line 17 Plug-in Problem
> Bundle 'org.eclipse.net4j.db.hsqldb' cannot be resolved
> MANIFEST.MF /org.eclipse.emf.cdo.tests.db/META-INF line 14
> Plug-in Problem
> Bundle 'org.eclipse.net4j.db.mysql' cannot be resolved
> MANIFEST.MF /org.eclipse.emf.cdo.tests.db/META-INF line 16
> Plug-in Problem
> Bundle 'org.eclipse.net4j.db.postgresql' cannot be resolved
> MANIFEST.MF /org.eclipse.emf.cdo.tests.db/META-INF line 18
> Plug-in Problem
> H2Adapter cannot be resolved to a type AllTestsDBH2.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 73 Java Problem
> H2Adapter cannot be resolved to a type
> AllTestsDBH2NonAudit.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 102 Java Problem
> HSQLDBAdapter cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 77 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 61 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 83 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 83 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 84 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 85 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 89 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 96 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 133 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 140 Java Problem
> HSQLDBDataSource cannot be resolved to a type
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 148 Java Problem
> MYSQLAdapter cannot be resolved to a type AllTestsDBMysql.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 74 Java Problem
> PostgreSQLAdapter cannot be resolved to a type
> AllTestsDBPsql.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 108 Java Problem
> The import org.eclipse.net4j.db.h2 cannot be resolved
> AllTestsDBH2.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 17 Java Problem
> The import org.eclipse.net4j.db.h2 cannot be resolved
> AllTestsDBH2NonAudit.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 23 Java Problem
> The import org.eclipse.net4j.db.hsqldb cannot be resolved
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 21 Java Problem
> The import org.eclipse.net4j.db.hsqldb cannot be resolved
> AllTestsDBHsqldb.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 22 Java Problem
> The import org.eclipse.net4j.db.mysql cannot be resolved
> AllTestsDBMysql.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 19 Java Problem
> The import org.eclipse.net4j.db.postgresql cannot be resolved
> AllTestsDBPsql.java
> /org.eclipse.emf.cdo.tests.db/src/org/eclipse/emf/cdo/tests/ db
> line 27 Java Problem
>
> ][/CODE]

Re: [CDO] Exception on commit [message #503390 is a reply to message #503388]

Sat, 12 December 2009 08:58

Eclipse User

Hi Eike,

Into an Eclipse IDE for Java EE Developers 3.5 (CDO 2.0) workspace I have checked out all of the CDO tests from the CVS repository using Branch 2.0_maint. I have installed the db plug-ins (except Hibernate) from the SF update site. Two test plugins (org.eclipse.emf.cdo.tests and org.eclipse.emf.cdo.tests.db) do not build. The first because of there are 4 methods not defined in CDOSavepointImpl, the second because DB bundles are missing.

Does this answer your question?

I the end this really is not critical to me, I am only using the test code to better understand CDO. I am pursuing this for these two reasons: 1) I would like to know that I do not have fundamental issues with my CDO setup; 2) I think it is important the users can build and test from the repository.

If this become painful to rectify I have no real problem with simply moving on at the moment Wink

Cheers,
Joel

Eike Stepper wrote on Sat, 12 December 2009 13:20

Hi Joel,

I'm confused, are you installing (into TP) or building (from WS)?

Cheers
/Eike

[Updated on: Sat, 12 December 2009 13:59] by Moderator

Re: [CDO] Exception on commit [message #503413 is a reply to message #503390]

Sun, 13 December 2009 03:53

Eclipse User

Hi Joel,

If you have compile errors then there's definitely something wrong with
your setup (TP and WS). Most probably you mixed wrong versions. Please
also try to reload your TP and restart Eclipse with -clean.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Joel Rosi-Schwartz schrieb:
> Hi Eike,
>
> Into an Eclipse IDE for Java EE Developers 3.5 (CDO 2.0) workspace I
> have checked out all of the CDO examples from the CVS repository using
> Branch 2.0_maint. I have installed the db plug-ins (except Hibernate)
> from the SF update site. Two test plugins (org.eclipse.emf.cdo.tests
> and org.eclipse.emf.cdo.tests.db) do not build. The first because of
> there are 4 methods not defined in CDOSavepointImpl, the second
> because DB bundles are missing.
>
> Does this answer your question?
>
> I the end this really is not critical to me, I am only using the test
> code to better understand CDO. I am pursuing this for these two
> reasons: 1) I would like to know that I do not have fundamental issues
> with my CDO setup; 2) I think it is important the users can build and
> test from the repository.
>
> If this become painful to rectify I have no real problem with simply
> moving on at the moment ;)
>
> Cheers,
> Joel
>
> Eike Stepper wrote on Sat, 12 December 2009 13:20
>> Hi Joel,
>>
>> I'm confused, are you installing (into TP) or building (from WS)?
>>
>> Cheers
>> /Eike
>
>

Re: [CDO] Exception on commit [message #503459 is a reply to message #503413]

Mon, 14 December 2009 05:37

Eclipse User

Hi Eike,

Sorry, I have just spent half an hour on writing detailed reply and it got devoured when I submitted it. (Not the first time this has happened to me on the Eclipse forums:( I just don't have the energy to redo it all again. So here is a synopsis.

I have restarted with -clean (more than once;-) to no avail.

I my opinion there are two more or less unrelated issues. First is that the CDO in the TP is not in sync with the test from CVS. I have clean Eclipse Modeling 3.5 SR1, so I have to assume that the mismatch is on the CVS side where I have R2_0_maintenance (Branch). The second issue is caused by the third party drivers from SF either being a miss-installed or a mismatch as the required bundles are not only not in my TP but are not found in a search on my computer.

In both cases I do not think there is much value for me to continue trying to resolve it unless you think I would be doing some kind of service to the CDO project. Let me know.

I am more interested, to be frank, in sorting my original issue for which I filed opened Bugzilla 297567 as this is a show stopper for me.

Many thanks,
Joel

Eike Stepper wrote on Sun, 13 December 2009 08:53

[Updated on: Mon, 14 December 2009 00:37] by Moderator

Re: [CDO] Exception on commit [message #503467 is a reply to message #503459]

Mon, 14 December 2009 01:12

Eclipse User

Hi Joel,

Comments below...

Joel Rosi-Schwartz schrieb:
> Hi Eike,
>
> Sorry, I have just spent 20 half an hour on writing detailed reply
I wonder why your messages don't get line-wrapped here. That's pretty
annoying ;-(

> and it got devoured when I submitted it. (Not the first time this has
> happened to me on the Eclipse forums:( I just don't have the energy
> to redo it all again. So here is a synopsis.
>
> I have restarted with -clean (more than once;-) to no avail.
Darned!

>
> I my opinion there are two more or less unrelated issues. First is
> that the CDO in the TP is not in sync with the test from CVS.
That's probably no issue in CDO.

> I have clean Eclipse Modeling 3.5 SR1, so I have to assume that the
> mismatch is on the CVS side where I have R2_0_maintenance (Branch).
Sounds good.

> The second issue is caused by the third party drivers from SF either
> being a miss-installed or a mismatch as the required bundles are not
> only not in my TP but are not found in a search on my computer.
That sounds like a problem.

>
> In both cases I do not think there is much value for me to continue
> trying to resolve it unless you think I would be doing some kind of
> service to the CDO project. Let me know.
I almost never hear of such problems and the manifests in CDO are top
quality. There must be something wrong on your setup.

>
> I am more interested, to be frank, in sorting my original issue for
> which I filed opened Bugzilla
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=297567 as this is a show
> stopper for me.
Vik just told me that he couldn't reproduce it. I'll try, too, with his
patch...

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

>
> Many thanks,
> Joel
>
> Eike Stepper wrote on Sun, 13 December 2009 08:53
>> Hi Joel,
>>
>> If you have compile errors then there's definitely something wrong
>> with your setup (TP and WS). Most probably you mixed wrong versions.
>> Please also try to reload your TP and restart Eclipse with -clean.
>>
>> Cheers
>> /Eike
>
>

Re: [CDO] Exception on commit [message #503486 is a reply to message #503467]

Mon, 14 December 2009 08:15

Eclipse User

Hi Eike and Vic,

I have just ran the test case in my Eclipse SR1 environment and it passes there also. When I exercise the same steps in the CDO Session view however I do get the exception. My apologies, I realise now that I was not explicit in stating that I was running this from the CDO Session view rather than code.

I have updated the Bugzilla with this same comment.

Cheers,
Joel

Eike Stepper wrote on Mon, 14 December 2009 06:12

> I am more interested, to be frank, in sorting my original issue for
> which I filed opened Bugzilla
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=297567 as this is a show
> stopper for me.
Vik just told me that he couldn't reproduce it. I'll try, too, with his
patch...

Cheers
/Eike

Re: [CDO] Exception on commit [message #503930 is a reply to message #502807]

Wed, 16 December 2009 04:29

Eclipse User

Many thanks to both Eike and Victor for their fabulous support in general and with this in particular.

Cheers,
Joel

Previous Topic:	[CDO] OutOfMemoryError when committing frequently
Next Topic:	Regenerating model code

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 06 15:54:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter