Hi, Regarding my first question: I got a fresh CVS snapshot and the error doesn't occur anymore. Great! > 1. The generated @jboss tag for relations seems to be wring (this is > what it says in e.g. FlightBean.java) > > * @jboss.relation > * fk-constraint="true" > * fk-column="$relationshipRole.targetRole.columnMap.foreignKey" > >*related-pk-field="$target.getColumn($relationshipRole.targetRole.columnMap.primaryKey).variableName"
Second: Shame on me!! :-) It seems that I hadn't fully understood the many2many attribute of the cmp20 task. After I set it to "false" everything worked fine. So in case of an m..n relation and a table which already models such a relation AND many2many set to true the CMR stuff gets generated twice. Correct? > 2. This is more of a design question on the Flight-Person-Reservation > demo and n:m relations in general. Why would I include e.g. in the > FlightBean a method to get/set persons, when I modelled the n:m relation > between Flight-Person through the Reservation? > The set/get person/flights CMR methods in the FlightBean/PersonBean (+ > their CMR tags) result in a separate relation table which is not really > needed since we have the ReservationBean. > The way I understand it, is that I can either transform an n:m relation > into 2 n:1 relations using a separate table (like reservations) OR I can > use a "true" n:m CMR relation where the container generates the table > for me and handles the realation through get/set Persons/Flights? Sorry again for asking stupid questions :-) That's it! Leander ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf _______________________________________________ middlegen-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/middlegen-user
