On Sat, Jul 25, 2009 at 11:15 PM, Mike Kear<[email protected]> wrote: > I tried putting the CFCs into the XML file in alphabetical order, and > that didn't really work. It improved things a bit, but what worked > most was to put CFCs related to different parts of the application > together - all the USER cfcs together and all the CONTENT cfcs > together and all the CATALOG cfcs together etc. With comments between > the sections of the XML file, so they are easy to find.
Another useful trick is to use the <import> directive so you can break your ColdSpring XML file down into multiple files with each file containing CFCs for a specific part of the application, then you have: <import resource="user-beans.xml"/> <import resource="content-beans.xml"/> <import resource="catalog-beans.xml"/> Each imported file must be a syntactically complete ColdSpring XML file, i.e., must contain <beans> .. </beans> and some <bean> definitions. -- Sean A Corfield -- (904) 302-SEAN Railo Technologies US -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret At ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:324968 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
