[rabbitmq-discuss] Breaking API changes in JAva API 2.7.0

[Cameron Davison]

Why isn't there a setAddresses on the connection factory? You seem to
be recommending everyone wrap the connection factory in another
factory that then gets passed into your object that will need to get
connections to rabbit. It would make a lot more sense to be able to
set all the available addresses on the ConnectionFactory and then be
able to pass that around to things that would need to create
connections.

-Cameron Davison

On Nov 11, 2011, at 7:19 AM, Steve Powell <steve at rabbitmq.com> wrote:

> Ah!
> Takes foot from mouth -- of course you need set*() calls, because we
> don't expose any address on the newConnection() calls now!  Oops.
>
> Apologies, I'll raise a bug to re-introduce the old API -- I guess it
> should teach me to be careful how we simplify. To encourage people
> to move away from the array interface, however, I think it may be
> deprecated and we will have:
>  newConnection(Address)
> or
>  newConnection(ExecutorService, Address)
>
> or similar.
>
> Thanks again.
> Steve Powell
> steve at rabbitmq.com
> [wrk: +44-2380-111-528] [mob: +44-7815-838-558]
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss