Its not that CFFORM can not be extended, its that people have not read the depths of the docs. CFFORM can be seen as being composed of 4 things. The first is the ability to create standard form tags dynamically. The second is to use pre-built javascript validation libraries. The third is to use pre-built Java form elements. The fourth is to define YOUR OWN java form elements. When thinking about extending CFFORM, people tend to forget that they can add their own Javascript validation scripts to extend tha abilities. They also forget (or usually don't know) that using the CFAPPLET tag will allow them to take a java applet that has a specific variable name or two and just 'plug it into' a CFFORM. In all my time using CF, I've only seen two custom Java CFFORM applets. The first is the calculator that I showed off in my CFFORM chapter in the WACK (vol 2&3). The other is a demo applet that ships with the CF docs. Unfortunatly (or fortunatly), this is all moot now as Harpoon will be taking over for most, if not all of the java applets in CF and will probably become the 'standard' for extending CFFORM. The only reason I write this is because someone mentioned that a negative with CF is that it dosn't allow CFFORM to be extended. p.s. on his other mention of CFOBJECT not supporting the asp model, this is not a part of the COM specification. Its something MS added in for their own use. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
