3 Replies Latest reply on Jul 2, 2014 12:57 PM by bsanders1979

    Spring/JSF/Hibernate/Tomcat

    bsanders1979

      Greetings,

      I am looking to setup Arquillian and I'm running into problems, so I just need to get a little direction. I followed the applicable instructions in the "Getting Started" section using Tomcat and had everything except the injection working. Next, I tried to follow the instructions for the Spring extension and then I was getting a "ClassNotFoundException" on MavenDependencyResolver in ShrinkWrap. After looking into the issue, it seems that there is some sort of version conflict and I'm unsure what the root cause is. Like I say, I'm not looking to be spoon-fed, but some "high level" instructions would be nice. At the very least, it would be nice to test the UI. Thanks!

       

      Brian Sanders

        • 1. Re: Spring/JSF/Hibernate/Tomcat
          aslak

          Try using the Spring extension 1.0.0.Final-SNAPSHOT from this repository; Index of /groups/public

          I'm suspecting you're running into Spring relying on a older v of ShrinkWrap Resolver then the one that comes with Arquillian currently.

           

          A new updated v. of Spring should be out tomorrow.

          • 2. Re: Spring/JSF/Hibernate/Tomcat
            bsanders1979

            Hey Aslak,

            Thanks for the speedy response. Based on your answer, I was able to figure out the issue. I was using Core 1.1.4.Final, but I noticed that 1.0.0.Beta2 was compiled against 1.0.4.Final. So, I switched to that version (just noticed the new beta release). The issue now is that when I try to run my test, it attempts to download the maven dependencies, but fails. What might I be missing here? I apologize if this is covered somewhere and I just haven't seen it, so anything you can tell me would be much appreciated. Thanks!

            • 3. Re: Spring/JSF/Hibernate/Tomcat
              bsanders1979

              Ok, so disregard my previous response about the dependencies. It seems to have been a "one time" thing where it was iterating thru repos and just couldn't find the dependency in one particular spot. However, I'm unclear as to why it wouldn't just find what has already been downloaded. Are the files being stored elsewhere?