Search:

Last week I pulled down STS 3.1.0, and used Roo to reverse engineer a PosgreSQL database. From the reverse engineer I got objects that contained 'Set's for the objects it was linked to (for example...

From memory, I think the bit of code that used this was in a managed bean that was a test file, so we just deleted the test stuff. Which probably doesn't help you that much sorry.

It's been a...

I think you need to define the database you want to connect you in the MySQL connection string.

I think there was an open enhancement request for it - if you want to vote on it :)

Did you follow the steps shown in the error message? i.e. do a setup then scaffold?

Have a look at the section on removing Roo in the docs - basically you can just fold in the stuff in the .aj files as needed I think.

Cheers,

Matt

The docs seem to say:

If you wish to add the field to a different target type you can specify the --class attribute as part of the field command which then allows you to tab complete to any type...

I think you need to define the --entity option to define what you are creating a repository for.

Cheers,

Matt

Maybe you could validate the properties file before you start up spring. You say the properties file is user input, so maybe do validation before using it?

Cheers,

Matt

Glad I could help - yes it is annoying, particularly since m2e suggests you should remove the versions. Yes would be good to log a bug - we'd never got round to it (I think).

Thanks,

Matt

My colleague here pulled the source, and got it to compile (took a little bit of work I think) when we hit this error.

The problem for us was that we are running a multimodule build with the...

I take it you've got the Eclipse Aspect J tools plugin installed?

We're using STS here, and we sometimes get it in the state where it looks the same - i.e. the classes show up as red, due to not...

Seems the perform tests command is just running the maven tests - so maybe just run those directly from the command line, and see what they give you?

I take it you can connect to your oracle db, and your using a jdbc connection string?

I think the issue is the manifest gets created with a whole lot of fluff that isn't actually needed for it to run. So you can trim it down, and remove unneeded dependencies - at least that's how I...

I found that the comments at the bottom showed you what to remove from the Manifest so that there was only one dependency that needed to be downloaded and installed - did you go through this too?
...

Hi,

Have you had a look at this:
http://nidget.wordpress.com/2011/07/21/how-to-osgify-an-oracle-jdbc-driver-with-spring-roo/

I followed this through (take note of the comments at the bottom...

We're using JSF. We'd used Primefaces on a previous project, so was quite nice to get all the bits set up for us by Roo. We're not really using the generated screens. But it does provide a nice...

Yes, just fixed them by hand. Can't remember which ones they were exactly, I think it was a version of Primefaces we couldn't find, and maybe an aspectJ version. But we just found the latest, or a...

We found that some of the versions of the dependencies couldn't be found - after fixing those the project came up ok.

Should be much the same as Eclipse with WTP. I.e. right click on the project, and then Debug As>Debug on Server

You may well need to set up your server at this point - depending on what you want,...

Hi,

I think you have more of a nexus/maven issue than roo.

So. From the settings you posted it looks like all your requests for jars via maven are being sent to your company nexus box, which...

I saw Primefaces had just put out 3.1, so upgraded to it.

Unfortunately the RooJsfManagedBean we have now has errors in the ManagedBean aj file - looks like the Primefaces guys removed the...

We're using Primefaces and JSF2 with spring, all scaffolded up with Roo. Works very nicely together.

I haven't used Spring MVC - but you probably wouldn't want to use that and JSF2 in the same...

Hi,

Yeah, I checked one of the other guys machines here - and it wasn't there. Maybe my initial install didn't quite pan out - I thought it didn't work because it said it was already there - but...