osdir.com
mailing list archive

Subject: Kai-Oliver Marohn/GFIDOR/IHK ist außer Haus. - msg#00023

List: windows.devel.soap.general

Date: Prev Next Index Thread: Prev Next Index
Ich werde ab 23.02.2003 nicht im Büro sein. Ich kehre zurück am
03.03.2003.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other
DevelopMentor lists at http://discuss.develop.com.



Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Namespace for the 'detail' element

The following SOAP document fails schema validation against the SOAP xsd (http://schemas.xmlsoap.org/soap/envelope) ---------------------- <?xml version="1.0" encoding="utf-8"?> <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <Body> <Fault> <faultcode>Client</faultcode> <faultstring>Invalid attempt to ....</faultstring> <detail> <dispositionReport xmlns="http://myuri.org/v1.1"> <result>Invalid userid or password</result> </dispositionReport> </detail> </Fault> </Body> </Envelope> ---------------------- Adding a null namespace declaration to each of the elements 'faultcode', 'faultstring' and 'detail' causes the above document to pass schema validation. ---------------------- <?xml version="1.0" encoding="utf-8"?> <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <Body> <Fault> <faultcode xmlns=''>Client</faultcode> <faultstring xmlns=''>Invalid attempt to ....</faultstring> <detail xmlns=''> <dispositionReport xmlns="http://myuri.org/v1.1"> <result>Invalid userid or password</result> </dispositionReport> </detail> </Fault> </Body> </Envelope> ---------------------- Does that mean that these elements (in particular 'detail') should not be declared with the SOAP namespace, and MUST occur within the null namespace? thanks, -mb You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Next Message by Date: click to view message preview

Re: Namespace for the 'detail' element

Nope. It means that your parser doesn't handle default namesapces very well. If you give the soap namespace a prefix and prepend your elements correctly does your document pass validation? <?xml version="1.0" encoding="utf-8"?> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <s:Fault> <s:faultcode>Client</s:faultcode> <s:faultstring>Invalid attempt to ....</s:faultstring> <s:detail> <dispositionReport xmlns="http://myuri.org/v1.1"> <result>Invalid userid or password</result> </dispositionReport> </s:detail> </s:Fault> </s:Body> </s:Envelope> Dan ----- Original Message ----- From: "Mark B" <mark_bradshaw_92516@xxxxxxxxx> To: <SOAP@xxxxxxxxxxxxxxxxxxx> Sent: Sunday, February 23, 2003 7:45 PM Subject: [SOAP] Namespace for the 'detail' element > The following SOAP document fails schema validation against the SOAP xsd > (http://schemas.xmlsoap.org/soap/envelope) > ---------------------- > <?xml version="1.0" encoding="utf-8"?> > <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> > <Body> > <Fault> > <faultcode>Client</faultcode> > <faultstring>Invalid attempt to ....</faultstring> > <detail> > <dispositionReport xmlns="http://myuri.org/v1.1"> > <result>Invalid userid or password</result> > </dispositionReport> > </detail> > </Fault> > </Body> > </Envelope> > ---------------------- > > Adding a null namespace declaration to each of the > elements 'faultcode', 'faultstring' and 'detail' causes the above document > to pass schema validation. > > ---------------------- > <?xml version="1.0" encoding="utf-8"?> > <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> > <Body> > <Fault> > <faultcode xmlns=''>Client</faultcode> > <faultstring xmlns=''>Invalid attempt to ....</faultstring> > <detail xmlns=''> > <dispositionReport xmlns="http://myuri.org/v1.1"> > <result>Invalid userid or password</result> > </dispositionReport> > </detail> > </Fault> > </Body> > </Envelope> > ---------------------- > > Does that mean that these elements (in particular 'detail') should not be > declared with the SOAP namespace, and MUST occur within the null namespace? > > thanks, > > -mb > > You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other > DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Previous Message by Thread: click to view message preview

Namespace for the 'detail' element

The following SOAP document fails schema validation against the SOAP xsd (http://schemas.xmlsoap.org/soap/envelope) ---------------------- <?xml version="1.0" encoding="utf-8"?> <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <Body> <Fault> <faultcode>Client</faultcode> <faultstring>Invalid attempt to ....</faultstring> <detail> <dispositionReport xmlns="http://myuri.org/v1.1"> <result>Invalid userid or password</result> </dispositionReport> </detail> </Fault> </Body> </Envelope> ---------------------- Adding a null namespace declaration to each of the elements 'faultcode', 'faultstring' and 'detail' causes the above document to pass schema validation. ---------------------- <?xml version="1.0" encoding="utf-8"?> <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <Body> <Fault> <faultcode xmlns=''>Client</faultcode> <faultstring xmlns=''>Invalid attempt to ....</faultstring> <detail xmlns=''> <dispositionReport xmlns="http://myuri.org/v1.1"> <result>Invalid userid or password</result> </dispositionReport> </detail> </Fault> </Body> </Envelope> ---------------------- Does that mean that these elements (in particular 'detail') should not be declared with the SOAP namespace, and MUST occur within the null namespace? thanks, -mb You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.

Next Message by Thread: click to view message preview

new to SOAP, no arrays??

Hi! I am new to SOAP but am accomplished developer. I am preparing to use a new product that uses the SOAP/XML API and am trying to use the SOAP::Parser module but it will not accept the vendors input. I am seeking advice as to how to use/augment the module for my purposes. It appears I might have to write a handler for array type?? But the vendor's reference is a little obscure. ANy help/advice would be greatly appreciated. thanks... ... > cat soapit.pl use SOAP::Parser; use Data::Dumper; my $parser = SOAP::Parser->new(); $parser->parsefile($ARGV[0]); my $headers = $parser->get_headers(); my $body = $parser->get_body(); $Data::Dumper::Purity = 1; $Data::Dumper::Indent = 1; $Data::Dumper::Terse = 1; print " HEADER ***\n"; print Dumper $headers; print " Body ***\n"; print Dumper $body > soapit.pl vrr.xml Duplicate accessor: item at /usr/local/lib/perl5/site_perl/5.6.1/SOAP/GenericInputStream.pm line 167. > cat vrr.xml <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://www.cisco.com/cim-cx/2.0" xmlns:ns1="urn:CIM"> <soapenv:Header> <ns0:message id="87855" sessiontoken="D3C4845765B5B28509096833F7251713" timestamp="2003-02-21T15:44:21.583Z" /> </soapenv:Header> <soapenv:Body> <ns1:enumerateInstancesResponse> <returns xsi:type="ns1:CIMReturnList" soapenc:arrayType="ns1:CIMReturn[]"> <record> <objectPath xsi:type="ns1:CIMObjectPath"> <className xsi:type="xsd:string">Region</className> <properties xsi:type="ns1:CIMPropertyList" soapenc:arrayType="ns1:CIMProperty[]"> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Name</name> <value xsi:type="xsd:string">NbiRegion</value> </item> <name xsi:type="xsd:string">Id</name> <value xsi:type="xsd:string">1</value> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">ContactInfo</name> <value xsi:type="xsd:string" /> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">AsNumber</name> <value xsi:type="xsd:string">100</value> </item> </properties> </objectPath> </record> </record> <record> <objectPath xsi:type="ns1:CIMObjectPath"> <className xsi:type="xsd:string">Region</className> <properties xsi:type="ns1:CIMPropertyList" soapenc:arrayType="ns1:CIMProperty[]"> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Name</name> <value xsi:type="xsd:string">Region1200</value> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Id</name> <value xsi:type="xsd:string">2</value> </item> </properties> </objectPath> <record> <objectPath xsi:type="ns1:CIMObjectPath"> <className xsi:type="xsd:string">Provider</className> <soapenv:Header> <ns0:message id="87855" sessiontoken="D3C4845765B5B28509096833F7251713" timestamp="2003-02-21T15:44:21.583Z" /> </soapenv:Header> <soapenv:Body> <ns1:enumerateInstancesResponse> <returns xsi:type="ns1:CIMReturnList" soapenc:arrayType="ns1:CIMReturn[]"> <record> <objectPath xsi:type="ns1:CIMObjectPath"> <className xsi:type="xsd:string">Region</className> <properties xsi:type="ns1:CIMPropertyList" soapenc:arrayType="ns1:CIMProperty[]"> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Name</name> <value xsi:type="xsd:string">NbiRegion</value> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Id</name> <value xsi:type="xsd:string">1</value> </item> </properties> </objectPath> <record> <objectPath xsi:type="ns1:CIMObjectPath"> <className xsi:type="xsd:string">Provider</className> <properties xsi:type="ns1:CIMPropertyList" soapenc:arrayType="ns1:CIMProperty[]"> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Name</name> <value xsi:type="xsd:string">NbiProvider</value> </item> <item xsi:type="ns1:CIMProperty"> <properties xsi:type="ns1:CIMPropertyList" soapenc:arrayType="ns1:CIMProperty[]"> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Name</name> <value xsi:type="xsd:string">NbiProvider</value> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">Id</name> <value xsi:type="xsd:string">1</value> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">ContactInfo</name> <value xsi:type="xsd:string" /> </item> <item xsi:type="ns1:CIMProperty"> <name xsi:type="xsd:string">AsNumber</name> <value xsi:type="xsd:string">100</value> </item> </properties> </objectPath> </record> </record> </returns> </ns1:enumerateInstancesResponse> </soapenv:Body> </soapenv:Envelope> -- Michael Matthews You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by