[grassol]

I’m using MyEclipse 6.01GA with Eclipse 3.3.1.1 on a Vista machine.

I’m sitting behind a firewall, so i have the proxy configuration activated (Window -> Preferences -> General -> Network Connections)

I have ALL validation turned off in the MyEclipse Validation Preferences (Window -> Preferences -> MyEclipse -> Validation).

When i open a xml file, for example a pom.xml from maven, the Popup-Dialog with userid and password for the proxy appears several times. That’s really annoying…
MyEclipse tries to access the schemaLocation of the maven.xsd.

When I change the Network Connection back to “Direct connection to the internet”, MyEclipse also tries to load the maven.xsd.

So there seems to be something broken with the validation…

Any hints?

Thanx
Oliver

[Loyal Water]

Can you make sure that under Project > Properties you haven’t overridden the workbench settings for the project ?
If you haven’t overridden it, it does look like an issue that the validator still tries to load the schema.

As a workaround, you should manually add the schema to the XML catalog so the validator uses that local copy instead of the internet one. You can add the schema to the XML catalog by going to Windows > Prefs > MyEclipse > File and Editors > XML Catalog > Add. You just need to make sure the URI that is used to reg the schema is the same you use in your file… it will match them, and use the catalog copy.

[grassol]

I checked that, i don’t have the project preferences overridden.

I used the workaround for the maven-xm. But this is annoying, cause you will never know, which xml-file the user will open.

Any ideas, when this issue (if it is really one) will be fixed?

Thanx
Oliver

[Loyal Water]

Oliver,
This is a bug which has already been filed. I would mostly be fixed for the next MyEclipse release. Thank you for reporting this issue.

[grassol]

This message has not been recovered.

[grassol]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Robert Varga]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Robert Varga]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Brian Fernandes]

Robert,

Could you please paste the header of your spring beans config here (part upto <beans>)? I’m trying to replicate this locally and would like to make sure we test the fix for your particular use case with the same DTD referenced.

Is this only happening for your spring beans config file or for other XML files as well?

Thanks.

[Robert Varga]

@Support-Brian wrote:

Robert,

Could you please paste the header of your spring beans config here (part upto <beans>)? I’m trying to replicate this locally and would like to make sure we test the fix for your particular use case with the same DTD referenced.

Is this only happening for your spring beans config file or for other XML files as well?

Thanks.

As far as I remember, it was only the Spring bean configuration files, at least that was what was really noticeable because the Spring Builder validates them pretty frequently. At least that was the only connection I noticed on the firewall.

The header of a file (I think all files in the project have the same header):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC
   "-//SPRING//DTD BEAN 2.0//EN"
  "http://www.springframework.org/dtd/spring-beans-2.0.dtd"
>
<beans>

Thanks and best regards,

Robert

[Brian Fernandes]

Robert,

Thanks for the report. I was able to replicate the issue easily AND additionally verify that it has already been fixed in the upcoming 6.5M1 release.

Once that is out, it would be great to get your feedback on this issue.

We appreciate your support, thanks again.

[Author]

Posts