Mailing-List: contact sandesha-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <26703072.1194603591178.JavaMail.jira@brutus>
Date: Fri, 9 Nov 2007 02:19:51 -0800 (PST)
From: "Thomas McKiernan (JIRA)" <jira@apache.org>
To: sandesha-dev@ws.apache.org
Subject: [jira] Updated: (SANDESHA2-127) RSP: beans should use real
 endpointreferences
In-Reply-To: <17092445.1194516410587.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SANDESHA2-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas McKiernan updated SANDESHA2-127:
---------------------------------------

    Attachment: storeEPRs2.patch

This should fix the issues

> RSP: beans should use real endpointreferences
> ---------------------------------------------
>
>                 Key: SANDESHA2-127
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-127
>             Project: Sandesha2
>          Issue Type: Bug
>            Reporter: Thomas McKiernan
>            Priority: Minor
>         Attachments: storeEPRs2.patch
>
>
> Some requirements in the Reliable Secure Profile state that some RM protocol faults should go to the sequence acksTo EPR.
> This does not currently happen, and so sandesha effectively assumes the replyTo and acksTo will always be the same, which is not always necessarily the case.
> This also brings up the bigger issue that EPRs are stored in the RMSequenceBean as Strings, and so various ref parameters are effectively lost.
> Since EPRs are serializable, this should be corrected, but in such a way that it does not break the schemas of previous versions.

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