Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Error on creating new GWT/Roo Project

  1. #1
    Join Date
    Aug 2010
    Posts
    8

    Default Error on creating new GWT/Roo Project

    Currently I'm getting an xml validation error after creating a new roo project and executing the expenses.roo script.

    Here are 2 of the validation errors that I get
    Multiple annotations found at this line:
    - Cannot locate BeanDefinitionParser for element [resources]
    - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for
    element 'mvc:resources'.

    Any help would be much appreciated.

  2. #2
    Join Date
    Jul 2010
    Posts
    5

    Default

    I get the same thing running STS 2.3.3M2

    I simply deleted the offending lines as a work around to see if I could get a simple project working - no luck.

    Can anyone get Roo 1.1.0 M3 to work with STS 2.3.3M2?

    Do we need to install a new GWT plug-in?

  3. #3
    Join Date
    Jun 2008
    Location
    Philadelphia, PA, USA
    Posts
    212

    Default

    I am seeing this too. Some things happened when I updated my book sample files to 1.1.0.M3:

    1. Roo added the JSon .aj files
    2. Roo didn't add @RooJson to the entity (don't know if this is critical)
    3. Roo didn't add the flexjson library to my pom.xml file (I added it manually by copying from a new m3 project)
    4. Roo didn't upgrade the Spring version from 3.0.2.RELEASE, I updated manually to 3.0.4

    Now it compiles, but I get the same error you do:

    DispatcherServlet - Context initialization failed
    [INFO] org.springframework.beans.factory.xml.XmlBeanDefin itionStoreException: Line 14 in XML document from ServletContext resource [/WEB-INF/spring/webmvc-config.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:resources'.

    I'm thinking something happened with the upgrade. I'm going to create a brand-new project with my one entity and try to generate GWT again.

    Ken
    Ken Rimple
    Chariot Solutions
    email: krimple@chariotsolutions.com
    work: www.chariotsolutions.com/education
    personal: www.rimple.com

    Author: Spring Roo in Action (Manning)
    MEAP Site: manning.com/rimple

  4. #4
    Join Date
    Mar 2009
    Posts
    13

    Default

    I've tried a brand new project and I'm getting:

    Description Resource Path Location Type
    cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:default-servlet-handler'. webmvc-config.xml /VeeItinerary/src/main/webapp/WEB-INF/spring line 20 XML Problem

    Description Resource Path Location Type
    cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:resources'. webmvc-config.xml /VeeItinerary/src/main/webapp/WEB-INF/spring line 14 XML Problem

    ^^ error 4 times

    This is after some spring roo cleanup to make it compile that far

    Overall, I'm increasingly unimpressed.

  5. #5
    Join Date
    Jun 2008
    Location
    Philadelphia, PA, USA
    Posts
    212

    Default

    Roo team: is it possible nobody updated the public XML schema for the Spring MVC namespace to support the new resources tag? It seems like the one online does NOT have the newest features.

    Ken
    Last edited by krimple; Aug 27th, 2010 at 11:35 AM.
    Ken Rimple
    Chariot Solutions
    email: krimple@chariotsolutions.com
    work: www.chariotsolutions.com/education
    personal: www.rimple.com

    Author: Spring Roo in Action (Manning)
    MEAP Site: manning.com/rimple

  6. #6
    Join Date
    Feb 2007
    Posts
    1

    Default Same error in expenses.roo or gwtNoEntities.roo script

    Hi ,,,

    I am trying to build using roo-1.1.0.M3, with gwt-2.1.M3 in STS 2.2.3.M2.

    It is is causing from webmvc-config.xml in the following lines

    ....

    <mvc:resources location="classpath:/META-INF/dojo/" mapping="/resources/dojo/**"/>
    <mvc:resources location="classpath:/META-INF/dijit/" mapping="/resources/dijit/**"/>
    <mvc:resources location="classpath:/META-INF/spring/" mapping="/resources/spring/**"/>
    <mvc:resources location="/" mapping="/resources/**"/>

    <!-- Allows for mapping the DispatcherServlet to "/" by forwarding static resource requests to the container's default Servlet -->
    <mvc:default-servlet-handler/>
    ...

    Any help or alternative is greatly helpful.

    Thanks
    V

  7. #7
    Join Date
    Jun 2010
    Posts
    7

    Default has ANYONE gotten this to work?

    I'm getting a bunch of these same errors both with my own roo script and the examples. Has anyone gotten a GWT project successfully built and running with 1.1M3? If so, what's the trick! I was very patiently waiting for M3 to be released so I could dive into my own project, so it's pretty disappointing that nothing seems to work.

    Roo team...any suggestions? If there are new steps we must follow can you publish a new blog post similar to: http://blog.springsource.com/2010/06...h-roo-and-gwt/

  8. #8
    Join Date
    Jun 2010
    Posts
    440

    Default Expenses GWT up & running on 1.1.0M3

    Guys,

    It works for me...
    I enabled 1.1.0.M3, and execute two commands:
    1) roo script expenses.roo
    2) mvn gwt:run


    That's it.

    I suggest make sure environment vars are properly set. If carry stuff from old versions this is source of weird errors.

    Thx

    jD

    Note: I worked with the shell not sts

  9. #9
    Join Date
    Mar 2009
    Posts
    13

    Default

    I've done it from shell and from command line - both cases I've received the above errors.

    In any case, Roo needs to work with developer's solutions (our objects) not the solo expenses.roo application only.

  10. #10
    Join Date
    Aug 2010
    Posts
    8

    Default

    Quote Originally Posted by delgad9 View Post
    Guys,

    It works for me...
    I enabled 1.1.0.M3, and execute two commands:
    1) roo script expenses.roo
    2) mvn gwt:run


    That's it.

    I suggest make sure environment vars are properly set. If carry stuff from old versions this is source of weird errors.

    Thx

    jD

    Note: I worked with the shell not sts

    Yea, it works if you only execute the commands that way, the XML files still give me validation errors and I cannot run it via the google eclipse plugin (I'm not sure if I'm supposed to be able to however).

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
  •