Results 1 to 6 of 6

Thread: Problem while using JMS with Spring Integration

  1. #1
    Join Date
    Mar 2009
    Posts
    6

    Default Problem while using JMS with Spring Integration

    Hi,
    I am using JMS along with spring integration. But, I am getting this weird exception while deploying my application.

    Please help !!


    org.springframework.beans.factory.BeanDefinitionSt oreException: Unexpected exception parsing XML document from class path resource [umpcore-application-context.xml]; nested exception is org.springframework.beans.FatalBeanException: Class [org.springframework.integration.jms.config.JmsName spaceHandler] for namespace [http://www.springframework.org/schema/integration/jms] does not implement the [org.springframework.beans.factory.xml.NamespaceHan dler] interface

  2. #2
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,840

    Default

    Can you check your classpath to be sure you have a single version of any Spring jar?

  3. #3
    Join Date
    Mar 2009
    Posts
    6

    Default

    Mark , Thanks a lot for the reply !!

    I followed your advice and I found different versions of Sprig related jars in the classpath. Now I am having only one copy/version of jar files.

    I am getting a new error now.

    Its cvc-complex-type.2.4.c for jms:outbound-channel-adapter

    Please help

  4. #4
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,840

    Default

    I think you just need to add the org.springframework.integration.jms JAR to the classpath.

  5. #5
    Join Date
    Mar 2009
    Posts
    4

    Default

    I had this exact problem yesterday. I had all the Spring-Integration jars in the classpath, including the required 3rd party jars. I'm using spring-integration-1.0.1.RELEASE. It turns out i was copying the jars from lib directory, instead of copying from the dist directory

    I hope this help you

  6. #6
    Join Date
    Mar 2009
    Posts
    6

    Default

    Hey,
    Thanks for the Reply !!

    I was able to fix the problem. It indeed was the conflict between the jar files.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •