• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: VelocityEOGenerator and unflattened part of to-many relationship
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: VelocityEOGenerator and unflattened part of to-many relationship


  • Subject: Re: VelocityEOGenerator and unflattened part of to-many relationship
  • From: Xavier Destombes <email@hidden>
  • Date: Sun, 25 Nov 2007 09:23:51 -0600

Hello Mike,
I've just downloaded the latest WOLips nightly (3.3.4667), the latest VelocityTemplate, EOGenerate my model again, but I still got the same error.


The non-flattened relationship to the join table and the to-one relationships in the join table itself are not marked as class relationship in my model though. Only the flattened one.

I'm not using package, could it be the reason why I still got the error?

It's always interesting to know how people are doing, so I'm curious about how do you handle many-to-may without flattened relationships.

Xavier


I'm still trying to find out why my generated classes using VelocityEOGenerator aren't correct.
There's only one error left.
I'm using WO5.3 with latest WOLips and Mike's Velocity templates.


I have a Customer entity and a MailingCategory entity joined in a toMany relationship.

In the flattened relationship _MailingCategoryCustomer.java, everything is correct.

but there is one method in both _Customer.java and _MailingCategory.java which has an error:

the template generates the following method:
I've committed a fix for this ... I don't use flattened properties, but it seems a LITTLE bit weird that you have a flattened relationship through the to-many but this bug implies that you also have the non-flattened relationship to the join table as a class relationship (but not the to-one relationships in the join table itself). It seems like if you have the flattened relationship through the join table that you don't probably want the to-many relationship TO the join table to be a class properties. Regardless I fixed the templates to make this work properly (or rather, at least not generate invalid code) as well ...

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: VelocityEOGenerator and unflattened part of to-many relationship
      • From: Mike Schrag <email@hidden>
References: 
 >VelocityEOGenerator and unflattened part of to-many relationship (From: Xavier Destombes <email@hidden>)
 >Re: VelocityEOGenerator and unflattened part of to-many relationship (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Strange WOLips importing error
  • Next by Date: Re: Strange WOLips importing error
  • Previous by thread: Re: VelocityEOGenerator and unflattened part of to-many relationship
  • Next by thread: Re: VelocityEOGenerator and unflattened part of to-many relationship
  • Index(es):
    • Date
    • Thread