Using Sculptor 1.8, I¹ve noticed that the model validator will emit warnings
when an entity¹s attribute is capitalized (³[WARNING]: Attribute/reference
should begin with a lower case letter²).
However, if I ignore that warning, the code still generates (but won¹t
compile).
Given this example:
Application MyApp {
basePackage=org.foo
Module abc{
Entity Foo {
package=domain.impl
String ABCValue key
}
}
}
The compilation failure is
³src/generated/java/org/foo/abc/domain/impl/FooProperties.java:[7,21]
package sharedInstance does not exist²
If you look at the generated class, you¹ll see the mangled import at the
bottom (one for each capitalized attribute):
package org.foo.abc.domain.impl;
import org.fornax.cartridges.sculptor.framework.domain.LeafProperty;
import org.fornax.cartridges.sculptor.framework.domain.PropertiesCollection;
import org.fornax.cartridges.sculptor.framework.domain.Property;
import sharedInstance.ABCValue;
I don¹t have a point of view on whether or not capitalized field names are
appropriate or not (they worked ok in sculptor 1.6 and earlier), but if they
aren¹t supported then the model validation should report them as an error
(since the error you get later doesn¹t make it clear what the problem is).
Have a good weekend!
------------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
