[rabbitmq-discuss] CommandAssembler

[Ben Hood]

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