2 Replies Latest reply on May 8, 2009 2:46 AM by cnhome

    Why my ESB 3.4 not work?

    cnhome

      Now I am learning the book about ServiceMix3.3 published in China.I write the demo code and change the config file servicemix.xml as following:

       

       

       

      When I start ServiceMix, get the error info:

       

      Caught: org.springframework.beans.factory.BeanDefinitionStoreException: Unrecognized xbean namespace mapping: http://servicemix.apache.org/http/1.0

      org.springframework.beans.factory.BeanDefinitionStoreException: Unrecognized xbean namespace mapping: http://servicemix.apache.org/http/1.0

       

      How can I do with it?! Anyone help me. Thanks a lot.

       

      Edited by: cnhome on May 6, 2009 8:27 AM

        • 1. Re: Why my ESB 3.4 not work?
          davestanley

          It seems like the http-component may not be on your classpath.

           

          There is an example that ships with Fuse ESB below "examples/basic" that also uses the same activationSpec approach. I would try and build that demo and then tweak it to suit your needs. 

           

          Also, please note that the http/jsr181 approach has been superceded by the cxfbc/cxfse components. It would also be worth looking at the /examples/cxf-wsdl-first sample, as this would be the recommended way to implement wsdl first service endpoints.

           

          Hope this helps

          /Dave

          • 2. Re: Why my ESB 3.4 not work?
            cnhome

            Thanks!

             

             

            I find some useful documents in http://servicemix.apache.org/servicemix-http.html.

             

            Classpath issues when embedding servicemix-http component

             

            When using the servicemix.xml configuration file to create http endpoints, you must include the servicemix-http-xxx.jar in your classpath.

            You will find this file inside the component installer (./components/servicemix-http-xxx.zip).

            Failing this, an IllegalArgumentException will be thrown with the following message:

            Component name: xxxxxx is bound to an object which is not a JBI component, it is of type: javax.xml.namespace.QName

             

             

             

            I would try it.

             

            Edited by: cnhome on May 8, 2009 6:45 AM