[jira] [Created] (PROTON-339) [Proton-J] Implement Data interface in pure Java

2013-06-18 Thread Rob Godfrey (JIRA)
Rob Godfrey created PROTON-339:
--

 Summary: [Proton-J] Implement Data interface in pure Java 
 Key: PROTON-339
 URL: https://issues.apache.org/jira/browse/PROTON-339
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-j
Reporter: Rob Godfrey
Assignee: Rob Godfrey
 Fix For: 0.5




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (PROTON-340) AMQP to JMS transformer fails to properly map AMQP specific property types like UnsignedInteger

2013-06-18 Thread Hiram Chirino (JIRA)

 [ 
https://issues.apache.org/jira/browse/PROTON-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiram Chirino updated PROTON-340:
-

Attachment: PROTON-340.patch

Attaching fix for the bug.

 AMQP to JMS transformer fails to properly map AMQP specific property types 
 like UnsignedInteger
 ---

 Key: PROTON-340
 URL: https://issues.apache.org/jira/browse/PROTON-340
 Project: Qpid Proton
  Issue Type: Bug
Reporter: Hiram Chirino
Assignee: Hiram Chirino
 Fix For: 0.5

 Attachments: PROTON-340.patch


 Causes errors like:
 Caused by: javax.jms.MessageFormatException: Only objectified primitive 
 objects, String, Map and List types are allowed but was: 1 type: class 
 org.apache.qpid.proton.amqp.UnsignedInteger
   at 
 org.apache.activemq.command.ActiveMQMessage.checkValidObject(ActiveMQMessage.java:521)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:487)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:475)
   at 
 org.apache.activemq.command.ActiveMQBytesMessage.setObjectProperty(ActiveMQBytesMessage.java:896)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.setProperty(InboundTransformer.java:265)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:168)
   at 
 org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:508)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:489)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:262)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (PROTON-340) AMQP to JMS transformer fails to properly map AMQP specific property types like UnsignedInteger

2013-06-18 Thread Gordon Sim (JIRA)

 [ 
https://issues.apache.org/jira/browse/PROTON-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gordon Sim resolved PROTON-340.
---

Resolution: Fixed

 AMQP to JMS transformer fails to properly map AMQP specific property types 
 like UnsignedInteger
 ---

 Key: PROTON-340
 URL: https://issues.apache.org/jira/browse/PROTON-340
 Project: Qpid Proton
  Issue Type: Bug
Reporter: Hiram Chirino
Assignee: Hiram Chirino
 Fix For: 0.5

 Attachments: PROTON-340.patch


 Causes errors like:
 Caused by: javax.jms.MessageFormatException: Only objectified primitive 
 objects, String, Map and List types are allowed but was: 1 type: class 
 org.apache.qpid.proton.amqp.UnsignedInteger
   at 
 org.apache.activemq.command.ActiveMQMessage.checkValidObject(ActiveMQMessage.java:521)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:487)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:475)
   at 
 org.apache.activemq.command.ActiveMQBytesMessage.setObjectProperty(ActiveMQBytesMessage.java:896)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.setProperty(InboundTransformer.java:265)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:168)
   at 
 org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:508)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:489)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:262)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (PROTON-340) AMQP to JMS transformer fails to properly map AMQP specific property types like UnsignedInteger

2013-06-18 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686978#comment-13686978
 ] 

ASF subversion and git services commented on PROTON-340:


Commit 1494211 from [~gsim]
[ https://svn.apache.org/r1494211 ]

PROTON-340: map AMQP specific application property value types. Patch from 
Hiram Chirino.

 AMQP to JMS transformer fails to properly map AMQP specific property types 
 like UnsignedInteger
 ---

 Key: PROTON-340
 URL: https://issues.apache.org/jira/browse/PROTON-340
 Project: Qpid Proton
  Issue Type: Bug
Reporter: Hiram Chirino
Assignee: Hiram Chirino
 Fix For: 0.5

 Attachments: PROTON-340.patch


 Causes errors like:
 Caused by: javax.jms.MessageFormatException: Only objectified primitive 
 objects, String, Map and List types are allowed but was: 1 type: class 
 org.apache.qpid.proton.amqp.UnsignedInteger
   at 
 org.apache.activemq.command.ActiveMQMessage.checkValidObject(ActiveMQMessage.java:521)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:487)
   at 
 org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:475)
   at 
 org.apache.activemq.command.ActiveMQBytesMessage.setObjectProperty(ActiveMQBytesMessage.java:896)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.setProperty(InboundTransformer.java:265)
   at 
 org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:168)
   at 
 org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:508)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:489)
   at 
 org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:262)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


Re: Data interface in Proton-J

2013-06-18 Thread Rob Godfrey
On 18 June 2013 23:45, Leon Mlakar l...@digiverse.si wrote:


 Fetched them, thank you. It does help indeed


Great


 , At the first glance it looks like more than just 30% done.


I may have done a bit more work on it over the weekend :)

I didn't really want to check in something that was really no more than a
couple of hours of half-thought messing around (so now you have *several*
hours of half thought messing around checked in for you to look at :) ).


 I even manged to integrate the stuff into my project and get the DataImpl
 instance through the factory with no problems.


Excellent.


 Will take a closer look in the next days, though. All this proton stuff is
 still pretty much new to me, so I might have some basic questions (like
 what exactly should narrow and widen do :-) later on.


An excellent question... the fact that I didn't know was possibly one
reason why I didn't implement them (I think Rafi did tell me once what they
are supposed to be for)...


 But let me first got through the sources and dig through whatever archives
 I manage to find.


Great - just ping me if you have any problems.

Cheers,
Rob



 Cheers,

 Leon



 On 6/18/13 10:30 AM, Rob Godfrey wrote:

 OK - I've just committed [1] the initial pass at the Data implementation.

 Not yet implemented are the copy, append, narrow and widen operations...
 or
 much in the way of checking errors are handled the same way as the C, etc.

 If find issues and/or want to contribute patches you can attach
 comments/patch files to the JIRA [2].

 Hope this helps,
 Rob

 [1] https://svn.apache.org/**r1494067 https://svn.apache.org/r1494067
 [2] 
 https://issues.apache.org/**jira/browse/PROTON-339https://issues.apache.org/jira/browse/PROTON-339


 On 14 June 2013 16:13, Rob Godfrey rob.j.godf...@gmail.com wrote:

  T

 [...]