Apr 18th, 2011, 06:20 AM
Roo 1.1.3 MEMBER OF AspectJ finder Hibernate
It looks like Roo 1.1.3 has a bug in the generated AspectJ finder for Hibernate.
I have just upgraded from 1.1.2 to 1.1.3 and have noticed that the referenced object in select statements have changed from <NameOfEntity> to just o.
The problem with this is that I think there have been an over sight for MEMBER OF <collection>.
So the statement that was previously 1.1.2:
SELECT entityName FROM EntityName AS entityName WHERE :member_item0 MEMBER OF entityName.member
SELECT o FROM EntityName AS o WHERE :member_item0 MEMBER OF entityName.member
entityName.member should be o.member and the staement should be:
SELECT o FROM EntityName AS o WHERE :member_item0 MEMBER OF o.member
Is this a known problem?
To fix just move the offending code from .aj file into entity file and make appropriate changes.
Apr 18th, 2011, 06:30 AM
The same code is generated for all ORM providers, with the exception for DataNucleus 1.x., which is a special case. If your units are failing or the Roo-created mvc app doesn't work, raise a bug request and attach a Roo script and/or the zipped up project (use the Roo backup command.
Apr 18th, 2011, 07:30 AM