I have an Xtext project in which I am trying to add a "#include" mechanism that allows the user to include a file (with any file extension) to be parsed for instances of my own Ecore object. The approach I took is similar to the one I found in this post: http://www.eclipse.org/forums/index.php/t/526180/
However, since I would like to be able to handle any type of file without concern for the file extension, I added an extension points to org.eclipse.emf.ecore.protocol_parser and org.eclipse.xtext.protocol_resourceServiceProvider with protocolName="file", rather than the extension version of those two as in the above post.
My question is can I safely make these extensions to the file protocol, or in doing so am I overriding other important EMF/Xtext resource handlers?
If you have a reference to these arbitrary files, how do you know how to parse them and turn them into an EMF model?
The much cleaner way would be to register every single file type you want to support similar to the description in that other thread.