- This topic has 23 replies, 6 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
That’s what I have been telling you. I followed the instructions.
I misinterpreted your ‘steps to reproduce’ as your only steps you took, my mistake.
If this continues with Beta2 please let us know so we can get to the bottom of this. Do you have any plugins like XMen or XMLBuddy that could be causing any ‘in-fighting’ with the MyEclipse XML editor?
Jon,
Just to be sure we’re testing exactly the same thing, can you post the contents of the smallest XML file that demonstrates the issue?
@support-scott wrote:
Jon,
Just to be sure we’re testing exactly the same thing, can you post the contents of the smallest XML file that demonstrates the issue?
Heh.
Granted, not much to validate or tidy, but still, the stuff should pop up. Also doesn’t pop up for any other xml files for me.
-Jon
<?xml version="1.0" encoding="UTF-8"?> <xml-body> </xml-body>@support-scott wrote:
Jon,
I’m glad I asked. Validation is only available on files that explicitly reference a DTD.
Here is the header of my main xml file, which DOES have a DTD.
<?xml version="1.0" standalone="no"?> <!-- $Id: AcceptableUse.xml,v 1.2 2004/06/04 15:56:20 jnials Exp $ --> <!-- $Author: jnials $ --> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "/usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd"> <book> <bookinfo>Now, that got me thinking that maybe it was a problem with using a file system DTD, so I replaced
/usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtdwith
http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtdAfter making the above change, I did not see the validate option, so just to be on the safe side, I stopped and restarted eclipse. Still no validate option.
Also, please note that as a control, I have validated this file many times with jedit.
Sigh. I feel like I am beating a dead horse here. What do I need to do to show you guys it isn’t working?
-Jon
Here is the header of my main xml file, which DOES have a DTD.
Thank you for the specifics, I tried this locally with multiple test files and multiple variations of the header, and they all worked as expected:
<?xml version=”1.0″ standalone=”no”?>
<!– $Id: AcceptableUse.xml,v 1.2 2004/06/04 15:56:20 jnials Exp $ –>
<!– $Author: jnials $ –><!DOCTYPE book PUBLIC “-//OASIS//DTD DocBook XML V4.2//EN”
“http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd”>Now, that got me thinking that maybe it was a problem with using a file system DTD, so I replaced
Maybe changing this to a full url, e.g. file:///xyz may help if you want to continue referecing the local DTD.
Sigh. I feel like I am beating a dead horse here. What do I need to do to show you guys it isn’t working?
Don’t give up, this has to have something to do with your setup as 3 of us with completely different setups have not seen this behavior.
I would encourage you to download a fresh copy of Eclipse 3.0RC2 and MyEclipse 3.8beta1 Manual Installl and install them someplace completely new. Then start Eclipse with the -data arg and specify a clean/new location for a workspace. Once you get that bare install running, try to validate a file and see if the menu option is there. Its possible a plugin you have running is conflicting with our editor or our editor is tripping up on another installed plugin.
Creating a new clean workspace is a must, don’t carry over any old config data, just do a sanity check to make sure that a ‘clean install’ will work.
Jon,
Are you running behind an internet proxy? If so, the proxy is most likely preventing the DTD from being downloaded which is in turn causing validation to fail since it can’t access the DTD.
