What I did was create an empty interface that only the classes I wanted to generate implemented. The xdoclet invocation that generated the DAO classes was restricted to classes that implement that interface.
You should be able to do something similar.
BTW, why are you providing external documentation for your classes instead of the interface? Good coding practice, as I understand it, would dictate that they use the interface exclusively in their code, with the exception of the constructor calls. And that should probably be hidden in an appropriate Factory class. Or are you documenting only the factories?
(If so the empty interface is obvious - Factory. Much of my generated code implemented a 'DAO' interface and it was much easier to write generic methods that used reflection allowing me to easily change my schema.)
pwomack wrote:
Can anyone point to the relevant parts of the xdoclet documentation, or (even better) point me to a example of doing something similar?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
