Comments on: Exploring Roo's Architecture

By: Paul Bernet

Paul Bernet — Fri, 17 Jul 2009 09:05:10 +0000

@Andrew:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=283814

By: Keith Thomas

Keith Thomas — Fri, 17 Jul 2009 04:37:44 +0000

As far as I can tell SpringSource are entirely silent on the whole Grails vs Roo topic. Any thoughts why this should be?

By: Andrew Eisenberg

Andrew Eisenberg — Thu, 16 Jul 2009 16:02:42 +0000

Paul,

Can you please raise a bug for this on bugzilla? And include the full stack trace. I will look at it. Thanks.

http://bugs.eclipse.org

By: Paul Bernet

Paul Bernet — Thu, 16 Jul 2009 07:15:05 +0000

@Andrew

The Ex got lost along the way.

java.lang.IllegalArgumentException: Argument not valid
at org.eclipse.swt.SWT.error(SWT.java:3865)
…
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

The same ex periodically occurs in the eclipse error log with two different "Message headers":
1) Problems occurred when invoking code from plug-in: "org.eclipse.jface".
2) Unhandled event loop exception

For the remaining @Roo* Annotations: I assue that I can write a script which deletes all @Roo* Annotations and import statements.

Regards.
Paul

By: Yehuda

Yehuda — Wed, 15 Jul 2009 17:40:16 +0000

working on a hobby project enabling ROO with JSR-113. will share when i have something stable.

By: Andrew Eisenberg

Andrew Eisenberg — Wed, 15 Jul 2009 14:38:42 +0000

@Paul,

"However, when I selected the entry for the first time I got the error below in the eclipse log."

I didn't see an error log. Did I miss it?

The refactoring will leave the @Roo* annotations on the target type. Push in refactoring does not change the semantics of your program, only the structure.

By: Javed Mandary

Javed Mandary — Wed, 15 Jul 2009 09:42:31 +0000

Strangely the download link for spring-roo doesnt seem to be working:
http://www.springsource.com/products/spring-community-download

Are there any other direct links that can be used?

By: Paul Bernet

Paul Bernet — Tue, 14 Jul 2009 11:57:29 +0000

@Andrew:

When I changed into the "Aspect Visualisation" perspective I was able to select the menu entry
However, when I selected the entry for the first time I got the error below in the eclipse log.
After a Clean/Build of the project I was able to proceed with the procedure as in:
http://contraptionsforprogramming.blogspot.com/2009/05/push-in-refactoring-for-ajdt.html

The resulting classes look like this – I've taken Pet as a sample:

@org.springframework.beans.factory.annotation.Configurable
@Entity
@RooJavaBean
@RooToString
@RooEntity(finders = { "findPetsByNameAndWeight", "findPetsByOwner", "findPetsBySendRemindersAndWeightLessThan" })
public class Pet {

Is this the correct result of the procedure ? I'm wondering that there are still Roo Annoations.

Regards.
Paul

By: Andrew Eisenberg

Andrew Eisenberg — Mon, 13 Jul 2009 23:00:12 +0000

@Paul:

No, you shouldn't need to activate anything. But it does seem like something funky is going on. Do you notice any relevant error messages in the error log? There could be something preventing AJDT from loading. A quick test to see if AJDT is properly loaded is to look for AJDT gutter markers in the ROO ITD files.

Please raise a bug for this on Bugzilla and paste any relevant error logs or stack traces into your report:
http://bugs.eclipse.org

By: Paul Bernet

Paul Bernet — Mon, 13 Jul 2009 14:34:14 +0000

I tried the "push in refactoring" which is mentioned above
- but run into problems. Here is what I did:

1)
Executed clinic.roo sample in Roo M2.

2)
Generated Eclipse-Project and imported it to STS 2.1.0 RC1

3)
AJDT Plug-In is in Version: 2.0.1.e35x-20090704-2000

4)
When I right click the clinic project I do not see the Sub-Menu Entry Refactor | Push In…
as suggested in http://contraptionsforprogramming.blogspot.com/2009/05/push-in-refactoring-for-ajdt.html

Do I need to activate AJDT somehow ?

Regards.
Paul