This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

How to update fields/relationships/entities afterwardsPage Title Module

Comment

Indeed, the regeneration of some Web artifacts needs some better handling. At the moment you could simply delete the controller as well and then just issue the 'controller scaffold' command again for the entity you want to provide scaffolding for.

Cheers,
Stefan

Comment

Indeed, the regeneration of some Web artifacts needs some better handling. At the moment you could simply delete the controller as well and then just issue the 'controller scaffold' command again for the entity you want to provide scaffolding for.

Comment

Which version of Roo are you using? Please try out Roo RC4 and take a look at the upgrade section in the included documentation where we describe which artifacts to delete and which commands to issue. If you still have issues, I would be very interested in some more details so we can replicate your problem and fix it .

Cheers,
Stefan

Comment

My app (just a prototype for now) was created with RC4. I got started with RC3, carefully recorded my commands so i was able to just replay the script. I hadn't really done any programming yet myself so upgrading was really easy, i just discarded my old project

I went through the information in the upgrade section of the manual as you said and could not find anything that applies to my situation.

So I suppose you want to get more info from me? Basically my case was like this:

The domain class is called Customer, the two fields I added are called shippingAddress and billingAddress are simple strings, with notNull, sizeMin and sizeMax defined. I manually modified the class to implement Serializable.

If I read between the lines, I think there is a feature request in here --

Roo command history per project, that can be dumped and sent back for bug reports

In fact that (much requested) feature already exists . Sorry I have not made this clear. When issuing commands in Roo RC4 it will create a log.roo file in the root of your project and that contains all commands you have issued. So if you start the Roo shell and then type 'backup' a zip archive will be created which contains that script. So all you have to do is to send me the zip file.

However, I would also need to know what steps you have taken outside the roo shell (changed java files (Serializable, etc)) and in which exact sequence you have taken these steps (ie. first I ran the attached script, then I added two fields in the Entities Java source, which should have updated the view artifacts). Also, it would be good to know if the Roo shell indicated any problems (ie errors, rollbacks etc). You can also run Roo shell in 'development mode' which will actually give you stack traces, etc.

Comment

However, I would also need to know what steps you have taken outside the roo shell (changed java files (Serializable, etc)) and in which exact sequence you have taken these steps (ie. first I ran the attached script, then I added two fields in the Entities Java source, which should have updated the view artifacts). Also, it would be good to know if the Roo shell indicated any problems (ie errors, rollbacks etc). You can also run Roo shell in 'development mode' which will actually give you stack traces, etc.

Cheers,
Stefan

Hi,

This might take a while

I have been issueing quite a few commands in the roo shell from within STS, and like i said, they did not get appended to log.roo.

I also messed around with the project in other ways quite a bit (modified pom.xml, added webflow.version and spring security.version properties), so there can be many things causing this. I will try to get it replayable, but there's a few things i need to secure before that

Comment

STS 2.3.0 offers Roo command history recording. It is implemented by STS code as opposed to the normal Roo shell code. If it's not working with STS 2.3.0 would you please log a bug report and steps to reproduce at https://issuetracker.springsource.com/browse/STS. Thanks!