Tried the ten minute example and failed miserably

[Aaron Digulla]

Hi,

I'd just like you to know that I evaluated Roo and couldn't get it to work. You can find my comments in my blog: http://blog.pdark.de/2010/03/05/spring-roo/

I think the comments are pretty self-explanatory. If you have questions, then I'll try to answer them.

Best regards,

[Ben Alex]

I have replied in a comment on your blog. I'll paste the reply here as well, as it appears to be moderated:

Hi

Thanks for trying Roo and sharing your experiences. Sorry you didn't get up an app running in the 10 minutes. Hopefully the following will offer some reasons why...

Regarding issue tracking, if you look at the Roo home page (http://www.springsource.org/roo) it contains a link caled "Full Project Resources Index". If you click that, it contains a link to the "Jira issue tracker" at http://jira.springframework.org/browse/ROO. We are working on a new home page at present and will make this easier in the future. In the meantime we've got almost 700 bugs in there, so I guess plenty of people have found it. :-)

In relation to the javax/xml/bind/JAXBException, this is actually a bug in Hibernate Validator on Java 5. If you check the "known issues" section of the Roo reference guide we cover this. It's not Roo's fault at all. Here's the link to our docs which explain: http://static.springsource.org/sprin...e-known-issues

Concerning the repository setup, we use the SpringSource Enterprise Bundle Repository as Roo 1.0.x applications aim to provide an OSGi-compatible experience out of the box. The reasons for the different artefact names is detailed in the FAQ question at http://www.springsource.com/repository/app/faq#q13. You may be pleased to know we're evaluating switching to Maven Central repositories for Roo 1.1.0, as we agree this can cause confusion. The time spent setting up Nexus, though, to be fair, is not due to Roo but due to your company's firewall/repository policies/preferences.

You're always welcome to ask us questions at the Roo forum at http://forum.springsource.org/forumdisplay.php?f=67. We're very friendly and keen to help.

Cheers

Ben Alex
Project Lead, Spring Roo
SpringSource - a division of VMware

[Aaron Digulla]

Thanks for the quick reply :-)

1. Non-standard Maven setup: Thanks for the explanation. At home, I wouldn't have much trouble but at work, it's really a big hassle to evaluate Roo as it is. It's good to hear that you'll support Maven Central in the future.

2. NoClassDefFoundError: Just add stax:stax:1.2.0 to your pom. If you worry about JDK 6, put that dependency in a profile which gets activated for JDK 5 and less.

3. I've opened a new bug: http://jira.springframework.org/browse/ROO-679

[Ben Alex]

Thanks for the quick reply :-)

1. Non-standard Maven setup: Thanks for the explanation. At home, I wouldn't have much trouble but at work, it's really a big hassle to evaluate Roo as it is. It's good to hear that you'll support Maven Central in the future.

It's very likely we'll do it for 1.1.0. I agree it will make it easier for everybody.

2. NoClassDefFoundError: Just add stax:stax:1.2.0 to your pom. If you worry about JDK 6, put that dependency in a profile which gets activated for JDK 5 and less.

I've reopened http://jira.springframework.org/browse/ROO-224 to try this out and update the docs/POM defaults accordingly. Thanks for the info.

3. I've opened a new bug: http://jira.springframework.org/browse/ROO-679

Thanks for logging this. My colleague Alan Stewart already started working on this today and has emailed me a patch to look over. Expect a fix very shortly!

Cheers
Ben

[Alan Stewart]

Fix for ROO-679 in SVN rev 669

[MiB]

2. NoClassDefFoundError: Just add stax:stax:1.2.0 to your pom. If you worry about JDK 6, put that dependency in a profile which gets activated for JDK 5 and less.

3. I've opened a new bug: http://jira.springframework.org/browse/ROO-679

When I tried out the current Chapter 5 code of "Spring Roo in Action" with Roo 1.1.4, using Hibernate 3.6, this error returned. Adding Stax 1.2.0 alone did not work, but doing as Daeron Meyer did and adding jaxb-api 2.1 and jaxb-impl 2.1.3 did resolve the situation.

The code I add currently with Roo 1.2:

<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1.3</version>
</dependency>