You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <bi...@basistech.com> on 2007/10/10 00:45:47 UTC
True or false: embedded schemata need to be imported?
-----Original Message-----
From: Mindreef Support [mailto:support@mindreef.com]
Sent: Tuesday, October 09, 2007 5:01 PM
To: Benson Margulies
Subject: [issue #QSU-61718-589]: Validation errors that don't make sense
to me
Hi Benson,
Thanks for sending the WSDL.
Issue #1: When you're on the overview page, you'll see just one error
line with XSD Schema Validation highlighted. Click on that line, or
click the red "5 failures" link on the top right and you'll get results
filtered for just the 5 failures. If the top error is expanded, you
might need to scroll down to see all five.
I see five on both SOAPscope 5.3 and SOAPscope Workstation 6.0.
Issue #2: I showed this to one of our developers. When your WSDL
includes multiple schema blocks, you need "include" statements for each
schema. You don't need to provide locations because the schemas are
already in the WSDL. This error message points out a basic ambiguity
between WSDL and Schema, and potential interop problems depending on how
your SOAP toolkit is implemented. According to XSD Schema, you must
import a schema in order to use it. This is entirely independent from
the WSDL spec.
I hope this helps.
Carol Tyler, Mindreef Support
On Tue, 09 Oct 2007 09:29:32 -0400, bim2007@basistech.com wrote:
> Issue #1:
>
> Top-level result from analysis with Mindreef Basic Diagnosis Results
> says '5 failures'.
>
> Only one failure is reported.
>
> Issue #2: the failure makes no sense to me. I don't know what all this
> 'fragment' business is about, but I see no reason why the namespace in
> question is 'not referencable' from the place it is referenced from.
All
> the schemas are included in-line.
>
>
> Schema validation error on node xsd:element
> Error resolving component 'ns1:Name'. It was detected that 'ns1:Name'
is
> in namespace 'http://rnm.basistech.com', but components from this
> namespace are not referenceable from schema document
>
'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082'.
> If this is the incorrect namespace, perhaps the prefix of 'ns1:Name'
> needs to be changed. If this is the correct namespace, then an
> appropriate 'import' tag should be added to
>
'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082'.
RE: True or false: embedded schemata need to be imported?
Posted by Benson Margulies <bi...@basistech.com>.
Then we got a compliance problem.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, October 10, 2007 6:06 PM
> To: cxf-user@incubator.apache.org
> Cc: Benson Margulies
> Subject: Re: True or false: embedded schemata need to be imported?
>
>
> If an embedded schema with one targetNamespace references
types/elements
> in an embedded schema in another targetNamespace, then yes, the other
> schema needs to be imported.
>
> Dan
>
>
> On Tuesday 09 October 2007, Benson Margulies wrote:
> > -----Original Message-----
> > From: Mindreef Support [mailto:support@mindreef.com]
> > Sent: Tuesday, October 09, 2007 5:01 PM
> > To: Benson Margulies
> > Subject: [issue #QSU-61718-589]: Validation errors that don't make
> > sense to me
> >
> > Hi Benson,
> > Thanks for sending the WSDL.
> >
> > Issue #1: When you're on the overview page, you'll see just one
error
> > line with XSD Schema Validation highlighted. Click on that line, or
> > click the red "5 failures" link on the top right and you'll get
> > results filtered for just the 5 failures. If the top error is
> > expanded, you might need to scroll down to see all five.
> > I see five on both SOAPscope 5.3 and SOAPscope Workstation 6.0.
> >
> > Issue #2: I showed this to one of our developers. When your WSDL
> > includes multiple schema blocks, you need "include" statements for
> > each schema. You don't need to provide locations because the schemas
> > are already in the WSDL. This error message points out a basic
> > ambiguity between WSDL and Schema, and potential interop problems
> > depending on how your SOAP toolkit is implemented. According to XSD
> > Schema, you must import a schema in order to use it. This is
entirely
> > independent from the WSDL spec.
> >
> > I hope this helps.
> >
> > Carol Tyler, Mindreef Support
> >
> > On Tue, 09 Oct 2007 09:29:32 -0400, bim2007@basistech.com wrote:
> > > Issue #1:
> > >
> > > Top-level result from analysis with Mindreef Basic Diagnosis
Results
> > > says '5 failures'.
> > >
> > > Only one failure is reported.
> > >
> > > Issue #2: the failure makes no sense to me. I don't know what all
> > > this 'fragment' business is about, but I see no reason why the
> > > namespace in question is 'not referencable' from the place it is
> > > referenced from.
> >
> > All
> >
> > > the schemas are included in-line.
> > >
> > >
> > > Schema validation error on node xsd:element
> > > Error resolving component 'ns1:Name'. It was detected that
> > > 'ns1:Name'
> >
> > is
> >
> > > in namespace 'http://rnm.basistech.com', but components from this
> > > namespace are not referenceable from schema document
> >
> >
'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082
> >'.
> >
> > > If this is the incorrect namespace, perhaps the prefix of
'ns1:Name'
> > > needs to be changed. If this is the correct namespace, then an
> > > appropriate 'import' tag should be added to
> >
> >
'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082
> >'.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
Re: True or false: embedded schemata need to be imported?
Posted by Daniel Kulp <dk...@apache.org>.
If an embedded schema with one targetNamespace references types/elements
in an embedded schema in another targetNamespace, then yes, the other
schema needs to be imported.
Dan
On Tuesday 09 October 2007, Benson Margulies wrote:
> -----Original Message-----
> From: Mindreef Support [mailto:support@mindreef.com]
> Sent: Tuesday, October 09, 2007 5:01 PM
> To: Benson Margulies
> Subject: [issue #QSU-61718-589]: Validation errors that don't make
> sense to me
>
> Hi Benson,
> Thanks for sending the WSDL.
>
> Issue #1: When you're on the overview page, you'll see just one error
> line with XSD Schema Validation highlighted. Click on that line, or
> click the red "5 failures" link on the top right and you'll get
> results filtered for just the 5 failures. If the top error is
> expanded, you might need to scroll down to see all five.
> I see five on both SOAPscope 5.3 and SOAPscope Workstation 6.0.
>
> Issue #2: I showed this to one of our developers. When your WSDL
> includes multiple schema blocks, you need "include" statements for
> each schema. You don't need to provide locations because the schemas
> are already in the WSDL. This error message points out a basic
> ambiguity between WSDL and Schema, and potential interop problems
> depending on how your SOAP toolkit is implemented. According to XSD
> Schema, you must import a schema in order to use it. This is entirely
> independent from the WSDL spec.
>
> I hope this helps.
>
> Carol Tyler, Mindreef Support
>
> On Tue, 09 Oct 2007 09:29:32 -0400, bim2007@basistech.com wrote:
> > Issue #1:
> >
> > Top-level result from analysis with Mindreef Basic Diagnosis Results
> > says '5 failures'.
> >
> > Only one failure is reported.
> >
> > Issue #2: the failure makes no sense to me. I don't know what all
> > this 'fragment' business is about, but I see no reason why the
> > namespace in question is 'not referencable' from the place it is
> > referenced from.
>
> All
>
> > the schemas are included in-line.
> >
> >
> > Schema validation error on node xsd:element
> > Error resolving component 'ns1:Name'. It was detected that
> > 'ns1:Name'
>
> is
>
> > in namespace 'http://rnm.basistech.com', but components from this
> > namespace are not referenceable from schema document
>
> 'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082
>'.
>
> > If this is the incorrect namespace, perhaps the prefix of 'ns1:Name'
> > needs to be changed. If this is the correct namespace, then an
> > appropriate 'import' tag should be added to
>
> 'http://localhost:8080/rlpws/NameIndex?wsdl&mindreefFragmentId=6062082
>'.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog