(oops! accidentally hit 'send' before I was anywhere near ready!)
There are two types of headers in WSDL:
- explicit - the soap:header message in a binding operation also appears in
the corresponding portType's operation. In other words, a parameter in a
method is sent in the soap message's
Wow. Lots of questions.
Let me make some comments, then I'll
Russell Butek
[EMAIL PROTECTED]
"St-Germain, Sylvain" <[EMAIL PROTECTED]> on 10/03/2002 11:20:54
AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: soap:header support
ch traffic about explicit headers. Anyone has?
--
Sylvain St-Germain
Macadamian Technologies
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 4:23 PM
To: [EMAIL PROTECTED]
Subject: soap:header support
There are a lot of nuances to supp
There are a lot of nuances to supporting soap:header in AXIS. Some of the
quirks that concern me are:
- explicit headers are SEI parameters that are sent as headers, implicit
headers are messages that aren't used by the portType. How are implicit
headers implemented? Via handlers, presumabl
ning...
Sylvain.
-Original Message-
From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 25, 2002 5:28 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Client side soap:header support.
I have been talking with Glen and giving this a bit of thought. It believe
that we do NO
EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 8:40 AM
To: [EMAIL PROTECTED]
Subject: RE: Client side soap:header support.
Sylvain - let me see if I can convey a compelling position for the dual
stack implementation.
Think of the ability to define a request header of tag name
TransactionID
ke of convenience. However, the abstraction
is a red herring if the and definitions differ.
/Chris
-Original Message-
From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 25, 2002 5:59 PM
To: [EMAIL PROTECTED]
Subject: RE: Client side soap:header support.
Glen
ilto:[EMAIL PROTECTED]]
Sent: Thursday, April 25, 2002 5:28 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Client side soap:header support.
I have been talking with Glen and giving this a bit of thought. It believe
that we do NOT want the headers on the Service, but they need to be
associated with
changes to your implementation without too much pain.
--
Tom Jordahl
Macromedia
-Original Message-
From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 2:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Client side soap:header support.
Tom,
As you noticed I did not
soap:header entry in the operation
binding.
You will need to apply the patch I have provided manually though...
Sylvain.
-Original Message-
From: Chris Haddad [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 2:50 PM
To: [EMAIL PROTECTED]
Subject: RE: Client side soap:header
Sylvain -
Do you have any thoughts on how we could easily extend the code to
support a hierarchical namespace?
I'd like to be able to add the following as soap headers:
some value
/Chris
some "ownership" information in there! as well as
cleaning up the System.out and the tabs.
Thanks Tom for your warm welcome!
Looking forward to see soap:header support in early B2 versions!
Sylvain.
-Original Message-
From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, A
3:51 PM
To: Axis Dev (E-mail)
Subject: Client side soap:header support.
Hi all,
Here is some code that provide client side support for soap:header entry in
the WSDL operation binding.
Modified files:
xml-axis/java/src/org/apache/axis/client/Service.java
xml-axis/java/src/org/apache/axis/w
Hi all,
Here is some code that provide client side support for soap:header entry in
the WSDL operation binding.
Modified files:
xml-axis/java/src/org/apache/axis/client/Service.java
xml-axis/java/src/org/apache/axis/wsdl/toJava/JavaStubWriter.java
Added files:
xml-axis/java/src/org/apac
14 matches
Mail list logo
