You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by Gordon Sim <gs...@redhat.com> on 2007/05/15 09:54:08 UTC

[java]: STRICT_AMQP and message properties

The java client (on M2) throws an exception when trying to set any 
property other than string if the STRICT_AMQP flag is on. Is it not only 
some of the extended types that are not strict AMQP? i.e. could this be 
relaxed for int typed properties as well?

Re: [java]: STRICT_AMQP and message properties

Posted by Martin Ritchie <ri...@apache.org>.

On 15/05/07, Gordon Sim <gs...@redhat.com> wrote:
> The java client (on M2) throws an exception when trying to set any
> property other than string if the STRICT_AMQP flag is on. Is it not only
> some of the extended types that are not strict AMQP? i.e. could this be
> relaxed for int typed properties as well?

You are right. I was over eager in throwing the Unsupported Exceptions.

Looking at the code it is clear to see it is wrong. The
AbstractJMSMessage setInt calls super.setInt just as setString does sp
it should either allow it or not use the super method.

However that is the only one as the acceptable types are:
Integer, String, Decimal and Date-timestamp (long value)

I shall remove the restriction on the int in AbstractJMSMessage
-- 
Martin Ritchie