> Just to finish the discussion, I was indeed talking about "design patterns > used in the J2EE world". > (excuse my english if it was not clear) > Fair enough. FYI, the design pattern catalog commonly referred to as J2EE design patterns can be found here (http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html).
> There is some nice ideas and concepts overthere. > If it can nicely be applied to CF, I don't see where is the problem. > (don't worry, I am not trying to do EJBs with CFCs... ;) > Sure there are some nice ideas and concepts. However, not all of them are applicable. I have already seen people in my local user group trying to use some of these patterns with CFMX even though there have been many people advising them against it. The pattern should either directly fit or you shouldn't use it. Adapting patterns is quite a bad practice that should be avoided. > You may be don't believe in design patterns as they expressed today, > that's > fine, I respect that. > But some others do believe in design patterns (Fusebox or others) and do > like to share them with the CF community. > Are you saying the Fusebox people believe in design patterns or Fusebox itself it a set of design patterns? From what I have seen neither is true, but I am interested in which you mean and why. -Matt ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
