You not actually going to prohibit folks for using the old constructors are
I'd say adding factories is a good thing, and you should encourage folks to
use the factories instead of the constructors, but please don't stop folks
from using the constructors directly.

On Wed, Jan 23, 2013 at 11:36 AM, Phil Harvey <>wrote:

> As part of the Proton JNI work, I would like to remove all calls to
> proton-j implementation constructors from "client code".  I intend that
> factories will be used instead [1], thereby abstracting away whether the
> implementation is pure Java or proton-c-via-JNI.
> I'd like to check that folks are happy with me making this change, and to
> mention a couple of problems I've had.
> In this context, "client code" is anything outside the current
> sub-component, where our sub-components are Engine, Codec, Driver, Message
> and Messenger, plus each of the contrib modules, and of course third party
> code.
> To enforce this abstraction, I am planning to make the constructors of the
> affected classes package-private where possible.  I believe that, although
> third party projects might already be calling these constructors, it is
> acceptable for us to change its public API in this manner while Proton is
> such a young project.
> Please shout if you disagree with any of the above.
> Now, onto my problem.  I started off with the
> org.apache.qpid.proton.engine.
> impl package, and found that  o.a.q.p.hawtdispatch.impl.AmqpTransport calls
> various methods on ConnectionImpl and TransportImpl, so simply using a
> Connection and Transport will not work.  I don't know what to do about
> this, and would welcome people's opinions.
> Thanks
> Phil
> [1] for example, these work-in-progress classes:



*Hiram Chirino*

*Engineering | Red Hat, Inc.*

* <> | |*

*skype: hiramchirino | twitter: @hiramchirino<>

*blog: Hiram Chirino's Bit Mojo <>*

Reply via email to