On 21 nov 2007, at 16:17, Freddie Tilley wrote:
When I generate my javaclasses files in Eclipse 3.3 using
JavaEOGenerator, all the attributes accessor methods always use data
types:
com.webobjects.foundation.NSData instead of just String, even though
I set the data type in Entity Modeler to String S
the JavaEOGenerator template contains attribute.valueTypeClassName
to set the class name
How can I fix this, because changing the types manually is obviously
not the long term answer
To answer my own question:
The reason why it doesn't work is when choosing a prototype for an
attribute in Entity Modeler (in eclipse) the following items
are not stored in the plist file of the entities attribute
valueClassName
valueType
I my case the prototypes stored in a separate eomodeld file with the
valueClassName and valueType of each item
however the JavaEOGenerator does not use this info to generate the
type and it defaults to NSData.
the eogen file generated by eclipse contains a reference to the
separate eomodeld file but it does not use the two missing
properties.
The workaround for this is copying two properties for each attribute
manually into the entity attributes in the plist and then it
works
Is there a workaround for this? Should I file a bug for Entity
Modeler? Or is the JavaEOGenerator responsible for this?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
