qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rupert Smith (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-250) .Net client does not use specs from the specs directory.
Date Mon, 08 Jan 2007 11:19:27 GMT

    [ https://issues.apache.org/jira/browse/QPID-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463007
] 

Rupert Smith commented on QPID-250:
-----------------------------------

The build scripts for the dotnet framing generation have been updated to point to the definitive
spec. An additional argument, containing an empty field table, has been added to the call
to BasicConsumeBody#CreateAMQFrame for an additional argument that was added to the 0.8 specs.
This fixes the build.

I've added a patch for these changes.

> .Net client does not use specs from the specs directory.
> --------------------------------------------------------
>
>                 Key: QPID-250
>                 URL: https://issues.apache.org/jira/browse/QPID-250
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>         Environment: .Net 1.1 and 2.0
>            Reporter: Rupert Smith
>         Attachments: Qpid-250.diff
>
>
> The .net client has its own private copy of the amqp 0.8 spec in dotnet/Qpid.Common/amqp.xml.
This differs slightly from the spec file in specs/amqp-0.8.xml. Having multiple copies of
the same spec that differ cannot be right. Also, chaning the .net build to point to the correct
spec breaks the build.
> Private copy of spec to be deleted. Build to be fixed to work with correct spec.

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

        

Mime
View raw message