axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacek Kopecky <>
Subject Re: [Vote] 1 Msg or 2
Date Fri, 02 Feb 2001 14:16:49 GMT
 As indicated in my pictures, the intermediaries are like targetted
services, wrapping the next SOAP application, so there's no need for
this copying request to response here.

 Can you come up with some other use case for being able to do this

                            Jacek Kopecky

On Thu, 1 Feb 2001, Kevin Mitchell wrote:

 > +1 for two messages presented thru the MessageContext. One message will 
 > likely lead to undo complication in the public API to manage the original 
 > state vs the current state.  
 > However, I think it should be possible to modify the original message and 
 > send it as the response, without instantiating two distinct message 
 > objects. I imagine this will be especially efficient for intermediaries 
 > that peform specific processing as directed by header entries, remove 
 > those header entries, and pass the message on or fault.  In this case a 
 > good portion of the original message may be retained verbatim. Examples 
 > are authentication or routing intermediaries.
 > >>>>>>>>>>>>>>>>>> Original Message
 > On 2/1/01, 9:37:55 AM, Doug Davis <> wrote regarding [Vote] 1 
 > Msg or 2:
 > > To help move things along, I'd like to propose that
 > > we VOTE on one of the smaller open issues - one message
 > > or two in the MessageContext.
 > > I propose that we have two messages, an incoming and
 > > an outgoing (or an request and a response - we can
 > > work on the words after the vote).  From the e-mails
 > > I think that's where most (not all) people are but
 > > I'd like to have a formal vote to try to bring this to
 > > a close.  Committers, if you vote -1 please give a
 > > details list of reasons why one message would be better
 > > in an effort to sway us to your side.  Likewise, if you
 > > vote +1 and can think of reasons why one message just
 > > won't cut it please let us know of those too.
 > > -Dug

View raw message