Announcement Announcement Module
Collapse
No announcement yet.
Mobile dependency on Spring 3.1? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mobile dependency on Spring 3.1?

    Hello,

    I am just getting started with Spring Mobile.  Based on the instructions, I included the following Maven dependency:

    Code:
    <dependency>
        <groupId>org.springframework.mobile</groupId>
        <artifactId>spring-mobile-device</artifactId>
        <version>1.0.0.M3</version>
    </dependency>
    When I look at the POM for Spring Mobile, I see that this project is dependent on spring-webmvc, 3.0.5.RELEASE. When I try to add a DeviceWebArgumentResolver however, the IDE complains:

    Code:
    "Element 'annotation-driven' must have no character or element information item [children], because the type's content type is empty."
    Here, I am referencing the following schema:

    Code:
    http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd
    Does the "argument-resolvers" child element require a dependency on Spring 3.1?

    Thanks!

  • #2
    Answered my own question...

    I had to fudge quite a bit of my maven dependencies to get this to work. In short, there are features in Spring Mobile which are dependent on Spring MVC 3.1. I think the POM needs to be updated to reflect that. Currently, Spring MVC 3.0.5 is listed as the dependency.

    Also, the POM for Spring MVC 3.1.0.M2 is pretty much blank.

    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <modelVersion>4.0.0</modelVersion>
      <groupId>org.springframework</groupId>
      <artifactId>spring-webmvc</artifactId>
      <version>3.1.0.M2</version>
      <description>POM was created by Sonatype Nexus</description>
    </project>
    As a result, some of the other dependencies that are normally included are dropped. Can we get this fixed?

    Comment


    • #3
      Have these issues been fixed in a snapshot or other location already?

      Comment

      Working...
      X