4 Replies Latest reply on Dec 13, 2004 5:32 PM by darranl

    Sample deployment info for JCA 1.5 inbound RA

    darth

      I still can't get JBoss to load my RAR, and I keep searching this site as well as googling the 'net but nowhere do I find info on a sample JBoss 4.0 JCA 1.5 inbound (only) Resource Adapter. I've followed numerous examples in building my own, and JBoss refuses to load (see Help!?!?!?!?! message posted last Friday). I've seen a reply by Adrian Brock that hints at a -ds.xml file, but _nowhere_ is an appropriate sample provided. The DTD reference does not exist in a JBoss 4.0 installation and the sample -ds.xml files in the installation are all for outbound RAs, not inbound, with no explanation of what the -ds.xml file's contents should be and what they mean.

      Lastly, no example inbound RAR for JBoss I've found on the net includes a -ds.xml file as part of its zip source file dowloads.

      I'm pulling out what little hair I have left - HELP, PLEASE!

        • 1. Switching JMX-Console from JRMP to HTTP invoker
          starksm64

          Hi,

          I read in the admin/dev guide that it's possible to switch to the HTTP/RMI invoker from the pre-configured JRMP invoker. But I'm not entirely sure how to do this.

          Right now the JRMP invoker references are in conf/jboss-service.xml and jmx-invoker-adaptor-server.sar/META-INF/jboss-service.xml

          I have the following http-invoker.sar configuration. Any suggestions on how to do this or where to start?



          <!-- The HTTP invoker service configration
          -->

          https://
          /invoker/JMXInvokerServlet
          false


          <!-- The HTTP HA invoker service configration for EJB invocations
          -->

          https://
          /invoker/EJBInvokerHAServlet
          false



          <!-- Expose the Naming service interface via HTTP -->

          <!-- The Naming service we are proxying -->
          jboss:service=Naming
          <!-- Compose the invoker URL from the cluster node address -->
          https://
          /invoker/JMXInvokerServlet
          false
          org.jnp.interfaces.Naming



          org.jboss.proxy.ClientMethodInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.naming.interceptors.ExceptionInterceptor
          org.jboss.invocation.InvokerInterceptor




          <!-- Expose the Naming service interface via clustered HTTP. This maps
          to the ReadOnlyJNDIFactory servlet URL
          -->

          jboss:service=Naming
          https://
          /invoker/readonly/JMXInvokerServlet
          false
          org.jnp.interfaces.Naming



          <!-- Config from: Sebastian -->
          <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
          to the JMXInvokerHAServlet servlet URL
          -->

          jboss:service=HAJNDI
          jboss:service=HAJNDI
          https://
          /invoker/JMXInvokerHAServlet
          false
          org.jnp.interfaces.Naming

          org.jboss.ha.framework.interfaces.FirstAvailable
          <!-- ### Change PartitionName attribute ### -->
          yankee


          org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
          org.jboss.proxy.SecurityInterceptor
          org.jboss.naming.interceptors.ExceptionInterceptor
          org.jboss.invocation.InvokerInterceptor




          <!-- Config from: Examples: chap8/ex3b/http-invoker-service.xml -->
          <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
          to the ReadOnlyJNDIFactoryHA servlet URL
          -->

          jboss:service=HAJNDI
          jboss:service=HAJNDI
          https://
          /invoker/readonly/JMXInvokerHAServlet
          false
          org.jnp.interfaces.Naming

          org.jboss.ha.framework.interfaces.FirstAvailable
          <!-- ### Change PartitionName attribute ### -->
          yankee


          org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
          org.jboss.proxy.SecurityInterceptor
          <!--
          org.jboss.naming.interceptors.ExceptionInterceptor
          -->
          org.jboss.invocation.InvokerInterceptor





          <!-- Config from: Examples: chap8/ex3b/http-invoker-service.xml -->
          <!-- Expose the HAJNDI service interface via clustered HTTP. This maps
          to the secured HAJNDIFactory servlet URL
          -->

          jboss:service=HAJNDI
          jboss:service=HAJNDI
          https://
          /invoker/restricted/JMXInvokerHAServlet
          false
          org.jnp.interfaces.Naming

          org.jboss.ha.framework.interfaces.FirstAvailable
          <!-- ### Change PartitionName attribute ### -->
          yankee


          org.jboss.invocation.http.interfaces.ClientMethodInterceptorHA
          org.jboss.proxy.SecurityInterceptor
          <!--
          org.jboss.naming.interceptors.ExceptionInterceptor
          -->
          org.jboss.invocation.InvokerInterceptor





          • 2. Re: Some experience
            darranl

            Hans,

            got Eclipse running on Solaris ok (once I sorted out my environment settings), and then ran the jbosside_installer fine. That worked ok.

            Then back into Eclipse, and try to configure JBossIDE. Problem was there was no place to select the server. All of the buttons, etc were missing. It's been awhile since I did Swing, and I know SWT isn't quite the same, but anyways, that seems to be the problem. Don't worry though, as the Lomboz plugin had the same problem, nothing to set the JBoss directory.

            So keep announcing updates on xdoclet/jboss-user so we know and I'll try them against the Solaris setup here.

            Bruce

            • 3. Re: Sample deployment info for JCA 1.5 inbound RA
              darth

              I don't understand how this reply answers my RAR inbound JCA 1.5 question/problem. Please elaborate.

              • 4. Re: Sample deployment info for JCA 1.5 inbound RA

                Just to shut you up. You are being ignored because although you
                *claim* to have made an effort to understand - you show very little result.

                You also need to understand that it is you who are asking for help.
                We already know how to do this. We are not going to waste time
                spoon feeding people who are lazy or incompetent.

                I recommend you post in the beginners forum where you might find more
                tolerance for you inane questions and assertions.

                If you look in the cunningly named "READ THIS FIRST"
                there is a link to the WIKI (reproduced here so you don't come back and say I
                cannot find it).
                http://jboss.org/wiki/Wiki.jsp?page=JBossJCA

                Here you will find an examples section which has something marked
                " * A simple example of message inflow"
                which contains what you are looking for:
                http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCAMessageInflowExample

                Strangely, google takes me directly to that page when I search for
                "jboss inbound example" and hit "I'm feeling lucky"? Hmm...

                Also on the JCA WIKI page you will find a configuration section
                which has the following link:
                "Inbound - Configuring a MessageListener for an inbound resource adapter (jca 1.5)"

                Here's another link I would recommend:
                http://www.jboss.org/wiki/Wiki.jsp?page=JBossForums