Results 1 to 3 of 3

Thread: Packaging WAR makes jpa setup fail with Roo 1.2.0.RELEASE

  1. #1
    Join Date
    Dec 2011
    Posts
    11

    Default Packaging WAR makes jpa setup fail with Roo 1.2.0.RELEASE

    Is there any reason that, with Spring Roo 1.2.0.RELEASE [rev 39eb957], if I specify packaging WAR, I can't add a jpa setup?

    Code:
    roo> project --topLevelPackage org.obliquid.jsf1 --java 6  --packaging WAR
    Created ROOT/pom.xml
    Created ROOT/src/main/resources
    Created ROOT/src/main/resources/log4j.properties
    roo> jpa setup --database H2_IN_MEMORY --provider HIBERNATE 
    File '/home/stefano/workspace/jsf/appo/src/main/resources/META-INF/spring/applicationContext.xml' does not exist
    The workaround is just don't set packaging WAR and then it works.

    Regards,
    Stivlo

  2. #2
    Join Date
    Aug 2010
    Location
    Goteborg, Sweden
    Posts
    434

    Default

    Have you checked the JIRA? This sort of problem could be fixed in the Roo nightlies.

  3. #3
    Join Date
    Dec 2005
    Posts
    930

    Default

    This is working as designed. You've specified that you want a WAR artifact, but you also want to put persistence code in your web project, which Roo does not allow. If you want to do a Roo 1.1.x style application, do not specify a packaging value. This option is used is intended to be used in multi-module Maven projects
    Alan Stewart
    Spring Roo Committer
    twitter @alankstewart

Tags for this Thread

Posting Permissions

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