You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2006/10/20 14:14:36 UTC

[jira] Updated: (SANDESHA2-20) Refactor ack header processing

     [ http://issues.apache.org/jira/browse/SANDESHA2-20?page=all ]

Matt Lovett updated SANDESHA2-20:
---------------------------------

    Attachment: rework.patch

Here's another patch, continuing the header processing theme. With this, inbound Sequence headers get processed in the InHandler (by the new SequenceProcessor class), but the message body is now handled by the message receiver (and application messages will run through to the app message receiver, not the sandesha one). That's goodness as it means we fit in with the axis architecture better, and could also cope with odd situations like a CreateSequence message that was sent reliably.

I also took the opportunity to change module.xml so that the inbound operations will be resolved correctly (by action), and outbound operations are now looked up instead of being created each time. I believe this will ensure that op.isClientSide() will now be telling the truth for all our flows.

This patch depends on the Axis2 jira at http://issues.apache.org/jira/browse/AXIS2-1457
and it won't work before that patch goes in

Thanks,

Matt

> Refactor ack header processing
> ------------------------------
>
>                 Key: SANDESHA2-20
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-20
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>            Priority: Minor
>         Attachments: ackPatch.txt, ackPatch.txt, ackRequested.patch, rework.patch
>
>
> As I have hinted a few times on list, I think that the message processing through the sandesha handlers could be refactored into header processing (within the handlers), and body processing (in a message receiver). This patch is the start of that work, refactoring the ack header processing.
> This patch also fixes a defect along the way, as there might be multiple ack headers on an inbound message.
> If this patch is accepted then I'll do the same for the ackRequest header, and then move on to the body processing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org