|
|
|
|
|
Re: Associate file-extension to 2 diff content-types based on file name patterns [message #517603 is a reply to message #517587] |
Mon, 01 March 2010 14:07 |
Ed Merks Messages: 33224 Registered: July 2009 |
Senior Member |
|
|
Chetan,
Comments below.
Chetan Kumar wrote:
> Hello Ed,
>
> Then mere file-association with a content-type based on file-names
> will not solve my problem.
Nope.
>
> Ultimately, with this set-up i want to load these 2 files (with same
> extn but different file-name postfix) into 2 different EMF models.
It seems likely then that the namespace of the root element or the name
of the root element should be sufficient to define the content type
without resorting to this notion of the postfix itself making the
distinction...
> The actual ContentType contributions associated with my 2 files is a
> black-box for me.
I'm not sure I understand that comment. Why?
> So, will contributing to EMF content_handler extension-point solve the
> problem ?
Yes, it will solve the problem from and EMF point of view, but the
platform itself uses content types to determine things like editor
associations and for that, the more flexible EMF solution won't help.
> as in, with my ContentHandler implementation - i can override the
> getFactory(URI) method to return based on file-name postfix strings.
>
> + Chetan Kumar
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03997 seconds