Thanks!
I just ran a filter in JIRA for any closed or resolved issues in the
ActiveMQ space under CMS ... After looking the ActiveMQ release pages I
was able to figure it out :)
I think moving forward, it might be easier to have AMQ-CPP in it's own
space - that way the filter criteria gets a lot
Right now the CPP client only supports the stomp protocol, which does
not support temporary topics. So it's a limitation of the client in the
fact that it only supports the stomp protocol right now.
You could try one of the openwire clients, which you can get to from the
C Integration page
Hey Hiram,
BTW, I just googled for svn:eol-style and ran across this link
http://www.apache.org/dev/svn-eol-style.txt
I'm guessing I should probably have these settings before I commit? ...
oops! :)
Nate
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Hey guys, are we using this?
http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin
Seems like it might be a way to bridge between commits and issues.
Nate
I have just submitted a new C++ stomp client to the activemq SVN at
https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-cpp/
This serves as a full blown replacement for CMS, which didn't fully
implementation of the protocol.
Some of the features this includes are:
1) stomp
Arashad,
Looking at the code, it appears that Tim Bish has implemented
persistence in the activemq-cpp code
(https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-cpp/
). This is a full-on replacement for CMS, but you'll need v4.0.1 (or
later) of the broker. Unfortunately, I'm not
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
There is already a correlation-id header defined in the AMQ extensions:
http://www.activemq.org/site/stomp.html - I was trying to reuse this
header for the connect handshake. I don't feel that strongly one way or
the other. The name response-id is fine - we'd just have to add
another header to
confusion?
On 6/12/06, Mittler, Nathan [EMAIL PROTECTED] wrote:
There is already a correlation-id header defined in the AMQ
extensions:
http://www.activemq.org/site/stomp.html - I was trying to reuse this
header for the connect handshake. I don't feel that strongly one way
or
the other. The name
I don't seem to have the permission to assign issues to myself. Is
there some process for getting issues assigned, or should I just be able
to assign myself any issues I want?
Thanks,
Nate
Re-posting to the dev list...
-Original Message-
From: Mittler, Nathan [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 7:21 AM
To: activemq-users@geronimo.apache.org
Subject: RE: Stomp and TextMessage
So, here's my impression of what we need to do (feel free to make
mods)...
1
Please define the interfaces that you want to be SP-free!
I'm with Hiram ... I think the entire API should be SP-free. The less
the users have to see SPs, the better.
It's all about the user and helping them come up to speed and use the
api
as quickly and painlessly as possible. I understand
a generic ProtocolFormat would
do the trick. What do think otherwise, any other suggestions on how we better
could prepare for the upcoming merge!?
Regards,
Mats
-Original Message-
From: Mittler, Nathan [mailto:[EMAIL PROTECTED]
Sent: den 6 mars 2006 13:52
To: activemq-dev@geronimo.apache.org
to make it compile.
Regards,
Mats
-Original Message-
From: Mittler, Nathan [mailto:[EMAIL PROTECTED]
Sent: den 6 mars 2006 15:23
To: activemq-dev@geronimo.apache.org
Subject: RE: AMQ C#/C++ client refactoring suggestion
I'm still coming up to speed on the C#/C++ client so I'm not prepared
14 matches
Mail list logo
