delta/python-packages/qpid-python.git/java/client/src/main, branch rajith_tmp

QPID-2273 : Fix Protocol Negotiation

2009-12-18T16:23:19+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@892301 13f79535-47bb-0310-9956-ffa450edef68

This is a fix for QPID-1830

2009-12-17T17:22:41+00:00

I have removed the checkReadable() method from the toBodyString()
This will enable the toString() method to be used any time on message.
I have also modified the Functions.str() to take in an additional parameter to denote to the starting position of the buffer.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@891805 13f79535-47bb-0310-9956-ffa450edef68

Update OSGI/Eclipse bundle versions and filenames for the 0.6 release

2009-12-10T14:08:45+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@889271 13f79535-47bb-0310-9956-ffa450edef68

QPID-2258 : AMQP0-9-1 Compliance fixes

2009-12-09T23:58:25+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@889022 13f79535-47bb-0310-9956-ffa450edef68

QPID-2242 : Update to 0-8 producer to set the JMS_QPID_DESTTYPE when sending messages.

2009-12-08T11:38:46+00:00

This update required a change to the FieldTable to clear any _encodedBuffer when setting a new value
Provided test in JMSDestintationTest. This test requires a broker that supports both 0-8/9 and 0-10 as we must first use a 0-10 connection to send a message, which does not set JMS_QPID_DESTTYPE, then receive the message on 0-8/9. This allows us to validate that messages recieved without JMS_QPID_DESTTYPE set will can correctly set the value without a BufferOverflow Exception when simply forwarding the message.

Excluded test from all cpp and InVM runs as test requires a 0-8/9 and 0-10 capable broker. Can reinstate to InVM when multiprotocol testing is capable.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@888345 13f79535-47bb-0310-9956-ffa450edef68

QPID-2242 : Update to the 0-8/9 code path to use the 0-10 static lookup tables for the Destination type when JMS_QPID_DESTTYPE has not been set.

2009-12-07T16:47:53+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@887994 13f79535-47bb-0310-9956-ffa450edef68

QPID-2242 : Removed unused AMQMessagseDelegate_0_10 constructor

2009-12-07T15:19:43+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@887951 13f79535-47bb-0310-9956-ffa450edef68

QPID-2242 : Fixed 0-10 code path's getJMSDestination() updated JMSDestinationTest to cover more test cases:

2009-12-07T15:17:18+00:00

- Recieving a msg via Queue,Topic
- Recieving a msg via Queue with a MessageListener
- Recieving a msg on a queue that was sent to a topic, requires JMX interface to perform message move.

Excluded test from 0-8 profile until the problem has been resolved

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@887948 13f79535-47bb-0310-9956-ffa450edef68

QPID-2192: restore erroneously removed setLinkedException()

2009-12-03T19:33:35+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@886890 13f79535-47bb-0310-9956-ffa450edef68

QPID-2192: remove extraneous printStackTrace()s

2009-12-02T01:48:58+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@886031 13f79535-47bb-0310-9956-ffa450edef68