Re: Request for XML Filter (AXIS2-1085)

[Takahide Nogayama]

Sanjiva said:
>The second point is what's fundamentally inconsistent with Axis2's
>architecture. If you want to introduce a StAX filter that one's thing.
>But doing that and having access to the message context doesn't make
>sense: we create an OMElement for the envelope giving just the StAX
>stream and then create a message context using that envelope.

Sorry I am not sure that I understand your point, but in my understanding, Message context
is created at AxisServilet and many information are added by AxisServlet,
TransportUtils (envelope is created here), AxisEngine, Dispatcher, and Handler while the
message is propagated to message receiver. The information means AxisConfiguration,
URL, character encoding type, SOAPAction, WSA-Action, AxisOperation, and so on. They
will be used at Handler layer to provide QOS.

Sanjiva said:
>If you want a StAX filter then it must be a StAX filter: StAX in, StAX
>out. I don't agree with the proposed change because its inconsistent
>with the design and appears to mix layers of processing.

Filter might not be clean design in terms of mixed layer processing. But handler with filter is
good for performance/memory perspective. Filter enables us to have an option of doing
some part of the job of the handler on StAX event layer or on handler layer.  It might not be
must-have but nice-to-have.
I think that mix layers of processing and performance improvement are trade-off problem.

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