OK, maybe I spoke too soon. Does the Advanced generation actually
work? I just looked at the output (I knew it would be Java, so I
didn't look before) and it wasn't what I was expecting. For example:
/tmp> more _Customer.mm
/** Class ${classGen.superPrefix}${classGen.className} was generated by Cayenne.
* It is probably a good idea to avoid changing this class manually,
* since it may be overwritten next time code is regenerated.
* If you need to make any customizations, please use subclass.
*/
public class ${classGen.superPrefix}${classGen.className} extends
$classGen.superClassName {
}
This isn't actually Java -- it didn't process the template. I tried
changing the output pattern back to *.java and got:
/tmp> more Customer.java
public class ${classGen.className} extends
${classGen.superPrefix}${classGen.className} {
}
Any thoughts?
Thanks,
/dev/mrg
PS. For Objective-C, it'll have to be done in two passes since a .h
and a .m is required.
On 10/11/06, Michael Gentry <[EMAIL PROTECTED]> wrote:
You know, I tried the Advanced option as a test, but got discouraged
because it generated an entire path for the package, but I just went
back in and noticed there is a "Use Package Path" checkbox. Turned
that off and it works perfectly. I'll make some templates now.
Thanks!
/dev/mrg
On 10/11/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
>
> On Oct 11, 2006, at 2:19 PM, Michael Gentry wrote:
>
> > I think the template will be the easy part. Proper integration with
> > Cayenne Modeler will be the hard part -- and Cayenne Modeler is
> > outside of the sandbox, so that could be a little touchy. Perhaps we
> > need a separate generator for testing/etc prior to merging with
> > Cayenne Modeler.
>
> While code is in the sandbox, you can use "Advanced" generation mode,
> and select the templates manually (selection will be remembered in
> the Modeler preferences). And once the code is moved to the trunk,
> we'll do a proper UI integration.
>
> Andrus
>
>
