| How to implement own URI scheme? [message #381973] |
Fri, 23 January 2004 06:25  |
Eclipse User |
|
|
|
Hi,
in our project we probably need to invent our own kind of URI for storing
cross-document references. The problem is that we have a lot of archives
containing metadata XMLs which reference each other, i.e. cross-archive
references. BUT, we cannot use JAR-URIs because they contain the absolute
path to the archive. This is unfortunately unacceptable in our case.
Now my idea is to use our own URI notation (only for the non-fragment
part), something like "metadata:/<our special scheme specific part>#<URI
fragment (same as in EMF)>".
Is this kind of extension generally possible in EMF, or are there any
hardcoded implementation details only allowing certain URI schemes? What
would be a good starting point (wrt. subclassing etc.) ?
bye
Stefan
|
|
|
| Re: How to implement own URI scheme? [message #381978 is a reply to message #381973] |
Fri, 23 January 2004 11:08  |
| Eclipse User |
|
|
|
Stefan,
Look at URIConverters and how ResourceSets use them. If you have a copy of
the EMF book, chapter 13 would be good to read.
Frank.
Stefan wrote:
> Hi,
>
> in our project we probably need to invent our own kind of URI for storing
> cross-document references. The problem is that we have a lot of archives
> containing metadata XMLs which reference each other, i.e. cross-archive
> references. BUT, we cannot use JAR-URIs because they contain the absolute
> path to the archive. This is unfortunately unacceptable in our case.
>
> Now my idea is to use our own URI notation (only for the non-fragment
> part), something like "metadata:/<our special scheme specific part>#<URI
> fragment (same as in EMF)>".
>
> Is this kind of extension generally possible in EMF, or are there any
> hardcoded implementation details only allowing certain URI schemes? What
> would be a good starting point (wrt. subclassing etc.) ?
>
> bye
> Stefan
|
|
|
Powered by
FUDForum. Page generated in 0.26480 seconds
Home