| ID Attributes [message #66487] |
Fri, 20 October 2006 10:36  |
Eclipse User |
|
|
|
Originally posted by: snej_NO-SPAM_.esuark.de
Hello there,
we have some ID attributes in our ecore model, and after settings this
id field with the emf-editor part in the gmf-diagram, it results in this:
<objectX id="#enteredID"/>
Does anybody know where the # sign comes from? Our id fields in the
ecore model are defined as "ID <java.lang.String>" and have the
attribute "ID" set to true.
We could filter this # out for postprocessing, but it would be nice if
it doesn't appear at all :).
regards
Jens Krause
|
|
|
| Re: ID Attributes [message #66550 is a reply to message #66487] |
Fri, 20 October 2006 11:32  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Jens,
Proxy resolving references (EReference.resolveProxies == true) will
generally be serialized in the form <resourceURI>#<fragment>. If they
are same document references, this will be deresolved to a document
relative form and become #<fragment>. Non-proxy resolving references
will just be of the form <fragment> since they must resolve to something
within the same document. So probably changing the model to set resolve
proxies to false will produce what you want.
Jens Krause wrote:
> Hello there,
>
> we have some ID attributes in our ecore model, and after settings this
> id field with the emf-editor part in the gmf-diagram, it results in this:
>
> <objectX id="#enteredID"/>
>
> Does anybody know where the # sign comes from? Our id fields in the
> ecore model are defined as "ID <java.lang.String>" and have the
> attribute "ID" set to true.
>
> We could filter this # out for postprocessing, but it would be nice if
> it doesn't appear at all :).
>
> regards
> Jens Krause
|
|
|
Powered by
FUDForum. Page generated in 0.02656 seconds
Home