Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » XML Schema Definition (XSD) » attribute reference unresolved - must be basic answer
attribute reference unresolved - must be basic answer [message #59230] Wed, 20 April 2005 14:54 Go to next message
Eclipse User
Originally posted by: spam.no-thanks.org

Hi,
during installation of the eclipse subversion plugin, I 'inherited' the
XSD plugin too. Now my eclipse 'problems' list is showing errors in
schemas in my project.

I have googled and searched this mailing list without finding a
solution. Perhaps someone can recognise what basic mistake I'm making -
and I'm sure it must be basic :(

XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang' is
unresolved

comes from this line of schema:

<xs:attribute ref="xml:lang" default="en"/>

which imports the schema mentioned in the error msg like so:

<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>

I have actually downloaded the xml.xsd schema and placed it in the same
directory, and I have this directory loaded as a class folder resource
in the .classpath for my project like so:

<classpathentry kind="lib" path="docs/Design/schemas"/>


Thanks
Adam
Re: attribute reference unresolved - must be basic answer [message #59282 is a reply to message #59230] Wed, 20 April 2005 18:49 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

I tried this in a sample and it loaded fine. It sure looks correct.
Maybe the problem is that your application doesn't have access to the
web in order to load the schema...


adam wrote:

> Hi,
> during installation of the eclipse subversion plugin, I 'inherited'
> the XSD plugin too. Now my eclipse 'problems' list is showing errors
> in schemas in my project.
>
> I have googled and searched this mailing list without finding a
> solution. Perhaps someone can recognise what basic mistake I'm making
> - and I'm sure it must be basic :(
>
> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
> is unresolved
>
> comes from this line of schema:
>
> <xs:attribute ref="xml:lang" default="en"/>
>
> which imports the schema mentioned in the error msg like so:
>
> <xs:import namespace="http://www.w3.org/XML/1998/namespace"
> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
>
> I have actually downloaded the xml.xsd schema and placed it in the
> same directory, and I have this directory loaded as a class folder
> resource in the .classpath for my project like so:
>
> <classpathentry kind="lib" path="docs/Design/schemas"/>
>
>
> Thanks
> Adam
Re: attribute reference unresolved - must be basic answer [message #59336 is a reply to message #59282] Thu, 21 April 2005 11:31 Go to previous messageGo to next message
Eclipse User
Originally posted by: spam.no-thanks.org

Hi Ed,

I'm definitely online all the time - but I do have a firewall - what
protocol does the import use? If it's HTTP then there's no problem. I
know I have problems with stuff like instant messenger.

How can I force a try in Eclipse? Will a refresh do it?


Adam

Ed Merks wrote:
> Adam,
>
> I tried this in a sample and it loaded fine. It sure looks correct.
> Maybe the problem is that your application doesn't have access to the
> web in order to load the schema...
Re: attribute reference unresolved - must be basic answer [message #59355 is a reply to message #59336] Thu, 21 April 2005 11:41 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

Your schema location was http.

I'm really not sure what's doing causing your schema to be validated
automatically (XSD doesn't provide such support) nor what would make it
try again. Certainly changing the time stamp of the file and refreshing
should do the trick...


adam wrote:

> Hi Ed,
>
> I'm definitely online all the time - but I do have a firewall - what
> protocol does the import use? If it's HTTP then there's no problem. I
> know I have problems with stuff like instant messenger.
>
> How can I force a try in Eclipse? Will a refresh do it?
>
>
> Adam
>
> Ed Merks wrote:
>
>> Adam,
>>
>> I tried this in a sample and it loaded fine. It sure looks correct.
>> Maybe the problem is that your application doesn't have access to the
>> web in order to load the schema...
>
Re: attribute reference unresolved - must be basic answer [message #59597 is a reply to message #59355] Mon, 25 April 2005 15:50 Go to previous messageGo to next message
Eclipse User
Originally posted by: spam.no-thanks.org

But it's an XSD error in my Eclipse 'Problems' view with the text:

XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang' is
unresolved

Is this not the XSD plugin in action?

Ed Merks wrote:
> Adam,
>
> Your schema location was http.
> I'm really not sure what's doing causing your schema to be validated
> automatically (XSD doesn't provide such support) nor what would make it
> try again. Certainly changing the time stamp of the file and refreshing
> should do the trick...
Re: attribute reference unresolved - must be basic answer [message #59619 is a reply to message #59597] Mon, 25 April 2005 20:27 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

That's certainly a message created by the XSD model, but XSD provides no
automated validator that produces this message. Opening a .xsd with the
Sample XML Schema Editor will do such validation, but when I try to do
that with your example, it works fine. Have you tried opening the
example with the Sample editor provided by XSD?


adam wrote:

> But it's an XSD error in my Eclipse 'Problems' view with the text:
>
> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
> is unresolved
>
> Is this not the XSD plugin in action?
>
> Ed Merks wrote:
>
>> Adam,
>>
>> Your schema location was http.
>> I'm really not sure what's doing causing your schema to be validated
>> automatically (XSD doesn't provide such support) nor what would make
>> it try again. Certainly changing the time stamp of the file and
>> refreshing should do the trick...
>
Re: attribute reference unresolved - must be basic answer [message #59713 is a reply to message #59619] Tue, 26 April 2005 12:40 Go to previous messageGo to next message
Eclipse User
Originally posted by: spam.no-thanks.org

OK, truth is, I can work fine with the schema, but these errors in
Eclipse (which seem to be invalid) are bugging me. I would like to get
rid of them without filtering out errors XML errors.

There are warnings too:
XSD: The location 'http://www.w3.org/2001/xml.xsd' has not been resolved

I can't see from looking in the help why XSD is outputting any errors or
warnings at all or what exactly Eclipse is doing when it finds .xsd
files while building the project.

Eclipse has associated .xsd file with the Sample XSD Editor and looking
at the schema, Ecilpse shows the warnings and errors at the appropriate
lines.

This seems to contradict your statement about XSD providing no autmoated
validator, surely?


Adam




Ed Merks wrote:
> That's certainly a message created by the XSD model, but XSD provides no
> automated validator that produces this message. Opening a .xsd with the
> Sample XML Schema Editor will do such validation, but when I try to do
> that with your example, it works fine. Have you tried opening the
> example with the Sample editor provided by XSD?
>
> adam wrote:
>
>> But it's an XSD error in my Eclipse 'Problems' view with the text:
>>
>> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
>> is unresolved
>>
>> Is this not the XSD plugin in action?
Re: attribute reference unresolved - must be basic answer [message #59736 is a reply to message #59713] Tue, 26 April 2005 15:24 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

When you open the editor, the editor will validate your schema. When I
try a sample schema with your example in it, I don't get errors, so I
can't reproduce the problem. You'll just have to take my word for the
fact that I've not written anything that will automatically validate the
schema as part of a build and that I know nothing about that. If you
want to send a complete schema example for me to try, I can do that...


adam wrote:

> OK, truth is, I can work fine with the schema, but these errors in
> Eclipse (which seem to be invalid) are bugging me. I would like to get
> rid of them without filtering out errors XML errors.
>
> There are warnings too:
> XSD: The location 'http://www.w3.org/2001/xml.xsd' has not been
> resolved
>
> I can't see from looking in the help why XSD is outputting any errors
> or warnings at all or what exactly Eclipse is doing when it finds .xsd
> files while building the project.
>
> Eclipse has associated .xsd file with the Sample XSD Editor and
> looking at the schema, Ecilpse shows the warnings and errors at the
> appropriate lines.
>
> This seems to contradict your statement about XSD providing no
> autmoated validator, surely?
>
>
> Adam
>
>
>
>
> Ed Merks wrote:
>
>> That's certainly a message created by the XSD model, but XSD provides
>> no automated validator that produces this message. Opening a .xsd
>> with the Sample XML Schema Editor will do such validation, but when I
>> try to do that with your example, it works fine. Have you tried
>> opening the example with the Sample editor provided by XSD?
>>
>> adam wrote:
>>
>>> But it's an XSD error in my Eclipse 'Problems' view with the text:
>>>
>>> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
>>> is unresolved
>>>
>>> Is this not the XSD plugin in action?
>>
Re: attribute reference unresolved - must be basic answer [message #60070 is a reply to message #59736] Thu, 28 April 2005 11:17 Go to previous messageGo to next message
Eclipse User
Originally posted by: spam.no-thanks.org

Ed,
I totally believe you when you say you didn't code it, but what I am
trying to elucidate is why it is doing that validation OR why it isn't
including the other schemas as it should when it does validate.

Unfortunately I am completely in the dark about the way that Eclipse is
behaving and I'm hoping to get the info from you or someone here! Do you
think I would have more success on the eclipse user list?

Id gladly send you the complete schema set just to test it quickly but I
think the problem is probably not with the schema. My email address
(once you remove the anti-spam bits) is

adam dot hardy :) bbc dot co dot uk

Thanks!

Ed Merks wrote:
> Adam,
>
> When you open the editor, the editor will validate your schema. When I
> try a sample schema with your example in it, I don't get errors, so I
> can't reproduce the problem. You'll just have to take my word for the
> fact that I've not written anything that will automatically validate the
> schema as part of a build and that I know nothing about that. If you
> want to send a complete schema example for me to try, I can do that...
Re: attribute reference unresolved - must be basic answer [message #60094 is a reply to message #60070] Thu, 28 April 2005 11:49 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

You mentioned "the eclipse subversion" plugin. I would assume that
"they" are providing this behavior. I am certainly willing to try out
your schemas (feel free to send them directly to my e-mail) but I can do
little about the way other plugins use XSD, so your question should
really be directed to the folks who implemented this automatic
validation support. It's sometimes the case that a schema in isolation
is invalid but when included in some context becomes valid, or vice
versa, so simply validating schemas by scanning for them and validating
each separately is a design with some issues... Your problem really
sounds like an inability to fetch the schema from the http location...


adam wrote:

> Ed,
> I totally believe you when you say you didn't code it, but what I am
> trying to elucidate is why it is doing that validation OR why it isn't
> including the other schemas as it should when it does validate.
>
> Unfortunately I am completely in the dark about the way that Eclipse
> is behaving and I'm hoping to get the info from you or someone here!
> Do you think I would have more success on the eclipse user list?
>
> Id gladly send you the complete schema set just to test it quickly but
> I think the problem is probably not with the schema. My email address
> (once you remove the anti-spam bits) is
>
> adam dot hardy :) bbc dot co dot uk
>
> Thanks!
>
> Ed Merks wrote:
>
>> Adam,
>>
>> When you open the editor, the editor will validate your schema. When
>> I try a sample schema with your example in it, I don't get errors, so
>> I can't reproduce the problem. You'll just have to take my word for
>> the fact that I've not written anything that will automatically
>> validate the schema as part of a build and that I know nothing about
>> that. If you want to send a complete schema example for me to try, I
>> can do that...
>
Re: attribute reference unresolved - must be basic answer [message #60118 is a reply to message #60094] Thu, 28 April 2005 12:56 Go to previous messageGo to next message
Eclipse User
Originally posted by: spam.no-thanks.org

OK, Ed, I just disabled the subversion plugin.

I then cleaned my project and got all problem entries to disappear. I
then opened one of my schemas, and Eclipse gave me the progress bar with
the status message "bundleentry://169/ xxxxxxx" and then it failed and
showed the XSD errors.

I didn't recognise the URL in the status message, not even the protocol!

Does this tell you anything?

Thanks
Adam

Ed Merks wrote:
> Adam,
>
> You mentioned "the eclipse subversion" plugin. I would assume that
> "they" are providing this behavior. I am certainly willing to try out
> your schemas (feel free to send them directly to my e-mail) but I can do
> little about the way other plugins use XSD, so your question should
> really be directed to the folks who implemented this automatic
> validation support. It's sometimes the case that a schema in isolation
> is invalid but when included in some context becomes valid, or vice
> versa, so simply validating schemas by scanning for them and validating
> each separately is a design with some issues... Your problem really
> sounds like an inability to fetch the schema from the http location...
Re: attribute reference unresolved - must be basic answer [message #60142 is a reply to message #60118] Thu, 28 April 2005 13:02 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Adam,

Did you disable the XSD plugin as well? A bundleentry scheme is
Eclipse's way to referencing something in an installed plugin. XSD uses
this access the cached schemas...


adam wrote:

> OK, Ed, I just disabled the subversion plugin.
>
> I then cleaned my project and got all problem entries to disappear. I
> then opened one of my schemas, and Eclipse gave me the progress bar
> with the status message "bundleentry://169/ xxxxxxx" and then it
> failed and showed the XSD errors.
>
> I didn't recognise the URL in the status message, not even the protocol!
>
> Does this tell you anything?
>
> Thanks
> Adam
>
> Ed Merks wrote:
>
>> Adam,
>>
>> You mentioned "the eclipse subversion" plugin. I would assume that
>> "they" are providing this behavior. I am certainly willing to try
>> out your schemas (feel free to send them directly to my e-mail) but I
>> can do little about the way other plugins use XSD, so your question
>> should really be directed to the folks who implemented this automatic
>> validation support. It's sometimes the case that a schema in
>> isolation is invalid but when included in some context becomes valid,
>> or vice versa, so simply validating schemas by scanning for them and
>> validating each separately is a design with some issues... Your
>> problem really sounds like an inability to fetch the schema from the
>> http location...
>
Re: attribute reference unresolved - must be basic answer [message #60165 is a reply to message #60142] Thu, 28 April 2005 13:49 Go to previous message
Eclipse User
Originally posted by: spam.no-thanks.org

I just disabled Subversion. I didn't see any way in the 'Product
Configuration' menu to disable XSD. Right from the start I could have
just removed the xsd plugin, but I was kind of hoping I would get some
benefit from it later.

I got rid of XMLSpy on the basis that it was a memory hog and not open
source, and then I discovered that the xsd plugin had the editor. Did
those schemas arrive again properly?


Ed Merks wrote:
> Adam,
>
> Did you disable the XSD plugin as well? A bundleentry scheme is
> Eclipse's way to referencing something in an installed plugin. XSD uses
> this access the cached schemas...
>
>
> adam wrote:
>
>> OK, Ed, I just disabled the subversion plugin.
>>
Re: attribute reference unresolved - must be basic answer [message #594779 is a reply to message #59230] Wed, 20 April 2005 18:49 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

I tried this in a sample and it loaded fine. It sure looks correct.
Maybe the problem is that your application doesn't have access to the
web in order to load the schema...


adam wrote:

> Hi,
> during installation of the eclipse subversion plugin, I 'inherited'
> the XSD plugin too. Now my eclipse 'problems' list is showing errors
> in schemas in my project.
>
> I have googled and searched this mailing list without finding a
> solution. Perhaps someone can recognise what basic mistake I'm making
> - and I'm sure it must be basic :(
>
> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
> is unresolved
>
> comes from this line of schema:
>
> <xs:attribute ref="xml:lang" default="en"/>
>
> which imports the schema mentioned in the error msg like so:
>
> <xs:import namespace="http://www.w3.org/XML/1998/namespace"
> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
>
> I have actually downloaded the xml.xsd schema and placed it in the
> same directory, and I have this directory loaded as a class folder
> resource in the .classpath for my project like so:
>
> <classpathentry kind="lib" path="docs/Design/schemas"/>
>
>
> Thanks
> Adam
Re: attribute reference unresolved - must be basic answer [message #594805 is a reply to message #59282] Thu, 21 April 2005 11:31 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
Hi Ed,

I'm definitely online all the time - but I do have a firewall - what
protocol does the import use? If it's HTTP then there's no problem. I
know I have problems with stuff like instant messenger.

How can I force a try in Eclipse? Will a refresh do it?


Adam

Ed Merks wrote:
> Adam,
>
> I tried this in a sample and it loaded fine. It sure looks correct.
> Maybe the problem is that your application doesn't have access to the
> web in order to load the schema...
Re: attribute reference unresolved - must be basic answer [message #594816 is a reply to message #59336] Thu, 21 April 2005 11:41 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

Your schema location was http.

I'm really not sure what's doing causing your schema to be validated
automatically (XSD doesn't provide such support) nor what would make it
try again. Certainly changing the time stamp of the file and refreshing
should do the trick...


adam wrote:

> Hi Ed,
>
> I'm definitely online all the time - but I do have a firewall - what
> protocol does the import use? If it's HTTP then there's no problem. I
> know I have problems with stuff like instant messenger.
>
> How can I force a try in Eclipse? Will a refresh do it?
>
>
> Adam
>
> Ed Merks wrote:
>
>> Adam,
>>
>> I tried this in a sample and it loaded fine. It sure looks correct.
>> Maybe the problem is that your application doesn't have access to the
>> web in order to load the schema...
>
Re: attribute reference unresolved - must be basic answer [message #594931 is a reply to message #59355] Mon, 25 April 2005 15:50 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
But it's an XSD error in my Eclipse 'Problems' view with the text:

XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang' is
unresolved

Is this not the XSD plugin in action?

Ed Merks wrote:
> Adam,
>
> Your schema location was http.
> I'm really not sure what's doing causing your schema to be validated
> automatically (XSD doesn't provide such support) nor what would make it
> try again. Certainly changing the time stamp of the file and refreshing
> should do the trick...
Re: attribute reference unresolved - must be basic answer [message #594941 is a reply to message #59597] Mon, 25 April 2005 20:27 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

That's certainly a message created by the XSD model, but XSD provides no
automated validator that produces this message. Opening a .xsd with the
Sample XML Schema Editor will do such validation, but when I try to do
that with your example, it works fine. Have you tried opening the
example with the Sample editor provided by XSD?


adam wrote:

> But it's an XSD error in my Eclipse 'Problems' view with the text:
>
> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
> is unresolved
>
> Is this not the XSD plugin in action?
>
> Ed Merks wrote:
>
>> Adam,
>>
>> Your schema location was http.
>> I'm really not sure what's doing causing your schema to be validated
>> automatically (XSD doesn't provide such support) nor what would make
>> it try again. Certainly changing the time stamp of the file and
>> refreshing should do the trick...
>
Re: attribute reference unresolved - must be basic answer [message #594985 is a reply to message #59619] Tue, 26 April 2005 12:40 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
OK, truth is, I can work fine with the schema, but these errors in
Eclipse (which seem to be invalid) are bugging me. I would like to get
rid of them without filtering out errors XML errors.

There are warnings too:
XSD: The location 'http://www.w3.org/2001/xml.xsd' has not been resolved

I can't see from looking in the help why XSD is outputting any errors or
warnings at all or what exactly Eclipse is doing when it finds .xsd
files while building the project.

Eclipse has associated .xsd file with the Sample XSD Editor and looking
at the schema, Ecilpse shows the warnings and errors at the appropriate
lines.

This seems to contradict your statement about XSD providing no autmoated
validator, surely?


Adam




Ed Merks wrote:
> That's certainly a message created by the XSD model, but XSD provides no
> automated validator that produces this message. Opening a .xsd with the
> Sample XML Schema Editor will do such validation, but when I try to do
> that with your example, it works fine. Have you tried opening the
> example with the Sample editor provided by XSD?
>
> adam wrote:
>
>> But it's an XSD error in my Eclipse 'Problems' view with the text:
>>
>> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
>> is unresolved
>>
>> Is this not the XSD plugin in action?
Re: attribute reference unresolved - must be basic answer [message #594992 is a reply to message #59713] Tue, 26 April 2005 15:24 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

When you open the editor, the editor will validate your schema. When I
try a sample schema with your example in it, I don't get errors, so I
can't reproduce the problem. You'll just have to take my word for the
fact that I've not written anything that will automatically validate the
schema as part of a build and that I know nothing about that. If you
want to send a complete schema example for me to try, I can do that...


adam wrote:

> OK, truth is, I can work fine with the schema, but these errors in
> Eclipse (which seem to be invalid) are bugging me. I would like to get
> rid of them without filtering out errors XML errors.
>
> There are warnings too:
> XSD: The location 'http://www.w3.org/2001/xml.xsd' has not been
> resolved
>
> I can't see from looking in the help why XSD is outputting any errors
> or warnings at all or what exactly Eclipse is doing when it finds .xsd
> files while building the project.
>
> Eclipse has associated .xsd file with the Sample XSD Editor and
> looking at the schema, Ecilpse shows the warnings and errors at the
> appropriate lines.
>
> This seems to contradict your statement about XSD providing no
> autmoated validator, surely?
>
>
> Adam
>
>
>
>
> Ed Merks wrote:
>
>> That's certainly a message created by the XSD model, but XSD provides
>> no automated validator that produces this message. Opening a .xsd
>> with the Sample XML Schema Editor will do such validation, but when I
>> try to do that with your example, it works fine. Have you tried
>> opening the example with the Sample editor provided by XSD?
>>
>> adam wrote:
>>
>>> But it's an XSD error in my Eclipse 'Problems' view with the text:
>>>
>>> XSD: Attribute reference 'http://www.w3.org/XML/1998/namespace#lang'
>>> is unresolved
>>>
>>> Is this not the XSD plugin in action?
>>
Re: attribute reference unresolved - must be basic answer [message #595141 is a reply to message #59736] Thu, 28 April 2005 11:17 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
Ed,
I totally believe you when you say you didn't code it, but what I am
trying to elucidate is why it is doing that validation OR why it isn't
including the other schemas as it should when it does validate.

Unfortunately I am completely in the dark about the way that Eclipse is
behaving and I'm hoping to get the info from you or someone here! Do you
think I would have more success on the eclipse user list?

Id gladly send you the complete schema set just to test it quickly but I
think the problem is probably not with the schema. My email address
(once you remove the anti-spam bits) is

adam dot hardy :) bbc dot co dot uk

Thanks!

Ed Merks wrote:
> Adam,
>
> When you open the editor, the editor will validate your schema. When I
> try a sample schema with your example in it, I don't get errors, so I
> can't reproduce the problem. You'll just have to take my word for the
> fact that I've not written anything that will automatically validate the
> schema as part of a build and that I know nothing about that. If you
> want to send a complete schema example for me to try, I can do that...
Re: attribute reference unresolved - must be basic answer [message #595152 is a reply to message #60070] Thu, 28 April 2005 11:49 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

You mentioned "the eclipse subversion" plugin. I would assume that
"they" are providing this behavior. I am certainly willing to try out
your schemas (feel free to send them directly to my e-mail) but I can do
little about the way other plugins use XSD, so your question should
really be directed to the folks who implemented this automatic
validation support. It's sometimes the case that a schema in isolation
is invalid but when included in some context becomes valid, or vice
versa, so simply validating schemas by scanning for them and validating
each separately is a design with some issues... Your problem really
sounds like an inability to fetch the schema from the http location...


adam wrote:

> Ed,
> I totally believe you when you say you didn't code it, but what I am
> trying to elucidate is why it is doing that validation OR why it isn't
> including the other schemas as it should when it does validate.
>
> Unfortunately I am completely in the dark about the way that Eclipse
> is behaving and I'm hoping to get the info from you or someone here!
> Do you think I would have more success on the eclipse user list?
>
> Id gladly send you the complete schema set just to test it quickly but
> I think the problem is probably not with the schema. My email address
> (once you remove the anti-spam bits) is
>
> adam dot hardy :) bbc dot co dot uk
>
> Thanks!
>
> Ed Merks wrote:
>
>> Adam,
>>
>> When you open the editor, the editor will validate your schema. When
>> I try a sample schema with your example in it, I don't get errors, so
>> I can't reproduce the problem. You'll just have to take my word for
>> the fact that I've not written anything that will automatically
>> validate the schema as part of a build and that I know nothing about
>> that. If you want to send a complete schema example for me to try, I
>> can do that...
>
Re: attribute reference unresolved - must be basic answer [message #595163 is a reply to message #60094] Thu, 28 April 2005 12:56 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
OK, Ed, I just disabled the subversion plugin.

I then cleaned my project and got all problem entries to disappear. I
then opened one of my schemas, and Eclipse gave me the progress bar with
the status message "bundleentry://169/ xxxxxxx" and then it failed and
showed the XSD errors.

I didn't recognise the URL in the status message, not even the protocol!

Does this tell you anything?

Thanks
Adam

Ed Merks wrote:
> Adam,
>
> You mentioned "the eclipse subversion" plugin. I would assume that
> "they" are providing this behavior. I am certainly willing to try out
> your schemas (feel free to send them directly to my e-mail) but I can do
> little about the way other plugins use XSD, so your question should
> really be directed to the folks who implemented this automatic
> validation support. It's sometimes the case that a schema in isolation
> is invalid but when included in some context becomes valid, or vice
> versa, so simply validating schemas by scanning for them and validating
> each separately is a design with some issues... Your problem really
> sounds like an inability to fetch the schema from the http location...
Re: attribute reference unresolved - must be basic answer [message #595167 is a reply to message #60118] Thu, 28 April 2005 13:02 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Adam,

Did you disable the XSD plugin as well? A bundleentry scheme is
Eclipse's way to referencing something in an installed plugin. XSD uses
this access the cached schemas...


adam wrote:

> OK, Ed, I just disabled the subversion plugin.
>
> I then cleaned my project and got all problem entries to disappear. I
> then opened one of my schemas, and Eclipse gave me the progress bar
> with the status message "bundleentry://169/ xxxxxxx" and then it
> failed and showed the XSD errors.
>
> I didn't recognise the URL in the status message, not even the protocol!
>
> Does this tell you anything?
>
> Thanks
> Adam
>
> Ed Merks wrote:
>
>> Adam,
>>
>> You mentioned "the eclipse subversion" plugin. I would assume that
>> "they" are providing this behavior. I am certainly willing to try
>> out your schemas (feel free to send them directly to my e-mail) but I
>> can do little about the way other plugins use XSD, so your question
>> should really be directed to the folks who implemented this automatic
>> validation support. It's sometimes the case that a schema in
>> isolation is invalid but when included in some context becomes valid,
>> or vice versa, so simply validating schemas by scanning for them and
>> validating each separately is a design with some issues... Your
>> problem really sounds like an inability to fetch the schema from the
>> http location...
>
Re: attribute reference unresolved - must be basic answer [message #595177 is a reply to message #60142] Thu, 28 April 2005 13:49 Go to previous message
adam is currently offline adam
Messages: 7
Registered: July 2009
Junior Member
I just disabled Subversion. I didn't see any way in the 'Product
Configuration' menu to disable XSD. Right from the start I could have
just removed the xsd plugin, but I was kind of hoping I would get some
benefit from it later.

I got rid of XMLSpy on the basis that it was a memory hog and not open
source, and then I discovered that the xsd plugin had the editor. Did
those schemas arrive again properly?


Ed Merks wrote:
> Adam,
>
> Did you disable the XSD plugin as well? A bundleentry scheme is
> Eclipse's way to referencing something in an installed plugin. XSD uses
> this access the cached schemas...
>
>
> adam wrote:
>
>> OK, Ed, I just disabled the subversion plugin.
>>
Previous Topic:Type derivation results in duplicate particles
Next Topic:getContent
Goto Forum:
  


Current Time: Wed Oct 22 22:33:43 GMT 2014

Powered by FUDForum. Page generated in 0.02457 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software