You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2006/11/27 09:58:21 UTC

[jira] Created: (SANDESHA2-51) Use addressing properties to close reply sequences

Use addressing properties to close reply sequences
--------------------------------------------------

                 Key: SANDESHA2-51
                 URL: http://issues.apache.org/jira/browse/SANDESHA2-51
             Project: Apache Sandesha2
          Issue Type: Improvement
            Reporter: Matt Lovett
         Assigned To: Matt Lovett


Currently server-side reply sequences are closed by storing the request message context, and using it to navigate to the operation context to check if the last inbound message has been replied to. There is a TODO in the code to do this in a more storage-friendly manner... and I agree that it is quite wasteful if we are not using an in-memory store. An alternative is to use the ws-a MessageId and RelatesTo fields to track the correct reply message.

I'll attach a patch to implement this.

-- 
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


[jira] Updated: (SANDESHA2-51) Use addressing properties to close reply sequences

Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-51?page=all ]

Matt Lovett updated SANDESHA2-51:
---------------------------------

    Attachment: terminate.patch

Patch as described above.

> Use addressing properties to close reply sequences
> --------------------------------------------------
>
>                 Key: SANDESHA2-51
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-51
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>         Assigned To: Matt Lovett
>         Attachments: terminate.patch
>
>
> Currently server-side reply sequences are closed by storing the request message context, and using it to navigate to the operation context to check if the last inbound message has been replied to. There is a TODO in the code to do this in a more storage-friendly manner... and I agree that it is quite wasteful if we are not using an in-memory store. An alternative is to use the ws-a MessageId and RelatesTo fields to track the correct reply message.
> I'll attach a patch to implement this.

-- 
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


[jira] Resolved: (SANDESHA2-51) Use addressing properties to close reply sequences

Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SANDESHA2-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Lovett resolved SANDESHA2-51.
----------------------------------

    Resolution: Fixed

> Use addressing properties to close reply sequences
> --------------------------------------------------
>
>                 Key: SANDESHA2-51
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-51
>             Project: Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>         Assigned To: Matt Lovett
>         Attachments: terminate.patch
>
>
> Currently server-side reply sequences are closed by storing the request message context, and using it to navigate to the operation context to check if the last inbound message has been replied to. There is a TODO in the code to do this in a more storage-friendly manner... and I agree that it is quite wasteful if we are not using an in-memory store. An alternative is to use the ws-a MessageId and RelatesTo fields to track the correct reply message.
> I'll attach a patch to implement this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (SANDESHA2-51) Use addressing properties to close reply sequences

Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-51?page=all ]

Matt Lovett updated SANDESHA2-51:
---------------------------------

    Attachment: terminate.patch

Patch as described above.

> Use addressing properties to close reply sequences
> --------------------------------------------------
>
>                 Key: SANDESHA2-51
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-51
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>         Assigned To: Matt Lovett
>         Attachments: terminate.patch
>
>
> Currently server-side reply sequences are closed by storing the request message context, and using it to navigate to the operation context to check if the last inbound message has been replied to. There is a TODO in the code to do this in a more storage-friendly manner... and I agree that it is quite wasteful if we are not using an in-memory store. An alternative is to use the ws-a MessageId and RelatesTo fields to track the correct reply message.
> I'll attach a patch to implement this.

-- 
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


[jira] Resolved: (SANDESHA2-51) Use addressing properties to close reply sequences

Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SANDESHA2-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Lovett resolved SANDESHA2-51.
----------------------------------

    Resolution: Fixed

> Use addressing properties to close reply sequences
> --------------------------------------------------
>
>                 Key: SANDESHA2-51
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-51
>             Project: Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>         Assigned To: Matt Lovett
>         Attachments: terminate.patch
>
>
> Currently server-side reply sequences are closed by storing the request message context, and using it to navigate to the operation context to check if the last inbound message has been replied to. There is a TODO in the code to do this in a more storage-friendly manner... and I agree that it is quite wasteful if we are not using an in-memory store. An alternative is to use the ws-a MessageId and RelatesTo fields to track the correct reply message.
> I'll attach a patch to implement this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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