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 "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/11/30 17:40:21 UTC

[jira] Created: (SANDESHA2-56) Better error msg for failure to send a CreateSequenceResponse

Better error msg for failure to send a CreateSequenceResponse
-------------------------------------------------------------

                 Key: SANDESHA2-56
                 URL: http://issues.apache.org/jira/browse/SANDESHA2-56
             Project: Apache Sandesha2
          Issue Type: Improvement
            Reporter: Thomas McKiernan
            Priority: Minor
         Attachments: createSeqResponseErrorMsg.patch

Currently, if a client throws an error when processing the createSequenceResponse (e.g. HTTP 500 error), an error might be thrown by the sending server's axisEngine.send method call indicating this.
The current createSequence processor will throw this error back up until it is eventually thrown back to the client as a fault.
This is slightly confusing and we should add a slightly more descriptive text msg when sending this fault back to the client.

I will attach a patch

-- 
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-56) Better error msg for failure to send a CreateSequenceResponse

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

David Illsley resolved SANDESHA2-56.
------------------------------------

    Resolution: Fixed
      Assignee: Andrew Gatford

Fixed in r481033

> Better error msg for failure to send a CreateSequenceResponse
> -------------------------------------------------------------
>
>                 Key: SANDESHA2-56
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-56
>             Project: Sandesha2
>          Issue Type: Improvement
>            Reporter: Thomas McKiernan
>            Assignee: Andrew Gatford
>            Priority: Minor
>         Attachments: createSeqResponseErrorMsg.patch
>
>
> Currently, if a client throws an error when processing the createSequenceResponse (e.g. HTTP 500 error), an error might be thrown by the sending server's axisEngine.send method call indicating this.
> The current createSequence processor will throw this error back up until it is eventually thrown back to the client as a fault.
> This is slightly confusing and we should add a slightly more descriptive text msg when sending this fault back to the client.
> I will attach a patch

-- 
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-56) Better error msg for failure to send a CreateSequenceResponse

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

Thomas McKiernan updated SANDESHA2-56:
--------------------------------------

    Attachment: createSeqResponseErrorMsg.patch

> Better error msg for failure to send a CreateSequenceResponse
> -------------------------------------------------------------
>
>                 Key: SANDESHA2-56
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-56
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Thomas McKiernan
>            Priority: Minor
>         Attachments: createSeqResponseErrorMsg.patch
>
>
> Currently, if a client throws an error when processing the createSequenceResponse (e.g. HTTP 500 error), an error might be thrown by the sending server's axisEngine.send method call indicating this.
> The current createSequence processor will throw this error back up until it is eventually thrown back to the client as a fault.
> This is slightly confusing and we should add a slightly more descriptive text msg when sending this fault back to the client.
> I will attach a patch

-- 
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-56) Better error msg for failure to send a CreateSequenceResponse

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

Thomas McKiernan updated SANDESHA2-56:
--------------------------------------

    Attachment: createSeqResponseErrorMsg.patch

> Better error msg for failure to send a CreateSequenceResponse
> -------------------------------------------------------------
>
>                 Key: SANDESHA2-56
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-56
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Thomas McKiernan
>            Priority: Minor
>         Attachments: createSeqResponseErrorMsg.patch
>
>
> Currently, if a client throws an error when processing the createSequenceResponse (e.g. HTTP 500 error), an error might be thrown by the sending server's axisEngine.send method call indicating this.
> The current createSequence processor will throw this error back up until it is eventually thrown back to the client as a fault.
> This is slightly confusing and we should add a slightly more descriptive text msg when sending this fault back to the client.
> I will attach a patch

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