Thanks.
Marlon
S. Isaac Dealey wrote:
I don't use FB for my own development -- I use the attributes trick so that
I can call certain base templates as custom tags if it'll help, and I use an
equivalent of the fuseaction variable and the fbx_switch that's more dynamic
(actually just dynamic includes). Speaking of which -- apparently a few
people have run into problems with migrating FB2/3 applications to CF MX as
a result of the 64k method limitation of the underlying Java engine.
Apparently when MX generates a java class for a new template, it puts
everything in a single method, so if you've got a switch-case in the
template it'll examine all those includes and include the contents of all
those included files in the generated Java code. So even if your switch case
statement only has 2 cases like <cfswitch
expression="#fusebox.fuseaction#"><cfcase value="a"><cfinclude
template="a.cfm"></cfcase><cfcase value="b"><cfinclude
template="b"></cfcase></cfswitch> you could still exceed the 64k limit if
the CF Server generates more than 64k of combined Java code from a.cfm and
b.cfm (i.e. between them, not per file).
-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org
