[rabbitmq-discuss] CommandAssembler

Ben Hood 0x6e6562 at gmail.com
Tue Nov 15 12:30:54 GMT 2011


Dear list,

I know that there is already a thread on the 2.6/2.7 client side API
changes, but I thought this one might fall into it's own thread.

I was wondering whether there was a conscious design choice to reduce
the visibility of the ported CommandAssembler to default package
scope?

We were using the old AMQCommand.Assembler which was public in the
com.rabbitmq.client.impl namespace.

Cheers,

Ben


More information about the rabbitmq-discuss mailing list