Sorry I forgot to update the proposal with the JIRA number. The patch was attached to https://issues.apache.org/jira/browse/QPID-1831
Note this contains and impl for the first proposal. Rajith On Thu, May 7, 2009 at 11:28 AM, Gordon Sim <g...@redhat.com> wrote: > Rajith Attapattu wrote: >> >> I think a single destination impl should be able to handle any type >> and I demonstrated that in the patch with AMQXDestination class. >> We currently have a destination impl per exchange and I think that >> restricts flexibility and IMO this sort of specialization is >> unnecessary. > > Looking back through this thread, I can't see the patch anywhere. Did it get > stripped from your original email or am I just looking in the wrong place? > > AMQXDestination becomes an important part of the public API. It would be the > class that most users who want to populate their own jndi directory would > use. The name and class definition would be worth considering in that light, > and some java doc might be useful. > > --Gordon. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
