Re: Request for XML Filter (AXIS2-1085)

[R J Scheuerle Jr]

>> OK then write a handler that turns off caching (so you get the pull
>> stream raw), eats whatever it wants and builds a new envelope and sticks
>> it onto the MC as the envelope.
>>
>> No expanding the tree, no architectural inconsistency and you get StAX
>> to play with. Problem solved?
>>
>> Sanjiva.
>>

>Yes, That is right. If we wrote handler which get parser and insert filter, 
>at the top of handler chain, then we could avoid to change transport layer to
>insert filter. 

>But we can not filter SOAP header part by the handler solution, because 
>SOAP header part is already build in transport layer before handler layer 
>by invoking envelope.getBody(). For example, envelope.getBody() is called
>on the bottom of HTTPTransportUtils.processHTTPPostRequest(), then the envelope 
>is passed to AxisEngine. All StAXEvents of the SOAP header are already consumed
>by the handler gets envelope. 

>Regards,
>---------------------------
>Takahide Nogayama

Sanjeeva,

Is is reasonable to introduce a handler phase that occurs just after the SOAPEnvelope is created but before it is queried ?


Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115  (IBM TL 678-5115)