> Having said that, I guess even within generated code it's only ever going > to be comments/descriptions etc. that get translated (the closest it > currently gets to touching code is the EJB entity_dataholder_key string), > which shouldn't prevent compilation/deploying. So it's probably okay to > let it carry on; it wants to return a more explanatory string than "GRR", > though. > > What does anyone else think? Stop the build (i.e. throw exception) and so > force you to go fix the mistyped resource key in the template/code, or let > it carry on?
Let it carry on but display a warning. Imho it's not that much important, after all it shouldn't happen :-) So do what's easier. Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
