|Re: Problem with HUTN configuration files [message #640826 is a reply to message #640779]
||Tue, 23 November 2010 10:10
| Louis Rose
Registered: July 2009
Location: York, United Kingdom
I'm a bit confused... This HUTN source code doesn't use a HUTN configuration file. In Epsilon, HUTN configuration files only define three types (Configuration, IdentifierRule and DefaultValueRule), none of which are used in this HUTN source code.
So, it seems that this isn't a problem with HUTN configuration files, but with a cross-model reference. I think the errors might be expected because, in this HUTN source, the two lines that have errors (firstElement and element) seem to be incorrect for two reasons:
1) They should start with "platform:/resource" (like the other cross-references in this HUTN source).
2) They should reference the target model elements using a URI fragment. For example, "//@firstname.lastname@example.org" is a valid URI fragment, which means the "first rule contained in the first configuration of the model".
"//gbddName/dsName" is not a valid URI fragment, and EMF cannot resolve it. Either use a valid URI fragment, or use an XMI ID instead.
The EMF book describes the way in which URI fragments and XMI IDs can be used to refer to model elements. There seems to be an online version of the relevant chapter here: http://learning.infocollections.com/ebook%202/Computer/Progr amming/Java/Eclipse.Modeling.Framework/0131425420_ch13lev1se c2.html
I can't explain why this worked in Epsilon 0.8.8. Without a URI schema (such as "platform:/resource"), the cross-references could not have been resolved. I hope the two proposals above help to fix the problem now though.
Powered by FUDForum
. Page generated in 0.11207 seconds