activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes" <e.se...@gmail.com>
Subject Re: NMS 1.1 Breaking API Change
Date Thu, 28 May 2009 20:22:15 GMT
There are 2 outstanding bugs logged against the 1.1 version as of this morning. Once those
are resolved a release candidate will be cut.

- Jim

-----Original Message-----
From: Bruce Snyder <bruce.snyder@gmail.com>

Date: Thu, 28 May 2009 12:26:22 
To: <dev@activemq.apache.org>
Subject: Re: NMS 1.1 Breaking API Change


On Fri, May 22, 2009 at 4:58 PM, semog <e.semog@gmail.com> wrote:
>
> This is a heads-up message for users of the NMS 1.1 library.  Two fixes were
> made to the product that will break compilation of existing code.  When you
> update to the latest version, you will need to update references to a couple
> of fields and parameters.  On the positive side, these breaking changes are
> obvious and will generate compiler errors.  They are not subtle changes that
> are hard to find in your code.
>
> Please see the following JIRA issues for more information:
>
> See https://issues.apache.org/activemq/browse/AMQNET-105
> See https://issues.apache.org/activemq/browse/AMQNET-101
>
> The basic change is that the NMSPersistent field is no longer a boolean
> value.  It has been renamed to NMSDeliveryMode and the type is the new
> MsgDeliveryMode enumeration.  The NMSPriority field has been changed from a
> simple byte type to the MsgPriority enumeration.  The Send() function
> parameters now use these new enumeration types.

Jim, any idea when the next release of NMS will take place?

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Mime
View raw message