Hi Vinny,

> I did not dive into the inner workings of the gateway, but 
> there is one new feature that will definitely interest you: the 
> lower keys tag in the gateway-config.xml file. Until CFMX7, ColdFusion 
> had a bad reputation of "messing" with the case of your keys. If you 
> build CFMX-Flex applications and you don't want CFMX7 to change the 
> case of your keys the value of this tag has to be "true". Now you can 
> use standard naming conventions without having to implement infamous 
> workarounds.

hmm - is this the same setting as in the Flex 1.5 gateway-config.xml (whichis 
set to false by default)? 

The way I understand this setting (for the Flex gateway) is that setting 
lowercase-keys to true forces all keys passed over the wire to lower case, i.e. 
a key

mixedCaseIdentifier

would be transferred as 

mixedcaseindentifier

which is OK for ActionScript 1.0 (as it's not case sensitive) and CF but not 
for Java or AS 2.0 - but setting this to true on the CF gateway would still 
force all keys to lower case which would probably break your AS 2.0 codeas it 
is case sensitive, or am I wrong?

Another thing; Is CF now really caring about case when calling a CFC via 
RemoteObject and the CFC returns an instance of a CFC? I used to return structs 
from CFCs and decorated them with the _remoteClass identifier - any newson this 
field?

> 1. If you create CFMX7 dynamically generated FlashPaper 
> reports and display
> them within a Flex panel, these FlashPaper reports won't 
> print. This is a serious bug MM is aware of and - I hope 
> - they will definitely fix in the next FlashPaper release.

yes, I hope so too. Currently, FlashPaper is great as a standalone 
documentformat but it does not play very well when loaded into another SWF app.

> 2. If you want to use CFLOGIN for authentication then there is another
> surprise: the Flex 1.5 setUsernamePassword API, currently 
> isn't connected to CFLOGIN. I hope they will fix this in Flex 2.0

that's bad news :(


Anyway, thanks for the information!

Cheers,
Dirk.


Reply via email to