Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44E69BEF.9050106@opensource.lk>
Date: Sat, 19 Aug 2006 10:34:47 +0530
From: Eran Chinthaka <chinthaka@opensource.lk>
Reply-To: chinthaka@opensource.lk
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Identifying REST vs SOAP messages
References: <44E5EB22.5090309@opensource.lk>
 <44E66F1B.4080102@thoughtcraft.com>
In-Reply-To: <44E66F1B.4080102@thoughtcraft.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig988722A192BEE2A8A9B22FB5"

--------------enig988722A192BEE2A8A9B22FB5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Glen,

Glen Daniels wrote:

> I think the algorithm is as follows:
>=20
> 1) check media-type.  If it's either of the well-defined ones for SOAP
> 1.2 (application/soap+xml, application/xop+xml), it's SOAP 1.2.

This is the problem. As I mentioned in my earlier mail also, content
type for SOAP 1.2 is optional. One can send a SOAP 1.2 message without
putting the content type as application/soap+xml. What can we do about th=
at?

We can make it a must for users to send the content type, even if it is
SOAP 1.2.

- Chinthaka


--------------enig988722A192BEE2A8A9B22FB5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFE5pvxjON2uBzUhh8RApjxAJ0XU+cNcwnXHPY5/ampQQMLxmJmKwCePbJV
DuZVF+hQatc0oq59779+4h0=
=VZ1T
-----END PGP SIGNATURE-----

--------------enig988722A192BEE2A8A9B22FB5--