Re: EO generating and Interfaces
Re: EO generating and Interfaces
- Subject: Re: EO generating and Interfaces
- From: "John Huss" <email@hidden>
- Date: Wed, 21 May 2008 21:39:56 -0500
If this is the only case, I would just add a different method to the eo class for this entity:
public NSArray<RRSCalendarEvent> workshopEvents() {
return (NSArray<RRSCalendarEvent>)workshops();;
}
You can change the existing method first to make it compile, then do a Refactor->Rename to change all the references to the new function, then put the old method back.
John
On Wed, May 21, 2008 at 9:23 PM, David den Boer <
email@hidden> wrote:
Not sure if this has been covered before, but we are trying to migrate to the new Veogen tool from the old Rubicode tool, and are running into a few issues, mainly with generics and interfaces.
The new templates generate a method like this :
public NSArray<com.apple.foo.model.WorkshopMaster> workshops() {
return (NSArray<com.apple.foo.model.WorkshopMaster>)storedValueForKey("workshops");
}
where the old ones would leave the generic off. Now 99% of the time, this is perfect, but in this one case, WorkshopMaster also conforms to the RRSCalendarEvent interface, and that is what we want. Is there any way to have veogen change that or are we hosed and have lots of code to rewrite?
_______________________________________________
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