In the past I would corral all of my queries as string constants in a query manager class -- an old Indian trick my grandfather taught me. Having a single location for database queries had a material impact in terms of improving maintainability.
I believe the objective of @NamedQuery is to precompile (with hints) and to keep EJBQL/SQL out of your methods. I am definitely not sure about that. I am also confused why they are entity bean meta data if they end up in a global namespace. Seems like a specialized Query class would be better. Can anybody give me a definitive statement on the purpose of NamedQuery annotations versus inline queries or a set of logically organized enums? TIA! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932681#3932681 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932681 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
