Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329011 - [parser] Proxy types not diagnosed
Summary: [parser] Proxy types not diagnosed
Status: NEW
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard: Legacy
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-29 04:41 EDT by Ed Willink CLA
Modified: 2012-04-05 16:08 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2010-10-29 04:41:14 EDT 
UMLReflectionImpl.getOCLTypeFor() does not handle an unresolved proxy which may result from a UML usage in which the UML pathmaps were not initialized. The current behaviour just drops through exploiting the PrimitiveType of the proxy class and eventually fails with missing operations. The failure message should at least contain the words 'unresolved proxy' or equivalent.

See http://www.eclipse.org/forums/index.php?t=msg&th=198861&start=0&S=3298dc889182b375c3537d202e634061 for a repro: