4 Replies Latest reply on Jun 8, 2010 1:50 PM by dward

    SOAPProxy internal wsdl

    rafaelliu

      I have a EJB3 WebService packed in a .JAR and a SOAProxy service packed in a .ESB using the internal schema.

       

      And I'm getting this error:

       

      DEPLOYMENTS IN ERROR:
        Deployment "jboss.esb.vfsfile:<esb pack>" is in error due to the following reason(s): java.lang.RuntimeException: unrecognized internal endpoint: jboss.ws:<ws mbean>
      

       

      Seems like the .ESB is being deployed before the .JAR, so I tried to declare a deployment.xml like this:

       

      <jbossesb-deployment>
        <depends>jboss.ws:<ws mbean></depends>
      </jbossesb-deployment>
      

       

      But that leads to:

       

      DEPLOYMENTS MISSING DEPENDENCIES:
        Deployment "jboss.esb.vfsfile:<esb pack>" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.esb.vfsfile:<esb pack>>" (should be in state "PreInstall", but is actually in state "** UNRESOLVED Demands 'jboss.ws:<ws mbean>' **")
      
      DEPLOYMENTS IN ERROR:
        Deployment "<UNKNOWN jboss.esb.vfsfile:<esb pack>>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ws:<ws mbean>' **, ** UNRESOLVED Demands 'jboss.ws:<ws mbean>' **
       
      

       

      Environment:

      * JBoss ESB 4.8

      * JBoss AS 5

        • 1. Re: SOAPProxy internal wsdl
          dward

          Rafael,

           

          "jboss.ws:<ws mbean>" is an invalid internal URI for the SOAPProxy.  You need to replace "<ws mbean>" with the actual mbean name of the web service, which you can find out by navigating the JMX Console.

           

          You can find an example of a proper internal URI for the SOAPProxy in the Programmer's Guide, the SOAPProxy javadoc, and in any of the webservice proxy quickstarts, for example: webservice_proxy_basic.

           

          David

          • 2. Re: SOAPProxy internal wsdl
            dward

            Of course, now I'm thinking you probably replaced the actual name with "<ws mbean>" just for the purpose of this forum post - LOL...

             

            I'm probably not going to be much help unless I can have a test case, or at least your pertinent configuration files as-is.  (jboss-esb.xml, deployment.xml, etc.)

             

            David

            • 3. Re: SOAPProxy internal wsdl
              rafaelliu

              Precisely LOL. Anyway, I took a look at the example and figured it out.

               

              Just for the record I was missing this Barrier MBean. Just adapted the wsbarrier-service.xml file to from the webservice_proxy_basic example my own pourpose.

               

              Thanks David

              • 4. Re: SOAPProxy internal wsdl
                dward

                Precisely LOL. ..

                 

                Hahaha... it's been one of those days.    I'm glad you got it workin'.

                 

                Best regards,

                David