I am just starting to read about XDoclet with the idea of using it for Hibernate and Axis. However, I have a design concern that I did not see addressed in the FAQs, docs, articles, or mailing list archive.
In the system I am working with, persisted classes do not know anything about Hibernate - they delegate to another class that does. The web service class does not know it is a web service - that is all laid out in the Axis config. If you are adding attributes to your classes to specify behavior for generating other files, this seems to make classes that were POJOs into library-knowledgable classes. I understand that attributes have no affect on compiled code so the issue is semantic more than anything else. This appears to be the trade-off for the ability to generate dependent files. Over the long-term, however, I'm curious as to people's thoughts on refactoring approaches? What if you decide to stop using Hibernate? Are there easy tools to remove attributes (as there are starting to be for refactoring Java code)? Would you need to cobble together some scripts to strip out this info? Is this a concern at all or is that I haven't really delved into XDoclet yet? thx andy ------------------------------------------------------- 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
