Connect active mq using openwire protocol












2














Does anybody has an example how to connect ActiveMQ OpenWire protocol using go please?
I used stomp & amqp with ActiveMQ for now and both are ok (testing), but our it architect will probably push for OpenWire as almost all our applications are Java based and that is standard for our company. So I would be happy for nay example, suggestions how to do it and not loose go service only because OpenWire protocol



thanks










share|improve this question




















  • 1




    I hope this would help you: godoc.org/qpid.apache.org/electron
    – Ehsan.Saradar
    Nov 19 '18 at 16:45
















2














Does anybody has an example how to connect ActiveMQ OpenWire protocol using go please?
I used stomp & amqp with ActiveMQ for now and both are ok (testing), but our it architect will probably push for OpenWire as almost all our applications are Java based and that is standard for our company. So I would be happy for nay example, suggestions how to do it and not loose go service only because OpenWire protocol



thanks










share|improve this question




















  • 1




    I hope this would help you: godoc.org/qpid.apache.org/electron
    – Ehsan.Saradar
    Nov 19 '18 at 16:45














2












2








2







Does anybody has an example how to connect ActiveMQ OpenWire protocol using go please?
I used stomp & amqp with ActiveMQ for now and both are ok (testing), but our it architect will probably push for OpenWire as almost all our applications are Java based and that is standard for our company. So I would be happy for nay example, suggestions how to do it and not loose go service only because OpenWire protocol



thanks










share|improve this question















Does anybody has an example how to connect ActiveMQ OpenWire protocol using go please?
I used stomp & amqp with ActiveMQ for now and both are ok (testing), but our it architect will probably push for OpenWire as almost all our applications are Java based and that is standard for our company. So I would be happy for nay example, suggestions how to do it and not loose go service only because OpenWire protocol



thanks







go activemq






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 7:55









Flimzy

37.5k96496




37.5k96496










asked Nov 19 '18 at 16:41









Vivlis

111




111








  • 1




    I hope this would help you: godoc.org/qpid.apache.org/electron
    – Ehsan.Saradar
    Nov 19 '18 at 16:45














  • 1




    I hope this would help you: godoc.org/qpid.apache.org/electron
    – Ehsan.Saradar
    Nov 19 '18 at 16:45








1




1




I hope this would help you: godoc.org/qpid.apache.org/electron
– Ehsan.Saradar
Nov 19 '18 at 16:45




I hope this would help you: godoc.org/qpid.apache.org/electron
– Ehsan.Saradar
Nov 19 '18 at 16:45












3 Answers
3






active

oldest

votes


















1














Take a look at the ActiveMQ OpenWire documentation. It has a link to a handful of Java classes which are used to generate C, C#, C++, & Java client code. You could probably use those as examples to create your own files to generate Go client code which can speak OpenWire.



That said, you're probably better served by using the Go AMQP or STOMP clients as ActiveMQ was designed to be used by multiple protocols.






