It's some kind of real mystery there... I got it to work sometimes (!?!)... means it works, than I restart CF8 and I get the error again, than I restart the application it works again.., next time I restart CF ....you know...
Than I notice that Flex didn't call the serviceproxy when I mapped it in cf-admin.... even though I changed use-mappings in WEB-INF/flex/remoting- config.xml to true ==> <use-mappings>true</use> ...than I removed that the whole line and wrote it again, restarted CF and it took the mapping ... strange... I think it has definitely nothing to do with ColdSpring but - as Sean said - there seems to be occasionally some real weirdness the way Flex is calling CFCs. It's a bit unsatisfying because as long as I don't know what happens and can bring light in, I can't use it in production. Daniel --- www.danielschmid.name On 8/15/07, Sean Corfield <[EMAIL PROTECTED]> wrote: > > On 8/14/07, Daniel Schmid <[EMAIL PROTECTED]> wrote: > > <cfcomponent name="contactServiceRemote" > > > > displayname="contactServiceRemote:RemoteProxyBean" > > hint="Abstract Base Class for Aop Based Remote Proxy Beans" > > output="false"> > > > > <cfset variables.beanFactoryName = "factory" /> > > <cfset variables.beanFactoryScope = "" /> > > <cfset setup() /> > > I have occasionally encountered problems with CFCs called from Flex > not executing the pseudo-constructor and this may the same problem. I > don't know what causes it but it happened to me / my team at Adobe > (Hosted Services) and we had to change our remote proxies (which we > wrote by hand) to initialize on demand inside all the remotely called > methods. > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > >
