Spring Roo 1.2.0.RELEASE available now

[bogdan10]

Is spring roo 1.2.0.RELEASE compatible with spring framework 3.1.RELEASE ? Is it safe to update to sf 3.1?
Well, I guess I had to upgrade from 3.0.5 to 3.1 since @RequestParam 'produces' attriibute has been added by roo 1.2 and did not update pom.xml. So far, so good.

[ellebana]

Hi..
I already downloaded spring roo 1.2.0RC1 and created new project. I notice that there is no "FINDER" view only Create and List..unlike in web mvc. Although the finder was stated in the created entity.
Is there any command that we need to add in creating finder?
Thanks.

[davesnyd]

I'm seeing the same problem and also struggling to resolve-- by which I mean, the answers I've turned up from Googling haven't worked yet.

I'm also seeing issues in the Java code with ReportLocator.java and in some of the aspect code for exceptions and constraint violations.

I'm working with 1.2.0 release under STS 2.8.1.

[tedp]

roo 1.2.0 can run in java 7 but with the following error:

InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInsta n
ce0(Native Method)

every time you type hint... the following error will appear:

InvocationTargetException at sun.reflect.GeneratedConstructorAccessor11.newInst a
nce(Unknown Source)

I have the same problem ('though using standard Oracle Java 6) and I've been wrestling with it now for a day or so, however I haven't come to any firm conclusion I'm afraid.

What I can say is that I can re-create the problem easily simply by first of all deleting my target folder and then running my JUnit tests. Deleting the target folder allows Roo to start (I get the problem whether I use STS or not) but once I run my unit tests and restart Roo, Roo gives the error NativeConstructorAccessorImpl.newInstance0.

So I have a work around but in case deleting the target folder doesn't work for others I've also noticed that during my upgrade from Roo 1.2.0.M1 I had to delete all the generated aspect J files for my domain objects only (forcing Roo to regenerate them from scratch) and if that doesn't work the other thing I did was to start again with a new pom.xml (I created a temporary project with the same top level package and set-up the same persistence and web settings) and manually copy all of your project specific dependencies etc.

Some combination of the above worked for me and I hope it works for others.

[MikeOliverAZ]

I must say I am very pleased with 1.2 the JSF/Primefaces looks great and is much easier to use than Apache Tiles and Dojo.

[fashoom]

I must say I am very pleased with 1.2 the JSF/Primefaces looks great and is much easier to use than Apache Tiles and Dojo.

Really? You like coding GUI's with the java faces API?

[dakine]

Aloha from the Philippines! want to learn more about Roo!

[samfndr]

Anyone has any luck with the OS command? I typed '!' and got the prompt back. I typed '!!' and I was suggested to install an addon. (spring-roo-os-commands (0.1.1.RELEASE))

Restart roo got 'Cannot specify an availability indicator for '!' more than once'.

Does OS command actually work in 1.2.0 release?

Thx.

[samfndr]

Does OS command actually work in 1.2.0 release?

Okay, I figured out. The command that I used to test is 'ls' on Mac OS X. This works with the Grails 2.0 prompt: '!ls'. Roo 1.2 needs this: '! ls'. I wish the documentation could tell me that... or make it more friendly like Grails.

Thx.

Sam

[loop0]

JSF/Primefaces isn't working correctly for @NotNull fields, it simply doesn't verify, I can add data without the "required" fields because they're not validated, I think it's a bug.