share|improve this answer





























    0














    Thank you for answers. I agree with stomp & amqp as sufficient for task and agree that write OpenWire client just for sake of it is not good option. I have to convince our architects now






    share|improve this answer





























      -1














      AMQP and OpenWire clients can co-exist and is by far the best solution for you, even though you have a Java-stack.



      Your second best bet is to write some glue code in Java/C#/C++ that connects an OpenWire AMQ client with something that GO can speak to (like another ActiveMQ using AMQP or STOMP ;-) ).



      If you really really really need OpenWire support, the best bet is to try to use the C++ client and call it using swig or whatnot.



      Writing a native OpenWire-client in Go is a major effort and there is no point, except as a "fun" task.






      share|improve this answer





















        Your Answer






        StackExchange.ifUsing("editor", function () {
        StackExchange.using("externalEditor", function () {
        StackExchange.using("snippets", function () {
        StackExchange.snippets.init();
        });
        });
        }, "code-snippets");

        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "1"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: true,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: 10,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379120%2fconnect-active-mq-using-openwire-protocol%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        1














        Take a look at the ActiveMQ OpenWire documentation. It has a link to a handful of Java classes which are used to generate C, C#, C++, & Java client code. You could probably use those as examples to create your own files to generate Go client code which can speak OpenWire.



        That said, you're probably better served by using the Go AMQP or STOMP clients as ActiveMQ was designed to be used by multiple protocols.






        share|improve this answer


























          1














          Take a look at the ActiveMQ OpenWire documentation. It has a link to a handful of Java classes which are used to generate C, C#, C++, & Java client code. You could probably use those as examples to create your own files to generate Go client code which can speak OpenWire.



          That said, you're probably better served by using the Go AMQP or STOMP clients as ActiveMQ was designed to be used by multiple protocols.






          share|improve this answer
























            1












            1








            1






            Take a look at the ActiveMQ OpenWire documentation. It has a link to a handful of Java classes which are used to generate C, C#, C++, & Java client code. You could probably use those as examples to create your own files to generate Go client code which can speak OpenWire.



            That said, you're probably better served by using the Go AMQP or STOMP clients as ActiveMQ was designed to be used by multiple protocols.






            share|improve this answer












            Take a look at the ActiveMQ OpenWire documentation. It has a link to a handful of Java classes which are used to generate C, C#, C++, & Java client code. You could probably use those as examples to create your own files to generate Go client code which can speak OpenWire.



            That said, you're probably better served by using the Go AMQP or STOMP clients as ActiveMQ was designed to be used by multiple protocols.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 19 '18 at 17:13









            Justin Bertram

            3,0391316




            3,0391316

























                0














                Thank you for answers. I agree with stomp & amqp as sufficient for task and agree that write OpenWire client just for sake of it is not good option. I have to convince our architects now






                share|improve this answer


























                  0














                  Thank you for answers. I agree with stomp & amqp as sufficient for task and agree that write OpenWire client just for sake of it is not good option. I have to convince our architects now






                  share|improve this answer
























                    0












                    0








                    0






                    Thank you for answers. I agree with stomp & amqp as sufficient for task and agree that write OpenWire client just for sake of it is not good option. I have to convince our architects now






                    share|improve this answer












                    Thank you for answers. I agree with stomp & amqp as sufficient for task and agree that write OpenWire client just for sake of it is not good option. I have to convince our architects now







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 23 '18 at 12:04









                    Vivlis

                    111




                    111























                        -1














                        AMQP and OpenWire clients can co-exist and is by far the best solution for you, even though you have a Java-stack.



                        Your second best bet is to write some glue code in Java/C#/C++ that connects an OpenWire AMQ client with something that GO can speak to (like another ActiveMQ using AMQP or STOMP ;-) ).



                        If you really really really need OpenWire support, the best bet is to try to use the C++ client and call it using swig or whatnot.



                        Writing a native OpenWire-client in Go is a major effort and there is no point, except as a "fun" task.






                        share|improve this answer


























                          -1














                          AMQP and OpenWire clients can co-exist and is by far the best solution for you, even though you have a Java-stack.



                          Your second best bet is to write some glue code in Java/C#/C++ that connects an OpenWire AMQ client with something that GO can speak to (like another ActiveMQ using AMQP or STOMP ;-) ).



                          If you really really really need OpenWire support, the best bet is to try to use the C++ client and call it using swig or whatnot.



                          Writing a native OpenWire-client in Go is a major effort and there is no point, except as a "fun" task.






                          share|improve this answer
























                            -1












                            -1








                            -1






                            AMQP and OpenWire clients can co-exist and is by far the best solution for you, even though you have a Java-stack.



                            Your second best bet is to write some glue code in Java/C#/C++ that connects an OpenWire AMQ client with something that GO can speak to (like another ActiveMQ using AMQP or STOMP ;-) ).



                            If you really really really need OpenWire support, the best bet is to try to use the C++ client and call it using swig or whatnot.



                            Writing a native OpenWire-client in Go is a major effort and there is no point, except as a "fun" task.






                            share|improve this answer












                            AMQP and OpenWire clients can co-exist and is by far the best solution for you, even though you have a Java-stack.



                            Your second best bet is to write some glue code in Java/C#/C++ that connects an OpenWire AMQ client with something that GO can speak to (like another ActiveMQ using AMQP or STOMP ;-) ).



                            If you really really really need OpenWire support, the best bet is to try to use the C++ client and call it using swig or whatnot.



                            Writing a native OpenWire-client in Go is a major effort and there is no point, except as a "fun" task.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Nov 19 '18 at 20:12









                            Petter Nordlander

                            19.1k43674




                            19.1k43674






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Stack Overflow!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.





                                Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                Please pay close attention to the following guidance:


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379120%2fconnect-active-mq-using-openwire-protocol%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                'app-layout' is not a known element: how to share Component with different Modules

                                android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                                WPF add header to Image with URL pettitions [duplicate]