| 
| EFS again... Metadata [message #331444] | Sun, 07 September 2008 15:27  |  | 
| Eclipse User  |  |  |  |  | Hi everybody. 
 I was wondering if there is a clean way for accessing metadata provided
 via EFS mechanisms.
 
 I'll try to explain better my use case. I successfully wrote a
 filesystem for accessing a remote system. The openInputStream and
 openOutputStream allow me to interact with the remote data by reading
 and saving it.
 
 Now my problem is that the remote data (that is actually a document)
 also has some metadata associated (e.g., the version, author, etc.).
 
 I was thinking of providing, through the openInputStream method, both
 the content and the metadata as the result. However I would like to keep
 things separated.
 
 The solution I found was to ask to EFS to give me the FileStore
 associated to the current edited URI. Then I cast this FileStore to its
 actual type that will have some extra methods for accessing the
 metadata, and I use them for getting what I want.
 
 This solution works fine. However it seems a bit dirty since I have to
 "open" the implementation of my filesystem by exporting all the
 FileStores that, normally, should be "internal".
 
 Do you know another way for doing what I am trying to do in a clean way?
 
 Thank you.
 
 -F
 |  |  |  | 
| 
| Re: EFS again... Metadata [message #331845 is a reply to message #331444] | Wed, 24 September 2008 17:57  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: eclipseng.arthorne.com 
 You may be able to use IFileInfo#getStringAttribute for this kind of
 metadata.
 --
 
 
 Fabio Mancinelli wrote:
 > Hi everybody.
 >
 > I was wondering if there is a clean way for accessing metadata provided
 > via EFS mechanisms.
 >
 > I'll try to explain better my use case. I successfully wrote a
 > filesystem for accessing a remote system. The openInputStream and
 > openOutputStream allow me to interact with the remote data by reading
 > and saving it.
 >
 > Now my problem is that the remote data (that is actually a document)
 > also has some metadata associated (e.g., the version, author, etc.).
 >
 > I was thinking of providing, through the openInputStream method, both
 > the content and the metadata as the result. However I would like to keep
 > things separated.
 >
 > The solution I found was to ask to EFS to give me the FileStore
 > associated to the current edited URI. Then I cast this FileStore to its
 > actual type that will have some extra methods for accessing the
 > metadata, and I use them for getting what I want.
 >
 > This solution works fine. However it seems a bit dirty since I have to
 > "open" the implementation of my filesystem by exporting all the
 > FileStores that, normally, should be "internal".
 >
 > Do you know another way for doing what I am trying to do in a clean way?
 >
 > Thank you.
 >
 > -F
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.33751 seconds