|
from i understood today:
I have to put the whole class name in eomodel like recipe.eo.Recipe
instead of just recipe. is that right?
Now i clean my old recipe/eo folder. sorry make confused i have one
Recipe table/class and use package name recipe as well.
built with superclass package=base,
then I got two folders/packages. one recipe.eo and
recipe.eo.base.
1) When you say you "from recipe.eo package could not access
recipe.eo.base package", I'm not sure what this means. EXACTLY what error
are you getting.
for
example in my Ingredient class:
public class
Ingredient extends _Ingredient{
}
error message:
"_Ingredient class cannot be resolved to a type"
because it's sit
in recipe.eo.base folder/package.
2) If your underscore file is generating a package name that is wrong, then
your templates are wrong. Either you are overriding the default templates
that are inside of WOLips with your own that are old and wrong, or you are not
up-to-date on your WOlips.
in the templates they are same as
#if
($entity.packageName)
package
$entity.packageName;
#end
WOlips version is 3.3.4750
thanks
kevin
"This communication is confidential and may contain
privileged and/or copyright material. If you are not the intended recipient you
must not use, disclose, copy or retain it. If you have received it in error
please immediately notify me by return email, delete the emails and destroy any
hard copies. ANZ National Bank Limited does not guarantee the integrity of this
communication, or that it is free from errors, viruses or
interference."
|