9 Replies Latest reply on Jul 5, 2007 5:01 AM by Pawan Grover

    EJB3 MDBs & JCA Message inflow with foreing JMS provider

    Juha Moisio Newbie

      Hi,

      Some time ago I tried to configure JCA inflow using Sonic Software JCA Adapter for JBoss. All I got is, DefaultJMSProvider is not bound.

      I would like to hear, what is situation of JCA Message inflow in EJB3?


      Best regards,

      Juha Moisio

        • 1. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
          Weston M. Price Master

          This has been addressed. I seem to remember you using the Sonic JMS/JCA adapter. This has been succefully integrated by a customer using the latest Sonic stuff.

          Note, some of the annotations for the EJB3 stuff have changed, most notably the new @ResourceAdapter("rar-name") annotation.

          • 2. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
            Weston M. Price Master

            Note, I believe Sonic provides example deployments on their web site.

            • 3. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
              Juha Moisio Newbie


              Which version of JBoss EJB3 includes working JCA Message inflow?

              Br,

              Juha

              • 6. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
                Juha Moisio Newbie

                Yes. It really works. Now I can change all of my MDBs to EJB3.
                No more configuration to standardjboss.xml.

                Nice work. Thanks a lot :)

                Br,

                Juha Moisio

                • 7. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
                  Juha Moisio Newbie

                  Here is sonic jndi loader conf.


                  
                  <?xml version="1.0" encoding="UTF-8"?>
                  <server>
                   <mbean code="com.sonicsw.sonicmq.asi.jndiloader.jboss.JBossLoader" name="sonic.jndiloader:service=JNDILoader">
                   <attribute name="LoaderConfigURL">file:/C:/jboss-4.0.4.GA/server/default/data/sonic-jndiloader-conf.xml</attribute>
                   <depends>jboss:service=Naming</depends>
                   </mbean>
                  
                  </server>
                  
                  




                  
                  <?xml version="1.0"?>
                  <sonicloader>
                   <jndiEnvironment>
                   <property name="java.naming.provider.url">jnp://localhost:1099</property>
                   <property name="java.naming.factory.initial">org.jnp.interfaces.NamingContextFactory</property>
                   <property name="java.naming.factory.url.pkgs">org.jboss.naming:org.jnp.interfaces</property>
                   <property name="java.naming.referral">throw</property>
                   </jndiEnvironment>
                  
                   <entities>
                   <!-- SonicMQ Destinations -->
                   <!-- Make sure these destinations have been created on the SonicMQ broker -->
                   <!-- Queues -->
                   <entity jndiName="SonicJMS/Queues/SampleQ1" class="progress.message.jclient.Queue">
                   <property name="queueName">SampleQ1</property>
                   </entity>
                   <entity jndiName="SonicJMS/Queues/SampleQ2" class="progress.message.jclient.Queue">
                   <property name="queueName">SampleQ2</property>
                   </entity>
                   <entity jndiName="SonicJMS/Queues/SampleQ3" class="progress.message.jclient.Queue">
                   <property name="queueName">SampleQ3</property>
                   </entity>
                  
                  
                   <entity jndiName="SonicJMS/Queues/fromCustomer" class="progress.message.jclient.Queue">
                   <property name="queueName">SampleQ1</property>
                   </entity>
                  
                   <entity jndiName="SonicJMS/Queues/toCustomer" class="progress.message.jclient.Queue">
                   <property name="queueName">SampleQ2</property>
                   </entity>
                  
                   <entity jndiName="SonicJMS/Queues/toESB" class="progress.message.jclient.Queue">
                   <property name="queueName">toESB</property>
                   </entity>
                  
                   <entity jndiName="SonicJMS/Queues/fromESB" class="progress.message.jclient.Queue">
                   <property name="queueName">fromESB</property>
                   </entity>
                  
                   <entity jndiName="SonicJMS/Queues/errorsQueue" class="progress.message.jclient.Queue">
                   <property name="queueName">errors</property>
                   </entity>
                  
                   <entity jndiName="SonicJMS/Queues/trackingQueue" class="progress.message.jclient.Queue">
                   <property name="queueName">tracking</property>
                   </entity>
                  
                  
                  
                   <!-- Topics -->
                   <entity jndiName="SonicJMS/Topics/SampleT1" class="progress.message.jclient.Topic">
                   <property name="topicName">SampleT1</property>
                   </entity>
                   <entity jndiName="SonicJMS/Topics/SampleT2" class="progress.message.jclient.Topic">
                   <property name="topicName">SampleT2</property>
                   </entity>
                   <entity jndiName="SonicJMS/Topics/SampleT3" class="progress.message.jclient.Topic">
                   <property name="topicName">SampleT3</property>
                   </entity>
                   <entity jndiName="SonicJMS/Topics/SampleT4" class="progress.message.jclient.Topic">
                   <property name="topicName">SampleT4</property>
                   </entity>
                  
                   </entities>
                  </sonicloader>
                  
                  
                  


                  • 8. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
                    David Budworth Newbie

                    sorry to ressurect an old topic, but I've been beating my head against a wall to get this to work with Sonic 7.5 and jboss 4.2

                    Is there a means of setting the default rar file to use for inflow in ejb3?

                    I've been changing standardjboss.xml but nothing seems to take effect. do I *have* to set it as an annotation in every MDB directly? Or can I change the default settings?

                    worse comes to worse, I'll edit the jboss source to change the default value, but I'd really rather avoid that.

                    I use JBoss 4.2 in the default configuraion and have removed the deploy/jms directory all together. I need to have the server stripped down as much as possible so I can't run JBossMQ along side of it. Just trying to drop sonic in in place of the JBoss MQ and not add extra config to every mdb.

                    Any help would be appriciated

                    • 9. Re: EJB3 MDBs & JCA Message inflow with foreing JMS provider
                      Pawan Grover Newbie

                      Hi All,

                      I am using JBOSS 4.0.5 Application Server and I need to intigrate it with SonicMQ so that I can use SonicMQ as JMS provider instead of using default JBOSS MQ.

                      Please let me know what steps i need to do or provide any URL from where i can get the stuff