We're updating the issue view to help you get more done. 

Unloading a relation which object has been loaded otherwise causes an expcetion

Description

The following case throws an exception:

  • Entering a sub client transaction

  • Load an object of type A which has an biderectional relation to type B

    • The foreign key is located at type A

  • Load an object of type B but do not load it by using the realation property (order of execution is not relevant)

  • Call UnloadService.UnloadVirtualEndPointAndItemData for type B for the realation with A

  • access the relation property on B

This test shows the issue

Here is the stack trace from our project

See UnloadInSubTransactionsTest.cs :: UnloadCollectionEndPointAndData_ForObject

Status

Assignee

Michael Ketting

Reporter

Matthias Rohrmoser

Labels

None

Components

Fix versions

Affects versions

Priority

Normal
Configure