project that uses EOGenerator is picking strange class names by default
-----------------------------------------------------------------------
Key: WOL-1118
URL: http://issues.objectstyle.org/jira/browse/WOL-1118
Project: WOProject/WOLips
Issue Type: Bug
Components: WOLips General
Affects Versions: WOLips 3.5.x
Environment: Mac OS X 10.5.8, WOLips 3.5.5984
Reporter: Ray Kiddy
I usually create 'Wonder Application' projects. I then create a new EOModel in the project. I check the "Use EOGenerator" checkbox. Lately, I seem to be getting very strange class names, by default, when I create a new entity.
Say that I create the entity "Foo". Even though I am using EOGenerator, I do not want to use a class for _every_ entity. I want to get EOGenericRecord as the class name for the Foo entity. I think that this used to be the behavior.
I usually have a package in my project like com.wykiwyk.appSpecific.data. I put entity classes in this package. I also use com.wykiwyk.appSpecific for the main package and com.wykiwyk.appSpecific.ui for components.
If I already have a few entity classes in the com.wykiwyk.appSpecific.data package, it might be a bit more reasonable for the default class name to be com.wykiwyk.appSpecific.data.Foo. This is not what happens.
It might even make a tiny bit of sense for the default class name to be com.wykiwyk.appSpecific.Foo, which does not happen either.
Instead I see com.Foo. What? When would that make sense? This is a silly value to have as the default.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
This archive was generated by hypermail 2.0.0 : Mon Oct 05 2009 - 11:02:00 EDT