Bugzilla – Full Text Bug Listing
| Summary: | Error report on mixing different views | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Egidijus Vaisnora <vaisegid> | ||||||
| Component: | cdo.core | Assignee: | Project Inbox <emf.cdo-inbox> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Eike Stepper <stepper> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | martin.fluegge | ||||||
| Version: | 4.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | Macintosh | ||||||||
| OS: | Mac OS X | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Egidijus Vaisnora
Created attachment 175576 [details]
test attached
Created attachment 175594 [details] Test v2 Hi Egidijus, I had a quick look to your test it it seems to me that the problem you are describing is quite similar to the one covered by Bug 305527. If you agree that this is the same issue we could close this one as duplicated and proceed on 305527. I modified your test case slightly to make it legacy aware. When accessing CDO related properties from an object it's always best to get this object using CDOUtil.getCDOObject() first. Otherwise you would get a ClasscastException when running a legacy scenario because in this case the object is just a normal EMF object and not a CDO native one. When using CDOUtil to get the object the test logic is transparent to NATIVE and LEGACY scenarios...in most cases ;) Yes, 305527 looks like the similar issue. We can close this one Closed because it's duplicate of Bug 305527. *** This bug has been marked as a duplicate of bug 305527 *** Moving all open problem reports to 4.0 Closing. |