RE: The future of the ActiveMQ C++ clients
Erin, a failover transport would be really cool, looking forward to a first glimpse. :) Please let me know if I we be of assistance in any way. It would be great if we all could unite and work on one client in the near future. Regards, Mats -Original Message- From: ErinO [mailto:[EMAIL PROTECTED] Sent: den 1 juni 2006 01:48 To: activemq-dev@geronimo.apache.org Subject: Re: The future of the ActiveMQ C++ clients Interesting, please pass along a snapshot. BTW, we are currently using Mat's CMS, and is trying to add failover transport to it. If your work can be easily combined with Mat's CMS work, that will be really cool. Erin Nathan Mittler wrote: > > Hey guys, > I've been working with a co-worker on a new c++ client that will > replace CMS and will truly support a pluggable protocol. We based > much of the code off of the .NET client, but had to do some > rearranging to get rid of protocol dependencies in the code. We're > nearing completion and have a full suite of CppUnit tests to go along > with it. The code base should be able to easily support the OpenWire > protocol as well (something CMS would have had some heartburn with). > > Up until now, Tim and I have just been working in secrecy off of our > own svn repo, since he doesn't have commit access to AMQ. But we > should have things to a decent state fairly soon (a couple of weeks, > perhaps). The first pass will only have STOMP implemented, but I was > hoping that once we get our stuff into Apache that you other guys > (Mats?) might give us a hand plugging in a connector for OpenWire? > > If anyone is interested, we can pass along a snapshot of our code base > so you can take a peek. > > Regards, > Nate > > On 5/30/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: >> >> Hi Mats, >> >> Yep, it should be possible to do 2 way ssl with ActiveMQ.. Perhaps >> the harder part will will finding a place to hold the client >> authentication info acquired from SSL to the broker. Perhaps we just >> stuff stuff into the connection info, not sure. >> >> I think it would be nice if all clients supported that feature, but I >> don't think it's a must have. >> >> As for the road map for the c++ clients, I'm hoping that things get >> consolidated down to 2 main sets of interfaces. 1st is the JMS like >> c++ API that supports all the features that the java client supports. >> 2nd is a simpler api that's perhaps only implemented using the stomp >> protocol. >> >> How we consolidate the APIs, I'm not sure. I think the C++ guys >> behind the different implementations are the ones that need to come >> to the table and discuss that. If they don't get consolidated, it >> might not be a bad thing. It gives users choice, and in the end they >> will pick what suits them best. >> >> Regards, >> Hiram >> >> On 5/30/06, Mats Forslöf <[EMAIL PROTECTED]> wrote: >> > Hi all, >> > >> > The openwire-cpp client is complete with one exception - the SSL part. >> The reason for this is that we would like it to support two-way SSL >> and before we starts to implement a two-way SSL socket we need to >> hear what you think about this regarding to the ActiveMQ server. Are >> there any problems with the current design to implement this and is >> it feasible for ActiveMQ to support it in the next release (4.1)? >> Also, should all clients (C, C++, .NET, Java) support this? >> > >> > How do we progress with the AMQ C++ clients. Do we have a roadmap >> > or >> any >> plans regarding the AMQ C++ clients? How do you think we should >> progress with the clients and into what? Should we merge the existing >> projects (OpenWire, STOMP, ...) or should they coexist? It is >> probably a bit confusing for the end users at the moment with several >> clients. I would like us to have a discussion on all this and more. >> Please, feel free to share your thoughts on the issues above. >> > >> > Regards, >> > Mats Forslöf >> > >> >> >> -- >> Regards, >> Hiram >> > > -- View this message in context: http://www.nabble.com/The+future+of+the+ActiveMQ+C%2B%2B+clients-t1704829.html#a4653968 Sent from the ActiveMQ - Dev forum at Nabble.com.
RE: [jira] Commented: (AMQ-656) Update of AMQ C++ client
Hi Nate! Once again thank you for applying uploaded patches, I've checked the code and it looks fine. There are some files, however, that should be removed from the "activemq-core" project since they are no longer used. The files are... activemq-core/src/gram/script GenerateCppMarshallingClasses.groovy GenerateCppMarshallingHeaders.groovy activemq-core/src/gram/java/org/apache/activemq/openwire/tool OpenWireCppMarshallingClassesScript.java OpenWireCppMarshallingHeadersScript.java Also, the above file names should be removed from the "openwire:generate" goal in maven.xml. <-- REMOVE! <-- REMOVE! Thanks! :) Regards, Mats -Original Message- From: Nathan Mittler (JIRA) [mailto:[EMAIL PROTECTED] Sent: den 27 maj 2006 16:02 To: activemq-dev@geronimo.apache.org Subject: [jira] Commented: (AMQ-656) Update of AMQ C++ client [ https://issues.apache.org/activemq/browse/AMQ-656?page=comments#action_36210 ] Nathan Mittler commented on AMQ-656: Mats, The 060518 patch has been applied and I moved the gram files to the activemq-core project. Let me know if everything is in order. Regards, Nate > Update of AMQ C++ client > > > Key: AMQ-656 > URL: https://issues.apache.org/activemq/browse/AMQ-656 > Project: ActiveMQ > Type: Improvement > Components: JMS client > Reporter: MF > Attachments: README.TXT, patch_060518.zip, source_060323.zip, > source_060324.zip, source_060404.zip, source_060406.zip, > source_060425.zip, source_060508.zip, source_060515.zip > > > Attached is a new update of the C++ client, the zip-file contains the full > source since the update is a major overhaul. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
AMQ C++ client: Encoding support added
Hi, Have uploaded a new update (http://issues.apache.org/activemq/browse/AMQ-656) for the C++ client which adds encoding support. It now contains an encoding framework with a default encoder that encodes to/from extended ASCII and modified UTF-8 as used in Java. The encoder can easily be replaced or turned off should you want to supply your own encoding. Also, a readme file has been added that documents the URI parameters and build commands. Tested on Windows XP (SP2), RedHat Enterprise Linux 4 and Mac OS X 10.4 with ActiveMQ broker 4.0 (pre-final). Regards, Mats
RE: ActiveMQ 4.0 final release candidate recut
Hi Hiram, I'm trying to run the 4th of May (Maven 1) build but it fails to download activemq-jaas-4.0.jar/activeio-core-3.0-beta3.jar. I tried to add the repository to the main pom.xml file but to no avail, any ideas why it won't work? Regards, Mats -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: den 5 maj 2006 16:24 To: activemq-dev@geronimo.apache.org Subject: Re: ActiveMQ 4.0 final release candidate recut I think that's because the parent pom has not been published to the official repository location yet. I think if you add http://people.apache.org/~chirino/incubator-activemq-4.0/maven2/ to your settings.xml then it should work. Regards, Hiram On 5/5/06, James Strachan <[EMAIL PROTECTED]> wrote: > Looks great! The notice files & licenses all look fine to me. > > The only minor nit right now is I can't run the activemq-web-demo and > activemq-web-console from the binary distro due to the parent pom not > downloading... > > http://www.rafb.net/paste/results/9SUFGr18.html > > On 5/5/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > Hi Folks, > > > > I have rebuild the final release candidate again. We are now > > including the activemq-web-demo and activemq-web-console projects in > > the example directory of the final distribution. Also we are now > > also will be publishing to a maven 2 repository in addition to the > > maven 1 repository. > > > > The > > https://svn.apache.org/repos/asf/incubator/activemq/tags/activemq-4. > > 0/activemq > > tag has been updated. > > > > The binary distributions are now at: > > http://people.apache.org/~chirino/incubator-activemq-4.0/maven1/incu > > bator-activemq/distributions/ > > > > The maven 1 repository layout for this release is at: > > http://people.apache.org/~chirino/incubator-activemq-4.0/maven1/ > > > > The maven 2 repository layout for this release is at: > > http://people.apache.org/~chirino/incubator-activemq-4.0/maven2/ > > > > > > -- > > Regards, > > Hiram > > > > > -- > > James > --- > http://radio.weblogs.com/0112098/ > -- Regards, Hiram
RE: [jira] Commented: (AMQ-656) Update of AMQ C++ client
Looks great, thanks! :) Regards, Mats -Original Message- From: Nathan Mittler (JIRA) [mailto:[EMAIL PROTECTED] Sent: den 28 april 2006 00:05 To: activemq-dev@geronimo.apache.org Subject: [jira] Commented: (AMQ-656) Update of AMQ C++ client [ https://issues.apache.org/activemq/browse/AMQ-656?page=comments#action_36104 ] Nathan Mittler commented on AMQ-656: Mats & David, I've added this patch to svn. Check it out and make sure all is as it should be :) Regards, Nate > Update of AMQ C++ client > > > Key: AMQ-656 > URL: https://issues.apache.org/activemq/browse/AMQ-656 > Project: ActiveMQ > Type: Improvement > Components: JMS client > Reporter: MF > Attachments: README.TXT, source_060323.zip, source_060324.zip, > source_060404.zip, source_060406.zip, source_060425.zip > > > Attached is a new update of the C++ client, the zip-file contains the full > source since the update is a major overhaul. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Update: ActiveMQ C++ Client
Hi, A new version has been uploaded to Jira http://issues.apache.org/activemq/browse/AMQ-656. The new version contains numerous improvements including: * Project renamed and source re-arranged into responsibility namespaces. Namespace "apache::activemq" contains the C++ ActiveMQ client implementation. Namespace "apache::cms" contains the "C++ Messaging Service" interfaces. Namespace "apache::ppr" contains the "Platform Portable Runtime" support and utility classes. * The file structure has been changed to use the same structure as other projects. * The protocol management has been improved to better support future pluggable protocols. A new URI parameter "protocol" has been added to select what protocol to use, currently only "openwire" supported. :) * The trace logging can now be turned on/off via the URI parameter "trace=true|false". * A new test case has been added that sends/receives a binary message asynchronously. More test cases will be added further on. * Transport filters has been introduced to make the transport layer all pluggable. * Bug fixes and other improvements including controlled shutdown by the new close() methods on session/connection. The code has been tested on Windows XP, RedHat Linux and Mac OS X using ActiveMQ broker 4.0RC1. Regards, Mats
RE: openwire-cpp question
If you can create a diff patch and send it to this mailing list it would be great. However, there area a size limitation on attachments in the mailing list so if the diff patch gets too large create a new issue in Apache JIRA (http://issues.apache.org/activemq/browse/AMQ) and attach it there. Thanks! Regards, Mats -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: den 20 april 2006 16:35 To: activemq-dev@geronimo.apache.org Subject: RE: openwire-cpp question Mats, Where do you want me to post the changes? Please let me know. Thanks! Vik -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: Thursday, April 20, 2006 3:50 AM To: activemq-dev@geronimo.apache.org Subject: RE: openwire-cpp question Hi Vik, Just a quick note regarding the OpenWire C++ client; the client is a work in progress, it has not been released yet - so expect bugs! We're playing catch-up with the broker and the C#-client and we didn't have the information on the protocol change until now. We will of course update the client with any protocol changes but we cannot give you a time fram other than as soon as possible. Can you please post the changes you had to make for compiling it on the Sun compiler, thanks. Regards, Mats -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: den 19 april 2006 19:55 To: activemq-dev@geronimo.apache.org Subject: RE: openwire-cpp question Hi Hiram, Thanks for the heads up. Can you please tell me where I can find your updated c client? David: are you planning to incorporate these changes in your code soon? Thanks! Vik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Wednesday, April 19, 2006 1:51 PM To: activemq-dev@geronimo.apache.org Subject: Re: openwire-cpp question On 4/19/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote: > Hey David, > > I was able to build this code on Sun Workshop 8, I had to put some OS > dependant condition checks, like you have for MACOS and have to modify code a > little bit here and there nothing major. > > I am able to run it with AMQ-RC2 but when I tried to run it with latest > SNAPSHOT (04/18) it was getting stuck after receiving BROKER_INFO command. > Wireformat may have changed a little.. perhaps we need to regenerate the openwire marshaller for c++ > I am not sure if latest SNAPSHOT is having issues because I had the same > problem with the STOMP C client it was getting stuck after sending the SUB > command. > There's been a small change to the stomp marshal ling. Before we were inconsistently adding \n after the \0 frame terminator. So I changed the activemq side to all ways consistently add the \n after the frame. It also expects frames that are sent to it to also have the \n. I could rollback the requirement for frames that it receive have a \n, but I think it would be better if the stomp protocol was a bit more consistent and just did things 1 way. So this could be what has broken some of the stomp clients. I've updated the c and ruby ones so that they work once again. > Thanks! > > Vik > > -Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 5:03 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > This code compiles and runs on GCC 3, GCC 4 and Visual Studio 2005. We have > never tried to compile it with Sun compiler. The code is tested and can > communicate with text messages with the broker (as our test code does). > > Hope to get the time to make the code compile with more C++ compilers as soon > as we get to a point where the code becomes complete. > > David > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: den 18 april 2006 23:37 > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > Hi David, > > I tried that code earlier and ran in to build issues, there are lots of > things in this code what Sun Compiler didn't liked. Is this code tested? > > Thanks! > > Vik > > -Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 18, 2006 2:55 AM > To: activemq-dev@geronimo.apache.org > Cc: Mats Forslöf > Subject: RE: openwire-cpp question > > The latest code is of the openwire cpp client was uploaded as a jira patch at > http://issues.apache.org/activemq/browse/AMQ-656. The latest version is > called "source 060406.zip". It contains the full source tree as well as make > files and a test program. > > /David > > -Original Message- > From: Mittler, Nathan [mailto:[EMAIL PROTECTED] > Sent: den 17 april 2006 17:28 &g
RE: openwire-cpp question
Hiram, Please specify what has changed in the protocol, it would save us a lot of time if someone could post these changes to the mailing list, if it already has been posted sorry for not observing it! Regards, Mats -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: den 19 april 2006 19:51 To: activemq-dev@geronimo.apache.org Subject: Re: openwire-cpp question On 4/19/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote: > Hey David, > > I was able to build this code on Sun Workshop 8, I had to put some OS > dependant condition checks, like you have for MACOS and have to modify code a > little bit here and there nothing major. > > I am able to run it with AMQ-RC2 but when I tried to run it with latest > SNAPSHOT (04/18) it was getting stuck after receiving BROKER_INFO command. > Wireformat may have changed a little.. perhaps we need to regenerate the openwire marshaller for c++ > I am not sure if latest SNAPSHOT is having issues because I had the same > problem with the STOMP C client it was getting stuck after sending the SUB > command. > There's been a small change to the stomp marshal ling. Before we were inconsistently adding \n after the \0 frame terminator. So I changed the activemq side to all ways consistently add the \n after the frame. It also expects frames that are sent to it to also have the \n. I could rollback the requirement for frames that it receive have a \n, but I think it would be better if the stomp protocol was a bit more consistent and just did things 1 way. So this could be what has broken some of the stomp clients. I've updated the c and ruby ones so that they work once again. > Thanks! > > Vik > > -Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 5:03 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > This code compiles and runs on GCC 3, GCC 4 and Visual Studio 2005. We have > never tried to compile it with Sun compiler. The code is tested and can > communicate with text messages with the broker (as our test code does). > > Hope to get the time to make the code compile with more C++ compilers as soon > as we get to a point where the code becomes complete. > > David > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: den 18 april 2006 23:37 > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > Hi David, > > I tried that code earlier and ran in to build issues, there are lots of > things in this code what Sun Compiler didn't liked. Is this code tested? > > Thanks! > > Vik > > -----Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 18, 2006 2:55 AM > To: activemq-dev@geronimo.apache.org > Cc: Mats Forslöf > Subject: RE: openwire-cpp question > > The latest code is of the openwire cpp client was uploaded as a jira patch at > http://issues.apache.org/activemq/browse/AMQ-656. The latest version is > called "source 060406.zip". It contains the full source tree as well as make > files and a test program. > > /David > > -Original Message- > From: Mittler, Nathan [mailto:[EMAIL PROTECTED] > Sent: den 17 april 2006 17:28 > To: activemq-dev@geronimo.apache.org > Cc: Mats Forslöf > Subject: RE: openwire-cpp question > > Hi Mats, > Is the code in svn your latest? I remember you including unit tests > and makefiles at some point - did these get lost when the last patch > was applied? > > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 11:08 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > There is no test stub either. I am wondering if someone ever tested it? > > Vik > > -Original Message- > From: Mittler, Nathan [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 11:01 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > Hmm ... that surprises me - I know the openwire-cpp team had included > makefiles in the past. I believe the code should support linux, > windows, & OSX. > > Does anyone know where the makefiles are? > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 10:08 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > Hey Nate, > > I don't see any make file or something in there? Do you have any idea > what O/S version and C++ complier this code recommends? > > Thanks!
RE: openwire-cpp question
Hi Vik, Just a quick note regarding the OpenWire C++ client; the client is a work in progress, it has not been released yet - so expect bugs! We're playing catch-up with the broker and the C#-client and we didn't have the information on the protocol change until now. We will of course update the client with any protocol changes but we cannot give you a time fram other than as soon as possible. Can you please post the changes you had to make for compiling it on the Sun compiler, thanks. Regards, Mats -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: den 19 april 2006 19:55 To: activemq-dev@geronimo.apache.org Subject: RE: openwire-cpp question Hi Hiram, Thanks for the heads up. Can you please tell me where I can find your updated c client? David: are you planning to incorporate these changes in your code soon? Thanks! Vik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Wednesday, April 19, 2006 1:51 PM To: activemq-dev@geronimo.apache.org Subject: Re: openwire-cpp question On 4/19/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote: > Hey David, > > I was able to build this code on Sun Workshop 8, I had to put some OS > dependant condition checks, like you have for MACOS and have to modify code a > little bit here and there nothing major. > > I am able to run it with AMQ-RC2 but when I tried to run it with latest > SNAPSHOT (04/18) it was getting stuck after receiving BROKER_INFO command. > Wireformat may have changed a little.. perhaps we need to regenerate the openwire marshaller for c++ > I am not sure if latest SNAPSHOT is having issues because I had the same > problem with the STOMP C client it was getting stuck after sending the SUB > command. > There's been a small change to the stomp marshal ling. Before we were inconsistently adding \n after the \0 frame terminator. So I changed the activemq side to all ways consistently add the \n after the frame. It also expects frames that are sent to it to also have the \n. I could rollback the requirement for frames that it receive have a \n, but I think it would be better if the stomp protocol was a bit more consistent and just did things 1 way. So this could be what has broken some of the stomp clients. I've updated the c and ruby ones so that they work once again. > Thanks! > > Vik > > -Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 5:03 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > This code compiles and runs on GCC 3, GCC 4 and Visual Studio 2005. We have > never tried to compile it with Sun compiler. The code is tested and can > communicate with text messages with the broker (as our test code does). > > Hope to get the time to make the code compile with more C++ compilers as soon > as we get to a point where the code becomes complete. > > David > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: den 18 april 2006 23:37 > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > Hi David, > > I tried that code earlier and ran in to build issues, there are lots of > things in this code what Sun Compiler didn't liked. Is this code tested? > > Thanks! > > Vik > > -Original Message- > From: David Fahlander [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 18, 2006 2:55 AM > To: activemq-dev@geronimo.apache.org > Cc: Mats Forslöf > Subject: RE: openwire-cpp question > > The latest code is of the openwire cpp client was uploaded as a jira patch at > http://issues.apache.org/activemq/browse/AMQ-656. The latest version is > called "source 060406.zip". It contains the full source tree as well as make > files and a test program. > > /David > > -Original Message- > From: Mittler, Nathan [mailto:[EMAIL PROTECTED] > Sent: den 17 april 2006 17:28 > To: activemq-dev@geronimo.apache.org > Cc: Mats Forslöf > Subject: RE: openwire-cpp question > > Hi Mats, > Is the code in svn your latest? I remember you including unit tests > and makefiles at some point - did these get lost when the last patch > was applied? > > > -Original Message- > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 11:08 AM > To: activemq-dev@geronimo.apache.org > Subject: RE: openwire-cpp question > > There is no test stub either. I am wondering if someone ever tested it? > > Vik > > -Original Message- > From: Mittler, Nathan [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 11:01 AM > To: activemq-dev@gero
RE: Update: AMQ C++ Client: First working draft
Hi Hiram, Yes, it is the content length but its value is always 4 less than the actual content length (calculated from the first content byte at position 5). Regards, Mats -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: den 5 april 2006 18:31 To: activemq-dev@geronimo.apache.org Subject: Re: Update: AMQ C++ Client: First working draft Hi Mats, Feature. Consider it to be like content-length Regards, Hiram On 4/5/06, Mats Forslöf <[EMAIL PROTECTED]> wrote: > Hi, > > A new update has been uploaded to > http://issues.apache.org/activemq/browse/AMQ-656, see issue for more details. > > When debugging the OpenWire protocol we've found an issue; the size > counter (first 4 bytes) of all packages received from the server is > always 4 numbers short of the actual package size (excluding the > counter itself)!? Bug or feature?? :) > > Regards, > Mats > > -- Regards, Hiram
Update: AMQ C++ Client: First working draft
Hi, A new update has been uploaded to http://issues.apache.org/activemq/browse/AMQ-656, see issue for more details. When debugging the OpenWire protocol we've found an issue; the size counter (first 4 bytes) of all packages received from the server is always 4 numbers short of the actual package size (excluding the counter itself)!? Bug or feature?? :) Regards, Mats
RE: Regarding feedback on OpenWire C++ client
Nate,
>You get no benefits at all by adding smart pointers to the interface.
>The user will delete their objects whenever they wish, regardless of
>what the openwire library does ... and if it does so, the openwire
>library will explode as soon as it tries to reference it. That's the
>thing - this is C++ and there is no mechanism to prevent someone from
>coding badly, and adding smart pointers to the API isn't going to change
>that. The user is responsible for both adding and removing referenes to
>its objects. And it's not the job of the openwire lib to worry about
>memory management in the user-domain - it should only be concerned with
>its own memory management.
>In addition, smart pointers are assuming that the object is allocated on
>the heap, as it will do a "delete" when the last reference is removed.
>This is wrong, because the user should be able allocate its objects in
>whatever way makes sense for the application.
>Also, adding smart pointer arguments to all the methods on the api makes
>it complicated and ugly. If the openwire library wants to use smart pointers
>internally, that's fine, but it shouldn't impose the use of smart pointers
>on the user. It's our job to make the user's experience a good one so they
>continue to use ActiveMQ in their applications.
Please define the interfaces that you want to be SP-free!
>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 that in these cases
>you're passing a pointer and not copying, but it complicates the user
>interface when the person just wants to pass in a string. They shouldn't
>have to create a string on the heap an then wrap it in a smart pointer to
>just call a function.
Just a quick note, this is not necessary with the current design of accepting
"const char*" and returning p. The user can easily extract the const
char from the SP string if wanted.
>Class Xxx {
> std::string name;
> void setName (const std::string& name) {
>this->name = name;
> }
> const std::string& getName () const {
>return this->name;
> }
>};
Shall we agree on the one above?
Regards,
Mats & David
RE: Regarding feedback on OpenWire C++ client
Hi Hiram, >> 5) .NET namespace >> >> Hiram, what rules does Apache imply on this? Is it ok to use the namespaces >> your giving examples on? Looking on the Java code all Apache code starts >> with org.apache. >> > >As far as I know the org.apache namespace is a Java thing as it's the only >language the encourages that form. I've never seen this form use in other >languages yet. Even so it might be better to be a bit overzealous to prevent namespace clashes :) If ASF does not have any rules about this we'll change it - no problem. However, if we're to sync the names between C# and C++ the C# name spaces should be altered also!? C# namespace cms namespace activemq.command namespace activemq.core namespace activemq.io C++ namespace cms namespace activemq::command namespace activemq::io namespace activemq::marshal namespace activemq::protocol namespace activemq::transport namespace activemq::util Regards, Mats
RE: New AMQ C++ client update
Hi Erin, See previous post regarding stability/bugs. To run the scripts to generate the commands you'll need to the source and Maven 1.0.2. Go to the activemq-core subdirectory and run 'maven -o openwire:generate". You should omit the "-o" (offline) flag the first time so Maven downloads all required libs. If you're running on Windows you need to patch the maven.xml by adding a line beneatch section , see below. <--- Add this line The path problem is known and will be fixed in a later version of AMQ. Remember to update the scripts from the C++ client update. Regards, Mats -Original Message- From: ErinO [mailto:[EMAIL PROTECTED] Sent: den 24 mars 2006 23:36 To: activemq-dev@geronimo.apache.org Subject: Re: New AMQ C++ client update Hi, It is nice to try the C++ client update. Although there are some glitches (reference count problem, non-initialized variables etc.), I got the client talk to a broker, seems there are some marshalling issues which I don't know how to solve them. The C++ client tried to talk to a ActiveMQ4.0 M4 broker, they didn't understand each other, I am wondering which version's broker the client should talk to? RC? Could you please also tell me how to regenerate the command classes? Seems the page on the ActiveMQ.org shows how to use the groovy scripts is broken. Thanks Erin -- View this message in context: http://www.nabble.com/New-AMQ-C%2B%2B-client-update-t1330048.html#a3580516 Sent from the ActiveMQ - Dev forum at Nabble.com.
Regarding feedback on OpenWire C++ client
Hi All, Thanks everyone for looking at and testing the latest C++ client update. Sorry if we have not been so clear regarding the stability of the code, the code is highly untested and as said in the upload mail we will commence testing/debugging shortly - so expect bugs!! As we've just finished the port we will shift focus and look into all the issues you have raised, see comments below. 1) Use of smart pointers. Though the user interface would be cleaner without smart pointers they serves a purpose even when the passed in object is not owned by the client. As soon as an object is shared between two classes you have the problem when the object should be deleted - this problem is eliminated when using SP's, the object is deleted when both object releases its reference to it. SP's and Strings: Semi-agreed :) The setters should all have "const char*" but we could change the getters to std:string (without SP), then it is up to the user to either use it as a std:string or a "const char*". 2) ITextMessage should extend IMessage This was a last minute change to make it compile. Nate, your solution seems to be a viable way of handling it - thanks! 3) SP dynamic_cast rather than reinterpret_cast It is correct that reinterpret_cast<> does not adjust the pointer value as needed when casting between different classes in a class hierarchy. However, the reinterpret_cast<> is used for casting between void* and objects and is needed for the p<> template to work. Where such pointer-value-adjustment is needed (up/down-casting), static_cast<> is used which works the same as dynamic_cast<> except that it does no runtime type check. 4) ExceptionListener An ExceptionListener is missing. We could either add a method on IMessageListener or add a new interface IExceptionListener, prefer the latter. Ok? 5) .NET namespace Hiram, what rules does Apache imply on this? Is it ok to use the namespaces your giving examples on? Looking on the Java code all Apache code starts with org.apache. Regards, Mats & David
New AMQ C++ client update
Hi, The new update should make the C++ client on par with the C# client. The client is now APR free which makes it totally independent of 3rd party libs and it compiles on both Windows and Linux (make files and updated groovy scripts included). Also, we have made a slight architectural re-design that differs from the C# client on the marshalling part - because of this there is no need for all the marshallers/registry. If any OpenWire guru could look through the marshalling part, to make sure we don't have made any obvious mistake, it would be appreciated. We will start testing/debugging shortly, however there are still some things that need some more work or are missing; - Support for UTF-8 - Exception handling - SocketFactory/SSL Socket - ActiveMQStream/ObjectMessage - Code comments The update is uploaded to a Jira issue, http://jira.activemq.org/jira/browse/AMQ-656. Regards, Mats
RE: OpenWire tight/loose encoding
Ok, thanks. Applied the patch on the C++ code. Regards, Mats -Original Message- From: James Strachan [mailto:[EMAIL PROTECTED] Sent: den 17 mars 2006 08:05 To: activemq-dev@geronimo.apache.org Subject: Re: OpenWire tight/loose encoding BTW I made a slight change to OpenWire the other day, turning Command.commandId into an int rather than a short (so that we can reuse it as a reliability counter when using unreliable transports like UDP/multicast) - I hope it does't cause too many problems in the C/C++ code. I"ve patched the C# code but the C/C++ code still needs upgrading. James On 3/17/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > Great! > > I can't wait to peek at the patch! > > Regards, > Hiram > > On 3/16/06, Mats Forslöf <[EMAIL PROTECTED]> wrote: > > Hi Hiram > > > > Thanks for the update. We have already selected the loose encoding as the > > default encoding in the C++ client, it's good to see that we have selected > > the same. The tight encoding is deferred to a future release since it is a > > bit more complicated and we wanted something up and running. We're just > > finished a architectural re-design in the C++ client that makes a lot less > > code to maintain and a bit easy to add other protocols (see previous posts > > regarding C++ refactoring suggestion). > > > > Will get back soon with a new patch udpate including updated groovy scripts. > > > > Regards, > > Mats > > > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Hiram Chirino > > Sent: den 16 mars 2006 13:46 > > To: activemq-dev@geronimo.apache.org > > Subject: Re: OpenWire tight/loose encoding > > > > Hi Mats! > > > > On 3/16/06, Mats Forslöf <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > We need some additional information on the OpenWire protocol to wrap up > > > our work on the C++ AMQ client. > > > > > > 1. To use loose encoding what do we have to do, is it simply to set the > > > tight encoding attribute to false on the OpenWireFormat package and then > > > send each package attributes one after each other? > > > > > > > OpenWire should always start up in loose encoding mode, in version 1 of the > > protocol, with all options off by default. This ensures backward > > compatibitlity since future clients will beforced to be backward compatible > > to even start talking. The clients then exchange a WireFormatInfo which > > contains information about the highest version of the protocol and > > requested protocol options that should be turned on. After that exchange > > both sides can upgrade the version and options to a set that is compatible > > between the 2 ends. > > > > > 2. What determines the order of the attributes on each package? The order > > > now seems to be determined by the groovy scripts. > > > > They are in the order that they were defined in the orifinal Java command > > classes. The groovy script just preserves the order. > > > > > > > > 3. What about the order of the boolean flags used in tight encoding, what > > > does each position stand for? > > > > > > > The bits in the BooleanStream are also serialized in the same order. > > > > > I must ask you of some documentation on this because we cannot verify > > > that our code is correct otherwise. > > > > > > > Any time! I guess we need to update the C++ guy to support loose encoding > > since that is now the minimum requirement. At least it's much simpler to > > implement. Should I work on that or have you guys allready have that > > covered? > > > > Regards, > > Hiram > > > > > Please help! > > > > > > Regards, > > > Mats Forslöf > > > > > > > > > -- > > Regards, > > Hiram > > > > > -- > Regards, > Hiram > -- James --- http://radio.weblogs.com/0112098/
OpenWire tight/loose encoding
Hi, We need some additional information on the OpenWire protocol to wrap up our work on the C++ AMQ client. 1. To use loose encoding what do we have to do, is it simply to set the tight encoding attribute to false on the OpenWireFormat package and then send each package attributes one after each other? 2. What determines the order of the attributes on each package? The order now seems to be determined by the groovy scripts. 3. What about the order of the boolean flags used in tight encoding, what does each position stand for? I must ask you of some documentation on this because we cannot verify that our code is correct otherwise. Please help! Regards, Mats Forslöf
RE: AMQ C#/C++ client refactoring suggestion
Yes, both the command and marshalling code is auto generated so the marshalling part must be moved into the command generation if we make the change. We're using Windoze for development at the moment but the code are prepared for *nix platforms. However we havn't had an opportunity yet to test it on those platforms, it should require only minor tweaks to make it compile though. Note however that the code is incomplete for functional tests at the moment but it should compile. If you can help out with this it would be great. Also, you need the Apache Portable Runtime 1.22 library 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 just yet to offer suggestions on architecture (at least, probably nothing terribly worthwhile). At the surface, what you're proposing makes sense. The one question I have is: how does this affect code generation? Are we currently auto generating both the marshalling and command code? If so, it seems like consolidating would make the set of groovy scripts smaller, which would be a good thing. BTW, I've been having trouble compiling the openwire-cpp code. I'm on Linux with gcc 4.0.0. Have you been able to get the code compiling? Thanks, Nate -----Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: Monday, March 06, 2006 8:09 AM To: activemq-dev@geronimo.apache.org Subject: RE: AMQ C#/C++ client refactoring suggestion Hi Nate, Thanks, that is an excellent suggestion, using 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 Subject: RE: AMQ C#/C++ client refactoring suggestion Hi Mats, One thing to keep in mind is that we're going to start merging our efforts in the future (at least on the C++ side). I believe that means (please correct me if I'm wrong) that what is currently the openwire c++ client will eventually be extended to support other protocols (such as Stomp). If that's the case, adding protocol-specific marshalling methods to the Commands may get hairy. Perhaps rather than the marshal/unmarshall methods taking an OpenWireFormat object, they could take a more generic type, such as a ProtocolFormat, for example? This way, the Command interface could be reused across protocols and the higher-level code could eventually be reworked such that it doesn't care about which protocol it's using. Regards, Nate -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: Monday, March 06, 2006 7:05 AM To: activemq-dev@geronimo.apache.org Subject: AMQ C#/C++ client refactoring suggestion The marshalling is currently done by a set of stand-alone objects inherited from BaseDataStreamMarshaller or BaseCommandMarshaller. An alternative design would be to let each command itself be marshall aware, that is, have them implement a marshalling interface that has two methods; marshal and unmarshal. One of the parameters to those methods would be OpenWireFormat, the command calls marshall/unmarshall on the OpenWireFormat object for each command attribute. OpenWireFormat then performs the actual marshalling by a helper class called DataStreamMarshaller and depending on what the OpenWireFormat attribute "tightEncoding" is set to OpenWireFormat calls either tight or loose marshalling. The benefit of this would be less code and the control of tight/loose marshalling is done in one place. Please let me know what you think, I may have missed something that makes this unsuitable. Regards, Mats
RE: Patch: C++ command generation scripts
Oops, didn't work this time either :), uploaded to http://jira.activemq.org/jira/browse/AMQ-603. Regards, Mats -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: den 2 mars 2006 08:20 To: activemq-dev@geronimo.apache.org Subject: Patch: C++ command generation scripts I have tweaked the C++ command generation scripts a bit to make them generate more precise types and includes, see attached files. Regards, Mats
Patch: C++ command generation scripts
I have tweaked the C++ command generation scripts a bit to make them generate more precise types and includes, see attached files. Regards, Mats
RE: Minor build problem
No problemo, either copying it to lib/ext or adding will do the trick. Regards, Mats -Original Message- From: James Strachan [mailto:[EMAIL PROTECTED] Sent: den 27 februari 2006 10:39 To: activemq-dev@geronimo.apache.org Subject: Re: Minor build problem On 27 Feb 2006, at 08:57, Mats Forslöf wrote: > James, > > I'm trying to run the "openwire:generate" target but it fails with > > openwire:generate: > [java] Parsing source files in directory: src/main/java/org/ > apache/activemq/command > [java] java.lang.NoClassDefFoundError: com/sun/javadoc/Type > [java] at > org.codehaus.jam.provider.JamServiceFactoryImpl.createSourceBuilder > (JamServiceFactoryImpl.java:205) > [java] at > org.codehaus.jam.provider.JamServiceFactoryImpl.createBuilder > (JamServiceFactoryImpl.java:158) > [java] at > org.codehaus.jam.provider.JamServiceFactoryImpl.createClassLoader > (JamServiceFactoryImpl.java:137) > [java] at > org.codehaus.jam.provider.JamServiceFactoryImpl.createService > (JamServiceFactoryImpl.java:78) > [java] at org.codehaus.gram.Gram.main(Gram.java:33) > [java] Exception in thread "main" > [java] [ERROR] Java Result: 1 > > Using JDK 1.4.2, maven 1.0.2 and have set both the JAVA_HOME and > MAVEN_HOME. Have I missed something obvious? Ah sorry about that. The build seems to work fine on OS X but sometimes can fail on windows boxes (am guessing you're on windows?) due to the javadoc classes not being on the classpath. Its the JAM library we're using relying on javadoc rather than QDox which is causing the issue. I think if you add the jar manually to your CLASSPATH variable (or copy it into lib/ext) it should fix it. I'm sure with some maven hacking we can figure out how to fix this, maybe by trying to add the jar to the classpath in the maven.xml. I can't remember the jar on windows - I think its tools.jar. You could try patch maven.xml in activemq-core line 105 and try adding some line like or something and that might fix it. James --- http://radio.weblogs.com/0112098/
Minor build problem
James, I'm trying to run the "openwire:generate" target but it fails with openwire:generate: [java] Parsing source files in directory: src/main/java/org/apache/activemq/command [java] java.lang.NoClassDefFoundError: com/sun/javadoc/Type [java] at org.codehaus.jam.provider.JamServiceFactoryImpl.createSourceBuilder(JamServiceFactoryImpl.java:205) [java] at org.codehaus.jam.provider.JamServiceFactoryImpl.createBuilder(JamServiceFactoryImpl.java:158) [java] at org.codehaus.jam.provider.JamServiceFactoryImpl.createClassLoader(JamServiceFactoryImpl.java:137) [java] at org.codehaus.jam.provider.JamServiceFactoryImpl.createService(JamServiceFactoryImpl.java:78) [java] at org.codehaus.gram.Gram.main(Gram.java:33) [java] Exception in thread "main" [java] [ERROR] Java Result: 1 Using JDK 1.4.2, maven 1.0.2 and have set both the JAVA_HOME and MAVEN_HOME. Have I missed something obvious? Regards, Mats
RE: Patch: C++ client
Uploaded the file to http://jira.activemq.org/jira/browse/AMQ-592. Have only had time to briefly look at the new groovy scripts but they seem to be okay, will try them out shortly. Congrats with the C# client, we need a little more work on the C++ client before the first test flight but we're getting there. Mats -Original Message- From: James Strachan [mailto:[EMAIL PROTECTED] Sent: den 24 februari 2006 16:33 To: activemq-dev@geronimo.apache.org Subject: Re: Patch: C++ client On 24 Feb 2006, at 08:30, Mats Forslöf wrote: > Having the same troubles again sending a patch to the mailing list, > should I upload it somewhere else or what is the right procedure? Sorry about that - Apache mail lists limit email size. I wonder could you attach it to a JIRA issue and post a URL? Many thanks! BTW I've got the C# client working now - will explain all in a few hours, so I should be in a good position to auto-create the marshalling code for C++ now. James > > Mats > > -Original Message- > From: Mats Forslöf [mailto:[EMAIL PROTECTED] > Sent: den 24 februari 2006 09:28 > To: activemq-dev@geronimo.apache.org > Subject: Patch: C++ client > > > Attached is a patch with numerous improvements as well as added > support for Map and Bytes messages. All classes within the > ActiveMQDestination tree is more complete since they are manually > maintained in the command hierarchy. > > Regards, > Mats James --- http://radio.weblogs.com/0112098/
RE: Patch: C++ client
Having the same troubles again sending a patch to the mailing list, should I upload it somewhere else or what is the right procedure? Mats -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: den 24 februari 2006 09:28 To: activemq-dev@geronimo.apache.org Subject: Patch: C++ client Attached is a patch with numerous improvements as well as added support for Map and Bytes messages. All classes within the ActiveMQDestination tree is more complete since they are manually maintained in the command hierarchy. Regards, Mats
Patch: C++ client
Attached is a patch with numerous improvements as well as added support for Map and Bytes messages. All classes within the ActiveMQDestination tree is more complete since they are manually maintained in the command hierarchy. Regards, Mats
Build tools: Groovy scripts
Hi, According to the source in module openwire-dotnet the commands are auto generated via a set of Grovvy scripts located in the activemq-openwire module. It would be nice to do the same for the openwire-cpp commands - anyone that knows where the scripts are, can't find them? Regards, Mats
RE: Trouble uploading OpenWire C++ client to mailing list
Thanks! :) Regards, Mats -Original Message- From: Hiram Chirino [mailto:[EMAIL PROTECTED] Sent: den 13 februari 2006 18:50 To: activemq-dev@geronimo.apache.org Subject: Re: Trouble uploading OpenWire C++ client to mailing list Hi Mats, I just finished committing the patch. I put it under activemq/ openwire-cpp. I uploaded the smart pointer header dependencies that the code has up to http://www.codehaus.org/~chirino/util/ifr/v1 It should be possible to cook up a build script the does a wget of the .hpp files automatically so that folks don't need to manually download. Regards, Hiram On Feb 13, 2006, at 12:33 PM, Hiram Chirino wrote: > Good point.. Since it s port of the c# stuff I guess it's quite > different than brand new stuff. I'll get it checked in today. > > Regards, > Hiram > > > On Feb 13, 2006, at 10:26 AM, Mats Forslöf wrote: > >> >> Is that really necessary in this case?? The code is a port of your C# >> client so the code is _very_ similar, shouldn't be any problem with >> IP there. :-) >> >> Regards, >> Mats >> >> -Original Message- >> From: Hiram Chirino [mailto:[EMAIL PROTECTED] >> Sent: den 13 februari 2006 16:11 >> To: activemq-dev@geronimo.apache.org >> Subject: Re: Trouble uploading OpenWire C++ client to mailing list >> >> Hi Matts! >> >> Awesome work! There's just so much of it! Usually it's no problem >> to accept a small patch, but with larger patches Apache likes to get >> a Contributor License Agreement (CLA) to make sure the IP is clear. >> If you get a chance, could you fill out and fax in the following >> form??? >> >> http://www.apache.org/licenses/icla.pdf >> >> Thanks, >> Hiram >> >> >> On Feb 13, 2006, at 3:50 AM, Mats Forslöf wrote: >> >>> Thanks Hiram! >>> >>> The source is uploaded onto issue Geronimo-1623. The code is split >>> into two files, one for the C++ client and one for Davids source >>> that should be "pulled" from his site on a build. Please let me know >>> how we should proceed, we need help from James or someone to get the >>> auto generation of the commands going. >>> >>> Regards, >>> Mats >>> >>> -Original Message- >>> From: Hiram Chirino [mailto:[EMAIL PROTECTED] >>> Sent: den 10 februari 2006 17:01 >>> To: activemq-dev@geronimo.apache.org >>> Subject: Re: Trouble uploading OpenWire C++ client to mailing list >>> >>> Hi Mats, >>> >>> As a work around, >>> Try putting it in the geronimo JIRA here: http://issues.apache.org/ >>> jira/secure/BrowseProject.jspa?id=10220 >>> Assign it to the ActiveMQ component and we should be able to find >>> it. >>> >>> Regards, >>> Hiram >>> >>> On Feb 10, 2006, at 6:20 AM, Mats Forslöf wrote: >>> >>>> Hi Rob, >>>> >>>> The patch is not more than 10k in compressed form. I tried to >>>> upload it to Jira again but with the same proxy problem. >>>> >>>> Mats >>>> >>>> -Original Message- >>>> From: Rob Davies [mailto:[EMAIL PROTECTED] >>>> Sent: den 10 februari 2006 11:40 >>>> To: activemq-dev@geronimo.apache.org >>>> Subject: Re: Trouble uploading OpenWire C++ client to mailing list >>>> >>>> There's been some problems today with jira - but seems to be >>>> working ok now. >>>> Attaching the file to jira seems the best thing todo - how big is >>>> the patch ? >>>> >>>> cheers, >>>> >>>> Rob >>>> >>>> On 10 Feb 2006, at 08:44, Mats Forslöf wrote: >>>> >>>>> Great, adding it to Jira doesn't work either, got a proxy error, >>>>> see below. >>>>> >>>>> Proxy Error >>>>> The proxy server received an invalid response from an upstream >>>>> server. >>>>> The proxy server could not handle the request POST /jira/secure/ >>>>> CreateIssueDetails.jspa. >>>>> >>>>> Reason: Error reading from remote server >>>>> >>>>> -- >>>>> -- >>>>> - >>>>> - >>>>> -- >>>>> >>>>> Apache/2.0.52 (Fedora) Server at jira.activemq.org Port 80 >>>>> >>>>> Any ideas on how to upload the patch? >>>>> >>>>> Regards, >>>>> Mats >>>>> >>>>> -Original Message- >>>>> From: Mats Forslöf [mailto:[EMAIL PROTECTED] >>>>> Sent: den 10 februari 2006 09:18 >>>>> To: activemq-dev@geronimo.apache.org >>>>> Subject: Trouble uploading OpenWire C++ client to mailing list >>>>> >>>>> Hi, >>>>> >>>>> I've been tryint to send patches to this mailing list but it >>>>> doesn't seem to work. Should I put in a Jira isssue instead? >>>>> >>>>> Regards, >>>>> Mats
RE: Trouble uploading OpenWire C++ client to mailing list
Thanks Hiram! The source is uploaded onto issue Geronimo-1623. The code is split into two files, one for the C++ client and one for Davids source that should be "pulled" from his site on a build. Please let me know how we should proceed, we need help from James or someone to get the auto generation of the commands going. Regards, Mats -Original Message- From: Hiram Chirino [mailto:[EMAIL PROTECTED] Sent: den 10 februari 2006 17:01 To: activemq-dev@geronimo.apache.org Subject: Re: Trouble uploading OpenWire C++ client to mailing list Hi Mats, As a work around, Try putting it in the geronimo JIRA here: http://issues.apache.org/ jira/secure/BrowseProject.jspa?id=10220 Assign it to the ActiveMQ component and we should be able to find it. Regards, Hiram On Feb 10, 2006, at 6:20 AM, Mats Forslöf wrote: > Hi Rob, > > The patch is not more than 10k in compressed form. I tried to upload > it to Jira again but with the same proxy problem. > > Mats > > -Original Message- > From: Rob Davies [mailto:[EMAIL PROTECTED] > Sent: den 10 februari 2006 11:40 > To: activemq-dev@geronimo.apache.org > Subject: Re: Trouble uploading OpenWire C++ client to mailing list > > There's been some problems today with jira - but seems to be working > ok now. > Attaching the file to jira seems the best thing todo - how big is the > patch ? > > cheers, > > Rob > > On 10 Feb 2006, at 08:44, Mats Forslöf wrote: > >> Great, adding it to Jira doesn't work either, got a proxy error, see >> below. >> >> Proxy Error >> The proxy server received an invalid response from an upstream >> server. >> The proxy server could not handle the request POST /jira/secure/ >> CreateIssueDetails.jspa. >> >> Reason: Error reading from remote server >> >> - >> - >> -- >> >> Apache/2.0.52 (Fedora) Server at jira.activemq.org Port 80 >> >> Any ideas on how to upload the patch? >> >> Regards, >> Mats >> >> -Original Message- >> From: Mats Forslöf [mailto:[EMAIL PROTECTED] >> Sent: den 10 februari 2006 09:18 >> To: activemq-dev@geronimo.apache.org >> Subject: Trouble uploading OpenWire C++ client to mailing list >> >> Hi, >> >> I've been tryint to send patches to this mailing list but it doesn't >> seem to work. Should I put in a Jira isssue instead? >> >> Regards, >> Mats
RE: Trouble uploading OpenWire C++ client to mailing list
Hi Rob, The patch is not more than 10k in compressed form. I tried to upload it to Jira again but with the same proxy problem. Mats -Original Message- From: Rob Davies [mailto:[EMAIL PROTECTED] Sent: den 10 februari 2006 11:40 To: activemq-dev@geronimo.apache.org Subject: Re: Trouble uploading OpenWire C++ client to mailing list There's been some problems today with jira - but seems to be working ok now. Attaching the file to jira seems the best thing todo - how big is the patch ? cheers, Rob On 10 Feb 2006, at 08:44, Mats Forslöf wrote: > Great, adding it to Jira doesn't work either, got a proxy error, see > below. > > Proxy Error > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request POST /jira/secure/ > CreateIssueDetails.jspa. > > Reason: Error reading from remote server > > -- > -- > > Apache/2.0.52 (Fedora) Server at jira.activemq.org Port 80 > > Any ideas on how to upload the patch? > > Regards, > Mats > > -Original Message- > From: Mats Forslöf [mailto:[EMAIL PROTECTED] > Sent: den 10 februari 2006 09:18 > To: activemq-dev@geronimo.apache.org > Subject: Trouble uploading OpenWire C++ client to mailing list > > Hi, > > I've been tryint to send patches to this mailing list but it doesn't > seem to work. Should I put in a Jira isssue instead? > > Regards, > Mats
RE: Trouble uploading OpenWire C++ client to mailing list
Great, adding it to Jira doesn't work either, got a proxy error, see below. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /jira/secure/CreateIssueDetails.jspa. Reason: Error reading from remote server Apache/2.0.52 (Fedora) Server at jira.activemq.org Port 80 Any ideas on how to upload the patch? Regards, Mats -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: den 10 februari 2006 09:18 To: activemq-dev@geronimo.apache.org Subject: Trouble uploading OpenWire C++ client to mailing list Hi, I've been tryint to send patches to this mailing list but it doesn't seem to work. Should I put in a Jira isssue instead? Regards, Mats
C++ Client Update
Hi all, I'm about to send an update of the C++ OpenWire client but I need an answer on the question regarding 3rd party library asked previously by David Fahlander before I can do that. Also, who else is working on the C++ client besides David and me, we need to synch up our works. Is there any development at all on ActiveMQ?? The development list has been silent for a long time now and I wonder who the committers are? Regards, Mats
Contrib: C++ client prototype
Oops, here is the files. Regards, Mats prototype.tar.gz Description: prototype.tar.gz
Contrib: A first go with the C++ client
Hi all, I have started to port the C# client into C++, see attached files. The code compiles but is not yet fully functional, also it currently uses APR but restricted to the socket transport layer only. This prototype code may serve as the basis for the design discussion. What coding guidelines should we use? Should APR be used? Etc. Regards, Mats
RE: ActiveMQ C++
Hi Ning, I started to write a prototype for a C++ client using the STOMP protocol and have recently switched to OpenWire (after some communication issues was resolved by Hiram). Since the documentation currently is a bit scarce for OpenWire I have been trying to figure out how things work so there is not much useable code to contribute right now, sorry. Also, we need to decide on what design to use, I have looked at the C# client and it seems as a good start. Regards, Mats -Original Message- From: Ning Li [mailto:[EMAIL PROTECTED] Sent: den 11 januari 2006 23:08 To: Mats Forslöf Cc: activemq-dev@geronimo.apache.org Subject: RE: ActiveMQ C++ Hi, Mats: I am going to write a C++ AMQ client as well, is it possible that you can contribute your the code now? Thanks. Ning -Original Message- From: Mats Forslöf [mailto:[EMAIL PROTECTED] Sent: Monday, December 19, 2005 1:09 AM To: activemq-dev@geronimo.apache.org Subject: ActiveMQ C++ Hi, I saw Nathan Millers post in this list regarding a C++ API for ActiveMQ. I have been working on the same but have had problems with the OpenWire protocol. I have tried to make it run on both Linux and Win32 but with the same problem, it can't connect. I have asked (in the users mailing list) what may cause this problem but have not received any replies yet. I have since then written a complete C++ client using STOMP instead that I eventually would like to contribute. The client supports STOMP 1.0 and both synchronous and asynchronous delivery of messages. I have found two bugs in STOMP 1.0 and AMQ 3.2 (see Jira issue AMQ-444 and AMQ-445). Can anyone of the OpenWire authors please give some guidence so I can add support for it in the C++ client. Regards, Mats
ActiveMQ C++
Hi, I saw Nathan Millers post in this list regarding a C++ API for ActiveMQ. I have been working on the same but have had problems with the OpenWire protocol. I have tried to make it run on both Linux and Win32 but with the same problem, it can't connect. I have asked (in the users mailing list) what may cause this problem but have not received any replies yet. I have since then written a complete C++ client using STOMP instead that I eventually would like to contribute. The client supports STOMP 1.0 and both synchronous and asynchronous delivery of messages. I have found two bugs in STOMP 1.0 and AMQ 3.2 (see Jira issue AMQ-444 and AMQ-445). Can anyone of the OpenWire authors please give some guidence so I can add support for it in the C++ client. Regards, Mats
