Heres an interesting problem. I have a CFX tag that is wrapped in a cfc 
function under redhat 7.2. When I invoke the cfc from a cfm page the CFX tag
executes as expected, but when I invoke the cfc from a flash movie (via 
the remoting interface) it throws the following error.

The CFX custom tag 'CFX_SSocket' was not found in the custom tag 
database. Please be sure to add custom tags to the database before using 
them. If you have added your tag to the database then you should check 
the spelling of the tag within your template to insure that it matches 
the database entry.

 Error processing CFX custom tag 'CFX_SSocket'.

I tried renaming and  re-registering the tag and it works from the cfm 
page but fails with the same error via flash,  the only odd thing I 
noticed is the error message
does not reflect changes I made to the case of the tag. The first time I 
complied the class I named it SSocket and registered it as CFX_SSocket, 
I tried re-registering
the tag as cfx_ssocket and keeping the class name the same. I ran 
through all the combinations of this naming scheme including recompiling 
the class with all lowercase
chars, all upper, mixed ...etc and it failed every time, however it 
worked every time from the cfm page even when the case of the class file 
did not match the case
in the cf admin. I also restarted the server between these cycles yet 
nothing worked. Is it possible that this is some kind of security 
feature of the flash remoting
interface or is this some kind of bug?

Anyone come across this type of thing before?

Thanks,

Jim Finucane

______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to