Description Eike Stepper 2011-02-01 05:11:27 EST

See bug 335942 !!!

In CDO this may lead to:

java.lang.NullPointerException
org.eclipse.net4j.signal.RemoteException: java.lang.NullPointerException
        at org.eclipse.net4j.signal.RequestWithConfirmation.setRemoteException(RequestWithConfirmation.java:128)
        at org.eclipse.net4j.signal.SignalProtocol.handleRemoteException(SignalProtocol.java:423)
        at org.eclipse.net4j.signal.RemoteExceptionIndication.indicating(RemoteExceptionIndication.java:63)
        at org.eclipse.net4j.signal.Indication.doExtendedInput(Indication.java:55)
        at org.eclipse.net4j.signal.Signal.doInput(Signal.java:316)
        at org.eclipse.net4j.signal.Indication.execute(Indication.java:49)
        at org.eclipse.net4j.signal.Signal.runSync(Signal.java:241)
        at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
        at org.eclipse.emf.cdo.server.internal.db.mapping.CoreTypeMappings$TMEnum.getDefaultValue(CoreTypeMappings.java:94)
        at org.eclipse.emf.cdo.server.db.mapping.AbstractTypeMapping.setValue(AbstractTypeMapping.java:115)
        at org.eclipse.emf.cdo.server.db.mapping.AbstractTypeMapping.setValueFromRevision(AbstractTypeMapping.java:94)
        at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.HorizontalBranchingClassMapping.writeValues(HorizontalBranchingClassMapping.java:635)
        at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.HorizontalBranchingClassMapping.writeRevision(HorizontalBranchingClassMapping.java:807)
        at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.writeRevision(DBStoreAccessor.java:563)
        at org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.writeRevisions(DBStoreAccessor.java:544)
        at org.eclipse.emf.cdo.spi.server.StoreAccessor.write(StoreAccessor.java:187)
        at org.eclipse.emf.cdo.internal.server.TransactionCommitContext.write(TransactionCommitContext.java:407)
        at org.eclipse.emf.cdo.spi.server.InternalCommitContext$1.runLoop(InternalCommitContext.java:40)
        at org.eclipse.emf.cdo.spi.server.InternalCommitContext$1.runLoop(InternalCommitContext.java:1)
        at org.eclipse.net4j.util.om.monitor.ProgressDistributor.run(ProgressDistributor.java:96)
        at org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitTransactionIndication.indicatingCommit(CommitTransactionIndication.java:233)
        at org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitTransactionIndication.indicating(CommitTransactionIndication.java:90)
        at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndicationWithMonitoring.indicating(CDOServerIndicationWithMonitoring.java:109)
        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:316)
        at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:63)
        at org.eclipse.net4j.signal.IndicationWithMonitoring.execute(IndicationWithMonitoring.java:63)
        ... 5 more

Is it possible to come up with an exception that points to where the user is supposed to fix the root cause??