Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4443F1D7.80800@thoughtcraft.com>
Date: Mon, 17 Apr 2006 15:51:51 -0400
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Proposal: Extending the handler invocation pattern
References: <1145040785.7710.3.camel@scylla.watson.ibm.com>	
	<19e0530f0604141213o314b42aq1810546fce3a519b@mail.gmail.com>	
	<1145059635.7710.18.camel@scylla.watson.ibm.com>	
	<1145121846.30233.24.camel@localhost.localdomain>	
	<1145240379.19954.32.camel@scylla.watson.ibm.com>
	<1145302524.29655.45.camel@localhost.localdomain>
In-Reply-To: <1145302524.29655.45.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From: Glen Daniels <glen@thoughtcraft.com>

> We'd need to create a new interface (or I guess it could be a Handler
> but I think that'll be confusing) and a syntax for registering them in a
> module.xml probably. Then the engine would notify all such parties once
> the MEP has been completed. We may need an additional bit on the
> MessageReceiver interface to ask whether the MEP has been completed.

I'm not sure we'd even need to go as far as a module.xml syntax.  What 
about simply...

class OperationContext {
   ...
   public void addCompletionObserver(CompletionObserver obs) {
     ...
   }
}

interface CompletionObserver {
   void operationComplete(OperationContext op);
   // This could even be operationSucceeded() and operationFailed()
}

This seems like it could be very handy, really easy to add, and it would 
let Handlers programatically do what Bill's looking for (I think?). 
We've already got OperationContext.setComplete() as the hook for this. 
Is there a major reason not to put this in now?  Seems a very small 
change which would provide clear value.

--Glen