The CFAdapter (beta) doesn't break Reactor anymore. I have it running (about 5 different versions of reactor/reaction) and CFAdapter installed in all my CFinstances.
Regards, João Fernandes Secção de Desenvolvimento Departamento de Informática -----Original Message----- From: [EMAIL PROTECTED] on behalf of Doug Hughes Sent: Wed 08-Feb-06 9:46 PM To: [email protected] Subject: RE: Reactor For CF Can't get revision 175 to work I see you're on *nix. FYI, Simeon Bateman spent several hours actually fixing all casing related issues in Reactor. However, there are a lot of you that probably (more or less through luck) had things working in Reactor already. These updates may have broken things. Try this: Create a totally new table. Create an object based on that. Does it work? If not, it might be that flex thing people mentioned. If so, then take all your generated code and copy it to a safe location. Then regenerate all your objects. After that copy your customizations back to your newly generated objects. That should work. (Ah the joys of alpha software.) Doug _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Blackwell Sent: Wednesday, February 08, 2006 3:12 PM To: [email protected] Subject: Reactor For CF Can't get revision 175 to work I've just checked out revision 175 and its not working for me at all. I'm getting the following error. The value returned from function init() is not of type reactor.data.abstractObjectDao. If the component name is specified as a return type, the reason for this error might be that a definition file for such component cannot be found or is not accessible. The error occurred in /var/www/html/reactor/core/objectFactory.cfc: line 102 Called from /var/www/html/reactor/core/objectFactory.cfc: line 29 Called from /var/www/html/reactor/reactorFactory.cfc: line 46 Called from /var/www/html/index2.cfm: line 2 Called from /var/www/html/Application.cfc: line 37 100 : <cfargument name="name" hint="I am the name of the object to translate." required="yes" type="string" /> 101 : <cfset var Object = CreateObject("Component", "reactor.core.object").init(arguments.name, getConfig()) /> 102 : <cfset var ObjectDao = CreateObject("Component", "reactor.data.#getConfig().getType()#.ObjectDao").init(getConfig().getDsn(), getConfig().getUsername(), getConfig().getPassword()) /> 103 : 104 : <cfset ObjectDao.read(Object) /> The createobject function on line 102 creates a "reactor.data.mysql.ObjectDao" but the init function from the abstractObjectDao says it returns a "reactor.data.abstractObjectDao". If I bodge this by setting its returntype to "Any", I'm seeing similar errors with other objects. abstractRecord throws an error when calling super.configure() which trys to return an abstractObject. I'm not sure if this is a problem that my flaky dev box is creating or if I've got a screwy version of the code from SVN.. ? Essentially here is the problem by way of two example cfcs base.cfc <cfcomponent> <cffunction name="test" access="public" returntype="base"> <cfreturn this> </cffunction> </cfcomponent> extend.cfc <cfcomponent extends="base"> </cfcomponent> test.cfm <cfset foo = createobject("component", "extend").test()> Cheers, Chris Blackwell Running CF7.0.1 & MySQL 5 on Linux
<<winmail.dat>>
