That shouldn't be the case -- I thought we were already picking the
correct templates based on the cgen version numbetr chosen.
Dirk, were you talking about using the standard templates or your own
custom versions?
On 2/3/07, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Hmm... actually this means that CayenneModeler should probably pick
> the correct "standard templates" for each generation mode. So it is a
> bug, although minor.
>
> Andrus
>
>
> On Feb 3, 2007, at 1:34 AM, Mike Kienenberger wrote:
>
> > On 2/2/07, Dirk Olmes <dir..anthippe.ping.de> wrote:
> >> I'm just playing around with cayenne a bit and stumbled over a
> >> strange
> >> behaviour of the modeler. When I generate classes and choose the 1.2
> >> class generator the generated java classes look like this:
> >>
> >> public class ${classGen.className} extends
> >> ${classGen.superPrefix}${classGen.className} {
> >> }
> >>
> >> When I choose the 1.1 class generator, everything looks normal.
> >
> > Ok... and? :-)
> >
> > classGen was obsoleted in the 1.2 version.
> >
> > From the 1.2 templates:
> >
> > ##Terminology:
> > ## Base class - super superclass of entity, ie,
> > org.objectstyle.cayenne.PersistentObject or MyBaseClass
> > ## Super class - superclass of entity, ie,
> > org.objectstyle.cayenne.art.auto._Artist
> > ## Sub class - class of entity, ie, org.objectstyle.cayenne.art.Artist
> > ##
> > ## Classes available in template
> > ## objEntity - the ObjEntity class: See
> > org.objectstyle.cayenne.map.ObjectEntity
> > ## stringUtils - class for string "helper" functions: See
> > org.objectstyle.cayenne.gen.StringUtils
> > ## entityUtils - class for entity "helper" functions: See
> > org.objectstyle.cayenne.gen.EntityUtils
> > ## importUtils - class for import statement management: See
> > org.objectstyle.cayenne.gen.ImportUtils
> > ##
> >
>
>
This archive was generated by hypermail 2.0.0 : Sat Feb 03 2007 - 18:30:39 EST