Hi Ulrich!
I'm afraid I determined that WOGen does not meet my needs for the
following reasons:
- Can't have entities that map no table
- Can't have 2 entities mapping the same table
- Generates EOs for all entities in a model. I want to exclude some.
E.g join tables.
- The above restriction also implies that I can't have different
entities from one model use different templates. E.g to have a
different inheritance root replacing EOGenericRecord
Within the time constraints of my current project I chose to integrate
calls to the classic EOGenerator in my build.xml files rather than
patching WOGen to fit my needs.
Pierre.
On Saturday, February 1, 2003, at 03:43 PM, Ulrich Köster wrote:
> Hi Pierre,
>
>
> Am Donnerstag, 30.01.03 um 17:05 Uhr schrieb Pierre Bernard:
>
>> Hi!
>>
>> Am I correct assuming that when I right-click on an EOModel file in
>> the WOLips perspective and select "Enable EO Generation" this should
>> generate a buildeos.xml file and thus enable EO generation using
>> WOGen? On my set-up (Eclipse M3, JDK 1.3.1, WOLips 0.9.7, WO 5.2)
>> this does not work. It does nothing apparent. No log message either.
> This is what I would expect :-) But unfortunately there was no time to
> finish this stuff.
>>
>> I thus went on to manually add a target to build.xml to generate EOs.
>> Unfortunately, WOGen fails on entities that have no table name set. I
>> frequently configure abstract entities this way. Moreover, WOGen
>> fails when 2 entities map the same table. This is also very common
>> when using inheritence.
>>
>> Are these known problems?
> I`ve never tested it. May be you have the time to fix it?
>
> Ulrich
>
>>
>> Best,
>> Pierre Bernard
>>
>> ---
>> Spinning WebObjects or cooking up Cocoa in Switzlerland?
>> Let me know: http://homepage.mac.com/I_love_my/
>>
>
This archive was generated by hypermail 2.0.0 : Sat Feb 01 2003 - 13:16:04 EST