At 11:35 AM 5/25/2006 +0000, frofis wrote:
> No, only the top-level namespaces (usually a
> complex schema has a top-level schema and several
> other defining internal types)

How to define that it top-level namespaces

If you cannot detect what is the schema that includes all the others, list them all.


> What do you mean by "main things"

my "main things" = our "top-level namespaces"

>and "allocate targetNamespace"?

in

> > parser->setExternalSchemaLocation("http://www.w3.org/2003/05/soap-envelope
> > file:///C:/CBuilder/Xml_Pr/soap-envelope.xsd
> > urn:cbr-ru:msg:props:v1.1
> > file:///C:/CBuilder/Xml_Pr/cbr_msg_props_v1.1.0.xsd
> > urn:cbr-ru:ed:v1.1 file:///C:/CBuilder/Xml_Pr/cbr_ed_v1.1.2.xsd");

http://www.w3.org/2003/05/soap-envelope - targetNamespace in soap-envelope.xsd
urn:cbr-ru:msg:props:v1.1 - targetNamespace in cbr_msg_props_v1.1.0.xsd
urn:cbr-ru:ed:v1.1 - targetNamespace in cbr_ed_v1.1.2.xsd

Thus

str = targetNamespace in soap-envelope.xsd + soap-envelope.xsd e.t.c

Yes; the format is "URI schema URI schema URI schema..."


> You have three choices:

find WideString

> The infrastructure is in place for
> locale-specific error messages, but I have never
> tried it;

I shall try

Enjoy!

Alberto


Thanks

Reply via email to