To be fair, if you're using CFML as a view-layer technology, none of that's needed or even wanted. Your view should basically be translating a predefined model into whatever end form is needed (HTML, usually). Custom tags are perfectly sufficient for that tasks, and if you ask me, the preferable mechanism.
It's only if you're using CFML for the whole application stack that those limitations will be hugely crippling. Though it wasn't until CF6 that we had them in ColdFusion itself, and there are a lot of applications out there that predate that release. This isn't to say that Smith is good or bad (or anything else), just that a feature-for-feature comparison is only valid if the target use cases are the same. If Smith is designed as an alternative view layer for J2EE applications (instead of JSP, Velocity, or whatever), having those features be omitted is actually a selling point. cheers, barneyb On 12/11/06, Andy Matthews <[EMAIL PROTECTED]> wrote: > I felt the same way. It's not even that it doesn't support CFCs. It doesn't > allow the CreateObject or cfinvoke methods. > > <!----------------//------ > andy matthews > web developer > certified advanced coldfusion programmer > ICGLink, Inc. > [EMAIL PROTECTED] > 615.370.1530 x737 > --------------//---------> > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:263569 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
