Le 25/05/2010 16:17, Rajith Attapattu a écrit :
Sure, pls file a JIRA and attach it.
Lets see what others also think.
The patch is attached to QPID-2627
https://issues.apache.org/jira/browse/QPID-2627
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
On Tue, May 25, 2010 at 10:25 AM, Emmanuel Bourg wrote:
> Le 25/05/2010 16:17, Rajith Attapattu a écrit :
>
>>> 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 th
Le 25/05/2010 16:17, Rajith Attapattu a écrit :
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 nec
On Tue, May 25, 2010 at 10:12 AM, Emmanuel Bourg 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. mi
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
clas
Hi,
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 cla
