Re: EOGeneration generating Number attributes instead of Boolean
Re: EOGeneration generating Number attributes instead of Boolean
- Subject: Re: EOGeneration generating Number attributes instead of Boolean
- From: Josh Paul <email@hidden>
- Date: Wed, 12 Nov 2008 20:57:24 -0800
Are you using Wonder? Prototypes?
On Nov 12, 2008, at 8:42 PM, Ramsey Gurley wrote:
Hi George,
Have you tried generating with any other templates and gotten
similar results? If no...
http://wiki.objectstyle.org/confluence/display/WOL/EOGenerator+Templates+and+Additions
If you're having trouble with other templates, check your EOModel
and make sure the value type is 'c' on that attribute's prototype.
That 'c' tells WebObjects it's a boolean being represented by a
number. But only on numbers! Oddly, the 'c' means something else
for strings :) In fact, check your model first. That would be my
guess. I'm using Eclipse 3.4 and I don't remember if the interface
is identical in 3.3, but it should look something like:
<Picture 1.png>
or perhaps
<Picture 2.png>
Ramsey
On Nov 12, 2008, at 10:55 PM, George Wiles wrote:
Environment:
Windows Vista, Eclipse 3.3, Wolips plugin 3.3.5xx,
EOGenerator v1.7 (configured as a builder in eclipse), MySQL 5.0.51a
Issue
We are setting up a new development environment for a developer and
are experiencing an EO Generation issue. All our development
component versions come from a standard copy in our repository.
In our entity layer, Boolean entity attributes are mapped to java
Boolean objects and MySQL tinyint(1) by a prototype called ‘flag’.
On all development environment the EOGenerator maps this correctly,
except for the new environment. We have pain-stakenly confirmed
all the development components are identical (eogenerator,
templates, wolips-plugins, eclipse, mysql, mysql drivers, and jdk
versions) and the project properties (build paths etc), external
properties files (<user>wobuild.properties).
Example
What we see after a clean (and the eogenerator builder executes)
public Boolean isAutoGenerated() {
return (Boolean)storedValueForKey("isAutoGenerated");
}
public void setIsAutoGenerated(Boolean aValue) {
takeStoredValueForKey(aValue, "isAutoGenerated");
}
What new developer see after a clean (and the eogenerator builder
executes)
public Number isAutoGenerated() {
return (Number)storedValueForKey("isAutoGenerated");
}
public void setIsAutoGenerated(Number aValue) {
takeStoredValueForKey(aValue, "isAutoGenerated");
}
Question
Does anyone have a resolution for this (i.e. what causes it and how
to resolve it)?
Many Thanks
George Wiles | Software Development
TXT2GET | P +64 4 384 1438 | M +64 27 2758 143
Level 5, 75 Ghuznee Street, Wellington, New Zealand
email@hidden| www.txt2get.co.nz
_______________________________________________
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
_______________________________________________
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