On Tue, May 25, 2010 at 10:12 AM, Emmanuel Bourg <[email protected]> wrote: > Le 25/05/2010 16:02, Rajith Attapattu a écrit : > >> Even though the 0-10 code path is not using MINA as a transport, it >> still has to carry those jar files as a dependency due to, >> 1. our transports being in the common module >> 2. mina byte buffer being used in some of the common and client module >> classes, most notably the various message impl classes. >> >> Possible solutions, >> >> 1. Create a new transport module, and get the common module to load >> the transports via reflection. The 0-10 client already has such a >> mechanism. >> >> 2. Change all instance of mina byte buffer to the nio byte buffer. > > > I experimented a bit with the removal of the Mina ByteBuffer. Overall it's > pretty straightforward, but it becomes a little more tricky in the JMS > message hierarchy, that's the only place where the automatic growing feature > of the Mina buffer is necessary.
This is where our previous effort also got bogged down. > I stopped at this point but I have a partial patch ready for everything else > if you are interested. Sure, pls file a JIRA and attach it. Lets see what others also think. > Emmanuel Bourg > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
