Daniels [mailto:[EMAIL PROTECTED] ]
Sent: Friday, December 28, 2007 1:49 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Soap Encoding support with ADB
Hey Amila:
won't need them. But for SOAP 1.1, the situation is
different.
The
encoding spec says
On Jan 3, 2008 10:52 PM, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Anne, all:
Anne Thomas Manes wrote:
SOAP encoding is much more likely to be used in a code-first scenario,
but you must make sure that it also works in a WSDL-first scenario.
+1
Regarding one of your questions, you
On Jan 4, 2008 2:48 AM, R J Scheuerle Jr [EMAIL PROTECTED] wrote:
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)
Glen Daniels [EMAIL PROTECTED] wrote on 12/28/2007 12:49:21 AM:
Hey Amila:
won't need them. But for SOAP 1.1, the
: Re: [Axis2] Soap Encoding support with ADB
Hey Amila:
won't need them. But for SOAP 1.1, the situation is
different.
The
encoding spec says you MUST encode all complex object types
as
top-level
members of the serialization. Therefore ALL
Here is the summary of this discussion.
ADB soap encoding support is to provide support for wsdls having soap
encoding schema types.
ADB supports only Single reference serialization and hence graphs with loops
can not be supported. But
multireference parsing is supported.
For a general schema
.
--
Tom Jordahl
Axis 1.x guy
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED] ]
Sent: Friday, December 28, 2007 1:49 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Soap Encoding support with ADB
Hey Amila
Hi Anne, all:
Anne Thomas Manes wrote:
SOAP encoding is much more likely to be used in a code-first scenario,
but you must make sure that it also works in a WSDL-first scenario.
+1
Regarding one of your questions, you would never see an element
defined as follows:
s:element
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)
Glen Daniels [EMAIL PROTECTED] wrote on 12/28/2007 12:49:21 AM:
Hey Amila:
won't need them. But for SOAP 1.1, the situation is different.
The
encoding spec says you MUST encode all
1:49 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Soap Encoding support with ADB
Hey Amila:
won't need them. But for SOAP 1.1, the situation is different.
The
encoding spec says you MUST encode all complex object types as
top-level
members of the serialization. Therefore ALL
using
already existing ADB logic
won't give any serializing de serializing issues.
Thanks,
Amila.
--
Tom Jordahl
Axis 1.x guy
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]
Sent: Friday, December 28, 2007 1:49 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Soap
serializing issues.
Thanks,
Amila.
--
Tom Jordahl
Axis 1.x guy
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED] ]
Sent: Friday, December 28, 2007 1:49 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Soap Encoding support with ADB
Hey Amila
I went through the soap 1.1 spec and found this as the first serialization
rule.
All values are represented as element content. A multi-reference value MUST
be represented as the content of an independent element. A single-reference
value SHOULD not be (but MAY be)
It only says if we use
On Dec 26, 2007 7:37 PM, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Amila:
Amila Suriarachchi wrote:
To support the soap encoding, there are a set of special classes in the
org.apache.axis2.databinding.types.soapencoding pacakge.
Er... sorry, but -1 on this approach. :(
The point of SOAP
On Dec 26, 2007 7:37 PM, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Amila:
Amila Suriarachchi wrote:
To support the soap encoding, there are a set of special classes in the
org.apache.axis2.databinding.types.soapencoding pacakge.
Er... sorry, but -1 on this approach. :(
The point of SOAP
Hey Amila:
won't need them. But for SOAP 1.1, the situation is different. The
encoding spec says you MUST encode all complex object types as top-level
members of the serialization. Therefore ALL conforming SOAP 1.1
encoding implementations will be putting out stuff that looks
Hi Amila:
Amila Suriarachchi wrote:
To support the soap encoding, there are a set of special classes in the
org.apache.axis2.databinding.types.soapencoding pacakge.
Er... sorry, but -1 on this approach. :(
The point of SOAP encoding is to be able to encode *standard language
types*. If you
16 matches
Mail list logo
