| More namespace help [message #43644] |
Wed, 05 May 2004 13:10  |
Eclipse User |
|
|
|
Ed,
More info on the problem I was having below... I'm not sure if the
schema location issue in the imports is related to this issue or not. I
mentioned in the thread below that all my cross schema references are wrong.
It is not just that they are wrong... but when the schema gets written out,
the references have the wrong namespace!! So, if schema A imports schema B
and schema C... and an Element in A has a type attribute from schema C...
when A gets written out, Element A's type attriubte is B:type and no xmlns
declaration is created for C.
I am completely lost at this point. I'm breakpointing all over the
place and all the references look correct right up until the save. After
the save all the references get reset to placeholder entities from the
incorrect schema. I do get the following in the log as a warning : XSD:
There is no xmlns declaration for namespace
'http://schemas.xmlsoap.org/soap/encoding' as well as XSD: The location
'soap_encoding.xsd' has not been resolved... also as a warning.
Unfortunately I don't have any schemas to send as I'm getting here via a
conversion process from our old proprietary xsd metamodel to your xsd
metamodel. I'm willing to send them off-line if you think they'll help, but
they are very UUID based making it much harder to read!!
HELP!!
thanks,
lp
|
|
|
|
| Re: More namespace help [message #43767 is a reply to message #43707] |
Wed, 05 May 2004 17:16  |
| Eclipse User |
|
|
|
Ed,
I sent you a producible test off line.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:409933E2.6F67A4BB@ca.ibm.com...
> Lance,
>
> I'll definitely need something that reproduces the problem to provide
decent
> help.
>
>
> Lance Phillips wrote:
>
> > Ed,
> > More info on the problem I was having below... I'm not sure if the
> > schema location issue in the imports is related to this issue or not. I
> > mentioned in the thread below that all my cross schema references are
wrong.
> > It is not just that they are wrong... but when the schema gets written
out,
> > the references have the wrong namespace!! So, if schema A imports
schema B
> > and schema C... and an Element in A has a type attribute from schema
C...
> > when A gets written out, Element A's type attriubte is B:type and no
xmlns
> > declaration is created for C.
> > I am completely lost at this point. I'm breakpointing all over the
> > place and all the references look correct right up until the save.
After
> > the save all the references get reset to placeholder entities from the
> > incorrect schema. I do get the following in the log as a warning : XSD:
> > There is no xmlns declaration for namespace
> > 'http://schemas.xmlsoap.org/soap/encoding' as well as XSD: The location
> > 'soap_encoding.xsd' has not been resolved... also as a warning.
> > Unfortunately I don't have any schemas to send as I'm getting here
via a
> > conversion process from our old proprietary xsd metamodel to your xsd
> > metamodel. I'm willing to send them off-line if you think they'll help,
but
> > they are very UUID based making it much harder to read!!
> >
> > HELP!!
> >
> > thanks,
> >
> > lp
>
|
|
|
| Re: More namespace help [message #586746 is a reply to message #43644] |
Wed, 05 May 2004 14:35 |
| Eclipse User |
|
|
|
Lance,
I'll definitely need something that reproduces the problem to provide decent
help.
Lance Phillips wrote:
> Ed,
> More info on the problem I was having below... I'm not sure if the
> schema location issue in the imports is related to this issue or not. I
> mentioned in the thread below that all my cross schema references are wrong.
> It is not just that they are wrong... but when the schema gets written out,
> the references have the wrong namespace!! So, if schema A imports schema B
> and schema C... and an Element in A has a type attribute from schema C...
> when A gets written out, Element A's type attriubte is B:type and no xmlns
> declaration is created for C.
> I am completely lost at this point. I'm breakpointing all over the
> place and all the references look correct right up until the save. After
> the save all the references get reset to placeholder entities from the
> incorrect schema. I do get the following in the log as a warning : XSD:
> There is no xmlns declaration for namespace
> 'http://schemas.xmlsoap.org/soap/encoding' as well as XSD: The location
> 'soap_encoding.xsd' has not been resolved... also as a warning.
> Unfortunately I don't have any schemas to send as I'm getting here via a
> conversion process from our old proprietary xsd metamodel to your xsd
> metamodel. I'm willing to send them off-line if you think they'll help, but
> they are very UUID based making it much harder to read!!
>
> HELP!!
>
> thanks,
>
> lp
|
|
|
| Re: More namespace help [message #586766 is a reply to message #43707] |
Wed, 05 May 2004 17:16 |
| Eclipse User |
|
|
|
Ed,
I sent you a producible test off line.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:409933E2.6F67A4BB@ca.ibm.com...
> Lance,
>
> I'll definitely need something that reproduces the problem to provide
decent
> help.
>
>
> Lance Phillips wrote:
>
> > Ed,
> > More info on the problem I was having below... I'm not sure if the
> > schema location issue in the imports is related to this issue or not. I
> > mentioned in the thread below that all my cross schema references are
wrong.
> > It is not just that they are wrong... but when the schema gets written
out,
> > the references have the wrong namespace!! So, if schema A imports
schema B
> > and schema C... and an Element in A has a type attribute from schema
C...
> > when A gets written out, Element A's type attriubte is B:type and no
xmlns
> > declaration is created for C.
> > I am completely lost at this point. I'm breakpointing all over the
> > place and all the references look correct right up until the save.
After
> > the save all the references get reset to placeholder entities from the
> > incorrect schema. I do get the following in the log as a warning : XSD:
> > There is no xmlns declaration for namespace
> > 'http://schemas.xmlsoap.org/soap/encoding' as well as XSD: The location
> > 'soap_encoding.xsd' has not been resolved... also as a warning.
> > Unfortunately I don't have any schemas to send as I'm getting here
via a
> > conversion process from our old proprietary xsd metamodel to your xsd
> > metamodel. I'm willing to send them off-line if you think they'll help,
but
> > they are very UUID based making it much harder to read!!
> >
> > HELP!!
> >
> > thanks,
> >
> > lp
>
|
|
|
Powered by
FUDForum. Page generated in 0.03366 seconds
Home