Thanks! will take a look -----Original Message----- From: Justin Ross [mailto:[email protected]] Sent: Tuesday, May 22, 2018 6:06 PM To: [email protected] Subject: Re: Using qpid in a JEE container
Hi, Leor. Here's one example. It's based on WildFly Swarm, but you can map it back to JBoss XML pretty easily. https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ssorj_upstate_tree_master_worker-2Dswarm&d=DwIBaQ&c=50QIlj_rdvCHMJgBy2QFEw&r=333S4N92M45Zk07lpPp3kJfNhA9lZ8JW7IN3uXq13Vo&m=WPRByM_Iwcv3naYTAu0TV2Lp6m2_GcP5DTVVPdFoZlQ&s=PXFAqHe8jdu3DUi4NG5f-0i6B81gnyfqsG3EHpsjsqI&e= https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ssorj_upstate_blob_master_worker-2Dswarm_container_src_main_java_org_amqphub_upstate_swarm_SwarmWorker.java&d=DwIBaQ&c=50QIlj_rdvCHMJgBy2QFEw&r=333S4N92M45Zk07lpPp3kJfNhA9lZ8JW7IN3uXq13Vo&m=WPRByM_Iwcv3naYTAu0TV2Lp6m2_GcP5DTVVPdFoZlQ&s=cJJWrby9UR8cKhdsHuu5T4g7U-4_LZVuDiOPLQoz-g4&e= https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ssorj_upstate_blob_master_worker-2Dswarm_container_src_main_resources_project-2Ddefaults.yml&d=DwIBaQ&c=50QIlj_rdvCHMJgBy2QFEw&r=333S4N92M45Zk07lpPp3kJfNhA9lZ8JW7IN3uXq13Vo&m=WPRByM_Iwcv3naYTAu0TV2Lp6m2_GcP5DTVVPdFoZlQ&s=QAiR6gHcgW7OPygbc0NqQL4fXEnvMc6qivrwzTHipqA&e= The Swarm component is going to get renamed soon, so look here if the links aren't working: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ssorj_upstate&d=DwIBaQ&c=50QIlj_rdvCHMJgBy2QFEw&r=333S4N92M45Zk07lpPp3kJfNhA9lZ8JW7IN3uXq13Vo&m=WPRByM_Iwcv3naYTAu0TV2Lp6m2_GcP5DTVVPdFoZlQ&s=mSYhxuFLAfbzq54VCfD_QwqzmTzP4yEQLweTr1KU72M&e= On Tue, May 22, 2018 at 12:51 PM Leor Amikam <[email protected]> wrote: > We have an existing jboss JEE application (web services, ejbs, etc.). > We now need it to talk to another system that uses Azure Service Bus. > Is it possible to create an MDB that utilizes qpid as the JMS provider? > > Thanks > Leor > > Notice: This e-mail and any attachments are confidential and may > contain legally privileged information and/or copyright material of > Hansen Technologies Limited or third parties. Copying, distributing, > disclosing, commercialising or otherwise acting in reliance on this > e-mail and any attachments is strictly prohibited unless you are the > addressee of this e-mail and have written permission to do so. If you > have received this e-mail in error please delete this e-mail > (including any copies and > attachments) and contact Hansen Technologies Limited by return e-mail > or by telephone on + 61 3 9840 3000. Any views expressed in this > e-mail are those of the individual sender and may not necessarily > reflect the views of or be a commitment by the organisation, except > where the individual sender has the authority and expressly states them to be > so. > Notice: This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Hansen Technologies Limited or third parties. Copying, distributing, disclosing, commercialising or otherwise acting in reliance on this e-mail and any attachments is strictly prohibited unless you are the addressee of this e-mail and have written permission to do so. If you have received this e-mail in error please delete this e-mail (including any copies and attachments) and contact Hansen Technologies Limited by return e-mail or by telephone on + 61 3 9840 3000. Any views expressed in this e-mail are those of the individual sender and may not necessarily reflect the views of or be a commitment by the organisation, except where the individual sender has the authority and expressly states them to be so.
