From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | mlw <pgsql(at)mohawksoft(dot)com> |
Cc: | swampler(at)noao(dot)edu, jfelice(at)cronosys(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PostgreSQL and SOAP, suggestions? |
Date: | 2003-04-02 10:29:09 |
Message-ID: | 1049279349.1767.101.camel@fuji.krosing.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
mlw kirjutas T, 01.04.2003 kell 15:29:
> Hannu Krosing wrote:
>
> >pgsql(at)mohawksoft(dot)com kirjutas E, 31.03.2003 kell 19:52:
> >
> >
> >>Actually, as far as I am aware, the header is for metadata, i.e. it is the
> >>place to describe the data being returned.
> >>
> >>
> >
> >Did you read the SOAP spec ?
> >
> yes
???
What you have come up with _is_not_ a SOAP v1.1 message at all. It does
use some elements with similar names but from different namespace.
the SOAP Envelope, Header and Body elemants must be from namespace
http://schemas.xmlsoap.org/soap/envelope/
Per section 3 paragraph 2 of SOAP spec a conforming SOAP processor MUST
discard a message that has incorrect namespace.
> <?xml version = "1.0"?>
> <mwssql:Envelope xmlns:mwssql="http://www.mohawksoft.com/mwssql/envelope">
> <mwssql:Header>
The <SOAP-ENV:Header> "is a generic mechanism for adding features to a
SOAP message in a decentralized manner without prior agreement between
the communicating parties. SOAP defines a few attributes that can be
used to indicate who should deal with a feature and whether it is
optional or mandatory (see section 4.2)".
The <SOAP-ENV:Body> "is a container for mandatory information intended
for the ultimate recipient of the message (see section 4.3). SOAP
defines one element for the body, which is the Fault element used for
reporting errors."
The Header element is encoded as the first immediate child element of
the SOAP Envelope XML element. All immediate child elements of the
Header element are called header entries.
The encoding rules for header entries are as follows:
1. A header entry is identified by its fully qualified element
name, which consists of the namespace URI and the local name.
All immediate child elements of the SOAP Header element MUST be
namespace-qualified.
...
An example is a header with an element identifier of "Transaction", a
"mustUnderstand" value of "1", and a value of 5. This would be encoded
as follows:
<SOAP-ENV:Header>
<t:Transaction
xmlns:t="some-URI" SOAP-ENV:mustUnderstand="1">
5
</t:Transaction>
</SOAP-ENV:Header>
> <exec:sql>update cgrpairs set ratio=0 where srcitem=100098670</exec:sql>
> <exec:affected>2657</exec:affected>
> <qry:sql>select * from ztitles limit 2</qry:sql>
> <qry:ROWSET>
> <qry:ROW columns="28">
where are namespaces exec:, qry: abd t: defined ?
----------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2003-04-02 12:56:49 | Re: PostgreSQL and SOAP, suggestions? |
Previous Message | Dave Page | 2003-04-02 09:56:30 | Re: View definition formatting |