Well the CFPROPERTY tag should be able to hold any type. In CFMX if the type is not one of those in the normal list, I assume it believes the type is a CFC.

If we want to support BD and I don't really see why we shouldn't, we either have to alert them to the issue -- preferred method. Or re-engineer fourq et al to look at a new attribute like proptype or something (a fair bit of work required).

Does anyone on the list have any contacts at New Atlanta?

-- geoff
http://www.daemon.com.au/

Tim Lucas wrote:
Just trying to get Farcry running on BlueDragon build 6,1,0,232.

Skipping the installer I copied a current install, duplicated the DB, messed with app.cfm and came across the following problems:

- <cftrace>'s in:
  Aura, Core and FourQ

- try/catch in <cfscript> in:
  farcry_core/tags/farcry/_config.cfm

- uuid types in:
  Core and FourQ

- Had to hard code application.path values in _serverSpecificVars.cfm

- BD doesn't like types for CFC properties other than the standard ones.
  For example type="nstring"

I stopped here because its pretty fundamental to FC using custom db types in the type field.

Any suggestions?

-- tim lucas

http://www.toolmantim.com



--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to