Comment 1 Stefan Winkler 2010-02-16 12:39:25 EST

Hi Sabri,

thanks for your Bug report. So far I am not able to reproduce it, though.

I have put your code into a test class:

public class Bugzilla_302838_Test extends AbstractCDOTest
{
  public void testRestaurant()
  {
    {
      CDOSession session = openSession();

      // open the transaction
      CDOTransaction transaction = session.openTransaction();

      // create the resource
      transaction.createResource("/edine/resto2.inventory");

      transaction.commit();
      session.close();
    }

    CDOSession session = openSession();
    session.getPackageRegistry().putEPackage(InventoryPackage.eINSTANCE);
    // open the transaction
    CDOTransaction transaction = session.openTransaction();

    // create the resource
    CDOResource resource = transaction.getResource("/edine/resto2.inventory");
    // Work with resource
    Restaurant restaurant = InventoryFactory.eINSTANCE.createRestaurant();
    resource.getContents().add(restaurant);

    // Commit the transaction
    transaction.commit();

    session.close();
  }
}

I had to introduce the block above, because the resource obviously would not exist on an empty database. I tried the code with several databases and configurations, but could not provoke the exception you report.

Can you please give some more information about you configuration? Which DB do you use? What is your server configuration?
Also, can you tell me how your resource is created in the code you gave?

Comment 2 Stefan Winkler 2010-02-16 12:43:02 EST

As a side-note: 
Eike, the Exception implies that the following call

CDOID cdoid = getPackageRegistry().getMetaInstanceMapper().lookupMetaInstanceID((InternalEObject)modelElement);

returns a CDOIDTemp for a modelElement instanceof EStructuralFeature. How can this happen?

Comment 3 Sabri Skhiri 2010-02-17 03:16:11 EST

Hi Stefan,

Thanx for your reactivity. 
Actually even I create the resource before, and that this creation successes, if I try to commit something on this resource it fails. So, I do no think that getOrCreateResource() or createResource() are involved.

Note: the package was registered as Dynamic in CDO, not as native. Does it change anything ?

Configuration info:
* DB: h2
* CDO 3.0.0.v200910010403 and Last from repository
* Exception on Linux Ubuntu and Win XP

Do you need something else ?

Comment 4 Caspar D. 2010-02-22 21:58:20 EST

Stefan asked for someone to comment whether bug 303466 might
have any relation to this.

At first sight, I think not, because the code snippets I see here 
use the generated InventoryPackage.

But then I'm a bit confused by Sabri's Feb 17 comment that "the 
package was registered as Dynamic in CDO, not as native"...

I'm guessing we either do not agree on the meaning of the term 
"dynamic", which AFAIC is defined by EMFUtil.isDynamicPackage(Object); 
or perhaps the code which actually produced the stacktrace is different 
from what's given in the initial bug report?

Please clarify..

Comment 5 Eike Stepper 2010-02-23 02:37:18 EST

(In reply to comment #4)
> But then I'm a bit confused by Sabri's Feb 17 comment that "the 
> package was registered as Dynamic in CDO, not as native"...

Just a minor correction: dynamic models are in fact native. At runtime they are using DynamicCDOObjects which derive from CDOObjectImpl.

Comment 6 Caspar D. 2010-02-23 06:19:57 EST

(In reply to comment #5)
> Just a minor correction: dynamic models are in fact native. At runtime they are
> using DynamicCDOObjects which derive from CDOObjectImpl.

Noted, which makes native-vs-non-native irrelevant for this bug.

Therefore, Sabri, please clarify if you really encountered this problem 
using a *non-generated* model. The code snippets in your original report
suggest that you were using the *generated* InventoryPackage.

Comment 7 Sabri Skhiri 2010-02-23 11:25:07 EST

Hi Caspar,

Actually I reproduced with both *non-generated* and *generated* InventoryPackage.

Best regards,

Sabri.

Comment 8 Stefan Winkler 2010-02-25 02:53:51 EST

Hi Sabri,

as I cannot reproduce the issue with my attempts of creating a test case, could you attach a (preferrably minimum) zipped project so that I can reproduce the problem in that way?

Thanks!

Comment 9 Sabri Skhiri 2010-02-25 10:56:21 EST

Created attachment 160197 [details]
The project I used to reproduce the bug

Process:
1. I start a run-time instance of Eclipse in order to have my inventory.cdo model loaded as a bundle.
2. I start a cdo server by the exercise 06 code
3. I open a CDO session UI view, I open a session to localhost and gastro repository
4. I try to import the resto1.inventory in a new resource and the exception occurs

and even in the CDO UI Session the exception occurrs.

Comment 10 Eike Stepper 2010-06-29 04:54:44 EDT

Rebasing all outstanding 3.0 problem reports to version 3.0.1

Comment 11 Eike Stepper 2010-07-07 07:10:40 EDT

Fixing wrong bug version.

Comment 12 Eike Stepper 2011-06-23 04:27:11 EDT

Moving all open problem reports to 4.0

Comment 13 Eike Stepper 2012-06-05 07:29:34 EDT

Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!

Comment 14 Eike Stepper 2012-08-14 22:51:06 EDT

Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.

Comment 15 Eike Stepper 2013-06-29 12:16:56 EDT

We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.

Comment 16 Eike Stepper 2015-07-14 02:08:48 EDT

Moving all open bugzillas to 4.5.

Comment 17 Eike Stepper 2016-07-31 00:51:44 EDT

Moving all unaddressed bugzillas to 4.6.

Comment 18 Eike Stepper 2017-12-28 01:13:08 EST

Moving all open bugs to 4.7

Comment 19 Eike Stepper 2019-11-08 02:14:40 EST

Moving all unresolved issues to version 4.8-

Comment 20 Eike Stepper 2019-12-13 12:55:11 EST

Moving all unresolved issues to version 4.9

Comment 21 Eike Stepper 2020-12-11 10:42:06 EST

Moving to 4.13.