Eclipse Community Forums: ServerTools (WTP) » Validating XML with other file suffixes

Home » Language IDEs » ServerTools (WTP) » Validating XML with other file suffixes

Validating XML with other file suffixes [message #162900]

Mon, 06 March 2006 07:31

Eclipse User

I'm sure this should be easy, but I can't figure it out. I need to
validate XML files that have a suffix other than ".xml". These are
well-formed XML documents, I have set up my XML Catalog to point to
their schema, and I have even added the xsi:schemaLocation attribute to
the root element. I have also associated this file suffix with the XML
content type in the preferences dialog. But when I try to "Run
Validation" by right-clicking on the file in the explorer, I get:

Resource /aiml/FrenchAIML/atomique_ed.aiml was not validated because
none of the enabled validators validates that type of resource.
Validation of resource /aiml/FrenchAIML/atomique_ed.aiml is complete.

If I rename the file to have an ".xml" suffix, then I can "Validate XML
File" with no problem.

What do I need to do to get the XML validator to work right in this case?

Re: Validating XML with other file suffixes [message #163004 is a reply to message #162900]

Tue, 07 March 2006 02:48

Eclipse User

I feel your pain. See bug 86385.
The best you can do for now is copy bits of code from xml.core's
plugin.xml into your own plugin.xml and specify you own file extensions.

Please vote to get this fixed. I know I have.

Re: Validating XML with other file suffixes [message #163072 is a reply to message #163004]

Tue, 07 March 2006 08:52

Eclipse User

craig wrote:
> I feel your pain. See bug 86385.
> The best you can do for now is copy bits of code from xml.core's
> plugin.xml into your own plugin.xml and specify you own file extensions.
> Please vote to get this fixed. I know I have.

Thanks! I've voted for it. Here's the link to the bug for anyone else
who wants to support it:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=86385

From reading the bug report I can see that this is a pretty significant
issue. It seems like a pretty fundamental thing about how one would
reasonably expect the validator to work. I think it may have fallen
through the cracks -- after over 1 year it's still marked as "NEW".

Meanwhile, many people are not getting the benefit of all the hard word
that has gone into the XML validator, because of this issue.

(I'm trying to make my vote really heavy. :-)

Previous Topic:	proxy.eclipse.org timeout
Next Topic:	wtp and .properties files, specifically log4j

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 07:41:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter