Installation guide

4 CFML Tags
4.1 ColdFusion Components
There are a few differences in CFC (ColdFusion Component) processing in BlueDragon,
including both enhancements and limitations, and with respect to their use as web
services. The following sections discuss these.
4.1.1 CFC Enhancements in BlueDragon
BlueDragon adds the following enhancements when working with CFCs:
• CFC instances can be duplicated using the Duplicate() function.
• CFC instances can be serialized (useful for J2EE servers where session replication
or persistence requires this).
• CFC instances can be correctly passed roundtrip using web services (from CFMX
to BD, but not the other way around).
• BlueDragon adds
CFCONSTRUCTOR for explicit definition of constructors (in addi-
tion to implicit construction). See Section 4.5.3 for more information.
4.1.2 CFC Limitations in BlueDragon
BlueDragon has the following limitations when working with CFCs:
• A component file (.cfc) must contain opening and closing CFCOMPONENT tags.
• It's not possible to define component functions inside
CFSCRIPT blocks.
Component functions can only be defined using the
CFFUNCTION tag.
• The file
component.cfc must exist, must not be empty, and must contain a
CFCOMPONENT tag pair (even if the tag pair is empty). In BlueDragon Server and
Server JX, it’s stored by default in their
[bluedragon]\config directory. In the
J2EE edition, it’s stored by default in the
WEB-INF\bluedragon directory.
• If you modify the source of a CFC that is inherited by another CFC, but don't
modify the inheriting CFC, the modified inherited class will not be reloaded when
the inheriting class is accessed. To reload the inherited class you must access it
directly, or manually flush the File Cache using the BlueDragon admin console
For additional limitations related to CFCs, see Section 4.3.10, discussing the
CFFUNCTION
tag, and Section 6.5, discussing declaration of CFC methods within a
CFINCLUDE tag.
BlueDragon 6.1 CFML Compatibility and Reference Guide 7