Hi Shawn;

I think the Q always boil down to the what Handlers to run or which
service. The MessgaeSender/MessageReciver expect a Registry, (called
AxisRegistry in my toy) which says which Hanlders to run for which
service!.

I see two ways to create this AxisRegistry
1) xml configuration file
2) Hard code a engine registry in the stub 

May be it is combinaion of the both. Initally the user have to
manually write #1 or #2. But ideally the WSDL code genration tool
should merge the server side and client side policy files and decide
on the policy and geneate the #1 or #2 based on the policy

Thanks
Srinath 


On Fri, 25 Mar 2005 00:52:51 +0000 GMT, Shawn Dahlen <[EMAIL PROTECTED]> wrote:
> Srinath,
> 
> Sorry I couldn't respond sooner.  I have some free time this weekend, so I 
> will check out what you have put together.
> 
> One issue that has been troubling me is how do we configure the handler chain 
> for a MessageProducer used by a client to send a message?  At the messaging 
> level, stubs are not generated, so the developer must configure manually.  
> Even at a service level, how / where does this info come from? How do we know 
> that a given endpoint requires security or reliability (or is the client 
> always the initiator for a reliable conversation)?  I guess this is where WS 
> Policy plays its part.
> 
> If you put together a solution already I apologize.  Would be interested in 
> hearing your thoughts though.
> 
> Shawn
> 
> -----Original Message-----
> From: Srinath Perera <[EMAIL PROTECTED]>
> Date: Wed, 23 Mar 2005 19:16:47
> To:"[email protected]" <[email protected]>
> Cc:Shawn Dahlen <[EMAIL PROTECTED]>
> Subject: [Axis2]Initial proposal for the messaged based Axis2 core
> 
> Hi All;
> 
> Based on the Shawn proposal I have checked in, a toy for the Axis2 core.
> 
> https://svn.apache.org/repos/asf/webservices/axis/trunk/archive/java/scratch/srinath_jaliya/
> more improvements coming soon
> 
> Thanks
> Srinath
>

Reply via email to