Thanks Nate - Thats exactly what I am trying to do now :( .....
Lalit Nagpal CSA, SunGard nmittler wrote: > > Unfortunately the CMS and JMS APIs do not provide this capability > directly. > What you could do is make it a string property and encode something at the > beginning (e.g. "int:123"), this way the application on the other end > knows > how to decode it. > > On 2/5/07, Lalit Nagpal <[EMAIL PROTECTED]> wrote: >> >> >> Hi >> >> Just observed the ::cms::Message header file in CMS API - latest trunk >> code >> .... The class gives different overloaded methods to store properties as >> int >> / float / string / double etc .... it also gives all the getter methods >> for >> retrieving properties for int / float and so on ..... >> >> In my code I try to loop into a set of name-value pairs that are passed >> to >> me and now need to be set in as message properties .... depending on data >> types I use the appropriate setter methods to set these ... like setInt >> for >> integer property etc .... >> >> Now at the receiving end (after the message has floated to the consumer) >> ideally situation should have been that I should know the datatype of the >> property that has been set somehow ..... this is not the case .... their >> is >> no way for me to know which property is of what data type ... this puts >> me >> in a fix and I need to apply a dirty patch here .... >> >> Can such a thing be added ..... The getter/setter methods do not solve >> the >> purpose in looping otherwise ... >> >> Regards >> >> Lalit Nagpal >> CSA, SunGard >> >> >> -- >> View this message in context: >> http://www.nabble.com/%3A%3Acms%3A%3AMessage-class-and-properties-tf3173160.html#a8802789 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/%3A%3Acms%3A%3AMessage-class-and-properties-tf3173160.html#a8820514 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
