This FAQ entry might help
http://incubator.apache.org/activemq/how-do-i-use-jms-efficiently.html
On 6/12/06, Erin Oceng <[EMAIL PROTECTED]> wrote:
Hi,
I am writing multithreaded MQ app code, I am not sure if this is ok (pseudo
code)
Connection connection = createConnection();
for ( each thr
I think that clears things up for me a bit - what you're proposing makes
sense. I'll poke around today and see what I can come up with.
Thanks,
Nate
On 6/12/06, Brian McCallister <[EMAIL PROTECTED]> wrote:
On Jun 12, 2006, at 4:14 PM, Nathan Mittler wrote:
> Agreed ... using the "type" heade
FWIW I'd like to have content-type header support. Couldn't we then
use content-type as the standard header that any Stomp-JMS bridge
would use to decide if something is a TextMessage or a BytesMessage?
On 6/13/06, Nathan Mittler <[EMAIL PROTECTED]> wrote:
I think that clears things up for me a
James,
I think that's what we're proposing here. I proposed "amq-msg-type",
but I suppose "content-type" is just as good. I think Brian's main
concern (Brian, correct me if I'm wrong) is that he'd like the mapping
of stomp message to AMQ message type to be pluggable, not hard-coded.
So if a user
On Jun 13, 2006, at 8:11 AM, Mittler, Nathan wrote:
James,
I think that's what we're proposing here. I proposed "amq-msg-type",
but I suppose "content-type" is just as good. I think Brian's main
concern (Brian, correct me if I'm wrong) is that he'd like the mapping
of stomp message to AMQ mes
I agree with all that. In a pure Stomp world, content-type is a very
useful header and probably affect how the stomp client processes the
message.
Whatever the default rule is for Stomp <-> JMS I'd have thought most
JMS providers would (through configuration or implementation) probably
use that t
Sounds good to me.
+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
Chirino
Sent: Tuesday, June 13, 2006 1:45 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
On 6/13/06, Mittler, Nathan <[EMAIL PROTECTED]> wrote:
> Just to
On Jun 13, 2006, at 10:36 AM, Hiram Chirino wrote:
The think your views are a bit STOMP point of view centric. bytes
messages work fine when both end assume you are just moving around
bytes messages.. and it's true everything can eventually converted
down to a byte[].
Yes, and no. I want to s
I would suggest that we use a weak form of specification encoding.
ActiveMQ already uses pseudo-urls in a lot of places, and named
transforms trump class names, usually:
yeah! URI style configuration rocks!
-Brian
--
Regards,
Hiram
Sure. that would be handy. But you could also eventualy support Map
messages too right?
That's certainly a possibility. We'd just have to come up with a form for
the body of the stomp frame in that case - shouldn't be terribly difficult.
With that said, I'm not seeing how I can do that
So it sounds like we're all in agreement on the content-type header. For
text, it would be something like "text" and for bytes it would be
"application/octet-stream". So this would not be an application-level
header, but would be used by my stomp client code to determine which message
type to cr
Hi all,
I have solve this problem
Arshad Ahamad writes:
Hi all,
I am compiling cmd code on SuSe(Linux machine-> i686-suse-linux,
version 2.6.13-15.8-default) , I am able to create the object file of this
code but when I make a executable file it gives the following error
On 6/13/06, Nathan Mittler <[EMAIL PROTECTED]> wrote:
So it sounds like we're all in agreement on the content-type header. For
text, it would be something like "text"
There could be a few values of Content-type which map to text
(text/xml, application/soap, application/xml etc).
Incidentally
[
https://issues.apache.org/activemq/browse/AMQ-716?page=comments#action_36326 ]
james strachan commented on AMQ-716:
Note that a workaround is to disable optimizeAcknowledge - e.g.
tcp://localhost:61616?jms.optimizeAcknowledge=false
> message is read
14 matches
Mail list logo
