> This is because the proxy generation depends on java reflection and java > reflection requires .class files. > But if you are using proxies in the hbm.xml file then the generated code > cannot compile because it is using the not-yet generated proxy interfaces > :) - its a chicken-egg problem :)
Yes, pretty yucky. > > What I would suggest is to have the codegenerators and proxygenerator use > the metadata package instead of parsing the xml manually! *Much* saner. The reason it is the way it is currently is that the individual bits of the toolset were done by different people at different times, with no real overarching vision. > 1. Code for parsing hbm.xml will only be written ONCE! :) > Secondly, I would suggest some kind of custom-attribute stuff like the one > provided in OJB. Then one could agument the definitions in hbm.xml with > custom attributes which could be used for codegeneration and other generic > purposes runtime (if it was available via the metadata package) Yeah, that would be cool. > Anyone already doing this ? :) Nope, I thought *you* owned the CodeGenerator now...... ;) ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
