|XML Editor content types and 'complex' extensions [message #216670]
||Wed, 02 July 2008 19:53
| Eugene Marcotte
Registered: July 2009
I'm not sure if this is the right place for XML editor stuff or not, I
seem to recall it being part of webtools.
I'm using Ganymede, on Fedora Core 9, 64 bit.
I was just trying to edit a file using the XML editor, and of course this
file doesn't end with .xml. The dialog that came up told me to add the
content type for this file, so I did. I added "*.jnlp.in" under xml and I
also added *.jnlp while I was there.
I went back to the file, and tried again. It still wouldn't open, same
exact message comes up. If I rename the file to end with just .jnlp, it
works file and opens up in the XML editor. If I add Test.jnlp.in (the full
name of the file) to the content types, tried again, and it opened right
up. I just cannot have a 'complex' file extension it seems.
So, I guess my question is: is there a way to get this to work?
Alternatively, is there any way to simply turn off content type checking?
I mean, does the XML editor really care what the extension of my file is
so long as it can be parsed as XML? I don't mind having to go to a file
and say "Open with XML editor" each time, if it will actually work.
Thanks a bunch,
|Re: XML Editor content types and 'complex' extensions [message #216708 is a reply to message #216670]
||Thu, 03 July 2008 02:46
|| Nitin Dahyabhai
Registered: July 2009
Eugene Marcotte wrote:|
> So, I guess my question is: is there a way to get this to work?
You might need to ask that one in eclipse.platform.
> Alternatively, is there any way to simply turn off content type
> checking? I mean, does the XML editor really care what the extension of
> my file is so long as it can be parsed as XML? I don't mind having to go
> to a file and say "Open with XML editor" each time, if it will actually
It's an issue we've wrestled with and debated over in the past, but
yes, it really has to care. The editor relies on implementations of
interfaces that can only be registered against content types and
filenames known to us at development time, in this case XML files,
and the numerous filename extensions we can confidently claim
responsibility for. Anything more has to rely on user preferences.
At least until someone thinks of something better.
Eclipse WTP Source Editing
Eclipse WTP, IBM
Powered by FUDForum
. Page generated in 0.01531 seconds