RE: [CFCDev] component extends object with relative path

[Raymond Camden]

As far as I know, any ISP integration that allows for custom DSNs is using unofficial code. There is no 'out of box' ability that lets ISPs allow this (afaik). As it stands, Crystaltech lets customers add mappings via a custom admin piece.   As for having to rewrite all of your code, this is not always true. Both my blog and test tracker (admitidly simple apps) work fine with a dynamic mapping name. ======================================================================= Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc Member of Team Macromedia Email    : [EMAIL PROTECTED] Blog     : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Davis Sent: Wednesday, May 26, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] component extends object with relative path I hate to disagree with you Ray, but CFCs without admin access are crippled.  Seriously.   You can’t effectively package, extend or type-check CFCs without setting a mapping and using dot notation – especially in a hosted environment (where naming conflicts are going to send you over the edge quickly since CF favors the admin mappings in the discovery process).   Yes, you CAN use them… but you really can’t build a decent system with them unless you can set at least one mapping.   Also remember I’m a BIG CFC fan – I love the little buggers – but the CFC discovery process is tremendously slanted towards admin access.  They are simply not very useful in situations where you lack that.   Most CF hosts have come up with workarounds or custom tools for this (although it still sucks that Macromedia has yet to make any sort of recommendations to either the community or to hosting providers for how to handle things so we’re stuck with multiple, incompatible solutions).   This, by the way, is the difference with Data Source.  Any host that uses CF has a system in place for setting up datasources and they’re all pretty much the same.  You can also abstract data source names within an application to prevent code-rewrites in the face of name conflicts – none of that is available with CFCs.  If you assume a CFC path and that mapping is taken in a shared environment you simply have to rewrite all the code that uses it.  (As an aside this is a continuing problem with Java development in general and is not specific to CF.)   But as much as I love CFCs I still see this as a major issue – and the largest stumbling block for them to become more widely accepted.   Jim Davis     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raymond Camden Sent: Wednesday, May 26, 2004 7:17 AM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] component extends object with relative path   This is, without a doubt, one of the silliest things I've heard here. It is absolutely untrue that Admin access is required to use CFC. Mappings can greatly help your organization, but they are not required. Shoot, by your logic, CF is completely useless because you can't use a database w/o having access to the CF Admin (so as to add a datasource).