You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org> on 2007/02/20 19:22:05 UTC

[jira] Created: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Update AMQConstant.cs to match response codes in AMQP 0.9
---------------------------------------------------------

                 Key: QPID-384
                 URL: https://issues.apache.org/jira/browse/QPID-384
             Project: Qpid
          Issue Type: Bug
          Components: Dot Net Client
         Environment: .NET
            Reporter: Tomas Restrepo


The set of known response codes in AMQConstant.cs is out of date for the .NET client and is causing compatibility issues with the java broker trunk. Need to synchronize to the spec again.

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


[jira] Commented: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476620 ] 

Rupert Smith commented on QPID-384:
-----------------------------------

Patch applied. Tests succesfully run.

> Update AMQConstant.cs to match response codes in AMQP 0.9
> ---------------------------------------------------------
>
>                 Key: QPID-384
>                 URL: https://issues.apache.org/jira/browse/QPID-384
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>         Environment: .NET
>            Reporter: Tomas Restrepo
>         Attachments: ssl_really.patch
>
>
> The set of known response codes in AMQConstant.cs is out of date for the .NET client and is causing compatibility issues with the java broker trunk. Need to synchronize to the spec again.

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


RE: [jira] Updated: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Posted by Tomas Restrepo <to...@devdeo.com>.
Hi kevin,

> Not sure this is correct. The but is for .NET but the patch is my Java SSL
> patch
>   (already submitted under QPID-383).

This is for the .NET client and doesn't affect the SSL patches you've been working on at all (particularly since I haven't provided the patch to enable SSL support on the .NET client to JIRA yet!).

It was just something I ran into while testing your patch :)

Tomas Restrepo
tomas.restrepo@devdeo.com
http://www.winterdom.com/weblog/





Re: [jira] Updated: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Posted by Kevin Smith <ks...@redhat.com>.
Tomas Restrepo (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/QPID-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Tomas Restrepo updated QPID-384:
> --------------------------------
> 
>     Attachment: ssl_really.patch
> 
> Patch to synchronize the response code values
> 
>> Update AMQConstant.cs to match response codes in AMQP 0.9
>> ---------------------------------------------------------
>>
>>                 Key: QPID-384
>>                 URL: https://issues.apache.org/jira/browse/QPID-384
>>             Project: Qpid
>>          Issue Type: Bug
>>          Components: Dot Net Client
>>         Environment: .NET
>>            Reporter: Tomas Restrepo
>>         Attachments: ssl_really.patch
>>
>>
>> The set of known response codes in AMQConstant.cs is out of date for the .NET client and is causing compatibility issues with the java broker trunk. Need to synchronize to the spec again.
> 
Not sure this is correct. The but is for .NET but the patch is my Java SSL patch 
  (already submitted under QPID-383).

--Kevin

[jira] Updated: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Restrepo updated QPID-384:
--------------------------------

    Attachment: ssl_really.patch

Patch to synchronize the response code values

> Update AMQConstant.cs to match response codes in AMQP 0.9
> ---------------------------------------------------------
>
>                 Key: QPID-384
>                 URL: https://issues.apache.org/jira/browse/QPID-384
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>         Environment: .NET
>            Reporter: Tomas Restrepo
>         Attachments: ssl_really.patch
>
>
> The set of known response codes in AMQConstant.cs is out of date for the .NET client and is causing compatibility issues with the java broker trunk. Need to synchronize to the spec again.

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


[jira] Closed: (QPID-384) Update AMQConstant.cs to match response codes in AMQP 0.9

Posted by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Restrepo closed QPID-384.
-------------------------------

       Resolution: Fixed
    Fix Version/s: M2
         Assignee: Tomas Restrepo

> Update AMQConstant.cs to match response codes in AMQP 0.9
> ---------------------------------------------------------
>
>                 Key: QPID-384
>                 URL: https://issues.apache.org/jira/browse/QPID-384
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>         Environment: .NET
>            Reporter: Tomas Restrepo
>         Assigned To: Tomas Restrepo
>             Fix For: M2
>
>         Attachments: ssl_really.patch
>
>
> The set of known response codes in AMQConstant.cs is out of date for the .NET client and is causing compatibility issues with the java broker trunk. Need to synchronize to the spec again.

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