JMS message type
in [Java Programming]
|
Prev: java threads context switching
Next: Urgent Openings: 1.(GIS, .Net) Web Developer, 2.QA Documentation(Jr level), 3.Business System Analyst, Austin, TX., 4.Maximo positions
From: Lew on 30 Jun 2010 08:37 gk wrote: >> Do you know the answer of my specific question ? If you want to help , >> could you please post the relevant link instead of the entire API. This is a discussion group, not a help desk. People donate their time to those who request help, for a variety of reasons that all boil down to generosity. One of the prerequisites for presumption on that generosity is appreciation for it. Jean-Baptiste obviously wants to help or he wouldn't have answered. You don't have the moral high ground to retort with, "If you want to help, ..." The trick is to understand how his advice helps. I have noticed that you have a tendency recently to ask questions that are answered in the fundamental documentation. Nothing will empower you as a programmer more than development of the ability to obtain your answers from that documentation. Ergo, Jean-Baptiste's advice is the most helpful anyone will give you on your question. -- Lew
From: Lew on 30 Jun 2010 08:50 gk wrote: > I don't understand the use of ByteMessage at all . Is it redundant > now ? or Still is in use ? From the Javadocs: "A BytesMessage object's message body contains a stream of uninterpreted bytes. This message type is for literally encoding a body to match an existing message format. In many cases, it is possible to use one of the other body types, which are easier to use. Although the JMS API allows the use of message properties with byte messages, they are typically not used, since the inclusion of properties may affect the format." > If could tell me a simple example where this could be of use that will > just wonderful . I did not find any concrete use of this . Could you > please explain this part ? Whether it's still in use is implicit in that it is not deprecated. The use case is where you want to send just raw bytes in the message. This is similar to ByteBuffer in the NIO library. Sometimes it's just more practical to think of content as a byte stream. -- Lew
From: gk on 30 Jun 2010 12:05 On 30 June, 17:50, Lew <no...(a)lewscanon.com> wrote: > gk wrote: > > I don't understand the use of ByteMessage at all . Is it redundant > > now ? or Still is in use ? > > From the Javadocs: > "A BytesMessage object's message body contains a stream of uninterpreted > bytes. This message type is for literally encoding a body to match an existing > message format. In many cases, it is possible to use one of the other body > types, which are easier to use. Although theJMSAPI allows the use of message > properties with bytemessages, they are typically not used, since the > inclusion of properties may affect the format." > > > If could tell me a simple example where this could be of use that will > > just wonderful . I did not find any concrete use of this . Could you > > please explain this part ? > > Whether it's still in use is implicit in that it is not deprecated. I can understand that. May be they could make it deprecate in later version (if not in use)! > > The use case is where you want to send just raw bytes in the message. This is > similar to ByteBuffer in the NIO library. Sometimes it's just more practical > to think of content as a byte stream. Yes . Thats implicit. ByteMessage itself implies to send just raw bytes in the message. What I was asking here is a practical example. Is there any situation you faced where you used this ?
From: Tom Anderson on 30 Jun 2010 17:44 On Wed, 30 Jun 2010, gk wrote: > On 30 June, 17:50, Lew <no...(a)lewscanon.com> wrote: >> gk wrote: >>> I don't understand the use of ByteMessage at all . Is it redundant >>> now ? or Still is in use ? >> >> The use case is where you want to send just raw bytes in the message. > > Yes . Thats implicit. ByteMessage itself implies to send just raw > bytes in the message. > > What I was asking here is a practical example. Is there any situation > you faced where you used this ? Not me. But say you were interacting with a CICS system via MQseries through its JMS interface. CICS messages look like this: https://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.wmq.bridge.doc/topics/fr11120_.html That's got to be a ByteMessage. tom -- You have now found yourself trapped in an incomprehensible maze.
From: Lew on 30 Jun 2010 19:47
gk wrote: >>> I don't understand the use of ByteMessage at all . Is it redundant >>> now ? or Still is in use ? Lew wrote: >> Whether it's still in use is implicit in that it is not deprecated. gk wrote: > I can understand that. May be they could make it deprecate in later > version (if not in use)! That's always true, even should it be in use. It seems very unlikely, though. AFAIK, Java APIs aren't deprecated based on popularity or lack thereof, but on technical concerns. Why do you think popularity is relevant to deprecation? -- Lew |