> I am attempting to create getter setters
> "forAllFields". It would be nice to have a tag that
> created these given a property name. Now I'm just
> having trouble getting the first char to be upper case
> in the method signatures.
>
> <XDtField:forAllFields>
> private String <XDtField:fieldName/>Value;
>
> public void set<XDtField:fieldName/>Value(String s)
> {
> <XDtField:fieldName/>Value = s;
> }
>
> I suppose I'm the one to write a template tag to do
> this, so I'll try to get some time, but just a
> comment...
>
> I'm noticing the list of template tags could grow very
> large. At some point it might just make sense to have
> a few tags that allow you to XML'ize the target class,
> then point to an XSLT to generate the derived
> class(es). The number of template tags will grow and
> grow and learning them is worse that a regular
> language. Consider looping. We have forAllFields,
> forAllMethods, forAllClasses, etc. A looping syntax
> for every possible type of collection. EJBDoclet is
> cool, but the power of attribute programming is more
> in the ability of developers to quickly create new
> applications of XDoclet, meaning templates.
Yup, the template system has some limitations like this. Xdoclet will
use Velocity.
Ara.
-------------------------------------------------------
This sf.net email is sponsored by:
Battle your brains against the best in the Thawte Crypto
Challenge. Be the first to crack the code - register now:
http://www.gothawte.com/rd521.html
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
