4 Replies Latest reply on Jun 16, 2008 1:28 AM by Jiri Pechanec

    Connection with SOAPUI to jbr-listener

    Stefan Lecho Newbie

      I've been doing some tests with a jbr-listener. When connecting with SOAPUI to the URL (http://localhost:9876) configured for the listener, I get a Connection Refused.

      I've been looking at the webservice-producer quickstart, and there the org.jboss.remoting.Client class is used. I hope :o) this is not the only way to connect to a jbr-listener. Could this be clarified ?

      Regards, Stefan Lecho.

        • 1. Re: Connection with SOAPUI to jbr-listener
          Tom Fennelly Master

          I'd need to see more your setup, but in short.... no, the jbr-listener is definitely not tied to JBR on the client side.

          So since you're using soapUI to access the endpoint, I assume you have a SOAPProcessor based action pipeline connected to that jbr-listener. If this is not the case, try using something else to fire a request to the endpoint.

          If the above is true (SOAPProcessor action pipeline)... then you should actually be pointing the soapUI at the contract/wsdl for that endpoint, and not the endpoint itself - soapUI will read the contract and know where to dispatch the SOAP requests to.

          To access the contract/wsdl details, bring up http://:/contracts in a browser. From there, you'll find the SOAP contract URL (wsdl address) for that http endpoint. This is the URL you need to use in soapUI for creating the "WSDL Project".

          • 2. Re: Connection with SOAPUI to jbr-listener
            Stefan Lecho Newbie

            Some additional information:

            At this point, I'm able to contact an external webservice by sending a message with a JMS client to the queue linked to a jms-listener and jms-provider. This works fine :o).

            But ... I do not want to force the usage of JMS for all the ESB clients that want to use this service. Therefor I was thinking to use an HTTP-based client that sends the SOAP Request to the jbr-listener and jbr-provider configured in my config file (see underneath).

            Since the jbr-provider is configured to use the 9876 port, I supposed that an HTTP connection to this port would have been sufficient to establish this connection. But unfortunately ... it is not :o(.

            In order to test this HTTP connection, I'm using SOAPUI. Once this is working, I will start to work on an HTTP client.

            PS: Why doesn't JBossESB supports a http-provider ?

            Providers

            <jms-provider name="JBossMQ" connection-factory="ConnectionFactory"
             jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
             jndi-URL="localhost">
             <jms-bus busid="fsbGwChannel">
             <jms-message-filter dest-type="QUEUE" dest-name="queue/fsb_gw_request"/>
             </jms-bus>
             <jms-bus busid="fphpESBChannel">
             <jms-message-filter dest-type="QUEUE" dest-name="queue/fphp_esb_request"/>
             </jms-bus>
            </jms-provider>
            <jbr-provider name="JBR-Http" protocol="http" host="localhost">
             <jbr-bus busid="Http-1" port="9876" />
            </jbr-provider>


            Services
            <service category="FSBServiceCategory"
             name="FSBWebService" description="FSB Webservice">


            Listeners
            <listeners>
             <jms-listener name="JMS-Gateway" busidref="fsbGwChannel" maxThreads="1" is-gateway="true"/>
             <jms-listener name="JMS-ESBListener" busidref="fphpESBChannel" maxThreads="1"/>
             <jbr-listener name="Http-Gateway" busidref="Http-1" is-gateway="false" maxThreads="1"/>
            </listeners>


            Actions
            <action name="PersonQuery" class="com.notary.esb.jboss.CredocSOAPClient">
             <property name="wsdl" value="...">
             <http-client-property name="file" value="/META-INF/https.properties" />
             </property>
            </action>


            • 3. Re: Connection with SOAPUI to jbr-listener
              Stefan Lecho Newbie

               

              Since the jbr-provider is configured to use the 9876 port, I supposed that an HTTP connection to this port would have been sufficient to establish this connection. But unfortunately ... it is not :o(.

              In order to test this HTTP connection, I'm using SOAPUI. Once this is working, I will start to work on an HTTP client.

              PS: Why doesn't JBossESB supports a http -provider ?


              Any clarification on this issue is highly appreciated :o)

              • 4. Re: Connection with SOAPUI to jbr-listener
                Jiri Pechanec Apprentice

                Hi,

                please switch JBR providerlistener to gateway

                <jbr-listener name="Http-Gateway" busidref="Http-1" is-gateway="true" maxThreads="1"/


                J.