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