Bugzilla – Full Text Bug Listing
| Summary: | epsilon.loadModel expand feature error | ||
|---|---|---|---|
| Product: | [Modeling] Epsilon | Reporter: | Chris Holmes <holmeschrisk> |
| Component: | Core | Assignee: | Dimitris Kolovos <dkolovos> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | interim | ||
I've tried to reproduce this but haven't managed to (hopefully, it's been fixed somewhere along the way). Closing as fixed but please feel free to re-open if encountered again. Fixed in the latest interim version. Fixed in 1.1 |
The epsilon.loadModel expand attribute allows clients to access models that are ref'd (rather than owned). The syntax for using this feature is: <epsilon.loadModel name="${MyModel}" type="EMF"> <parameter name="expand" value="true"/> <parameter name="modelFile" file="${MyModelModel}"/> <parameter name="metamodelUri" value="${MyMetamodelUri}"/> <parameter name="readOnLoad" value="true"/> <parameter name="storeOnDisposal" value="false"/> </epsilon.loadModel> If two instances of the same model are loaded under different aliases then the expand feature does not operate correctly and it is not possible to navigate from the named model instance to the ref'd model. Item 'Navigation of ref'd associations posted on 07-May-2010 to the epsilon newsgroup refers. Error demonstrated to Dimitris on 20-May-2010 and this bug report raised at his request.