[transfer-dev] Re: function is not of type transfer.com.TransferObject
you have to add an *object* there, not an ID. Try: cfset session.generalCAR.setissueType(transfer.get(issueType, type, form.issueTypeId) / when you run a 'set' against a related object, you have to 'set' the object, not the object's primary key value =) Chris Peterson On Fri, Nov 21, 2008 at 7:30 AM, Gavin Baumanis [EMAIL PROTECTED]wrote: Hi There , I seem to be having ongoing issue with getting transfer to to the most simplest of tasks. If I dump the object I see all the methods that are automatically created for me via transfer - so far so good and I can see the methods for setting / getting the fields I have declared in my XML. Specifically I see a method setisuetype issue type is a manytoone with the following declaration in my XML; object name=issueType table=tbl_issueType id name=id_tbl_issueType type=numeric / property name=issueType type=string / /object object name=generalCAR table=tbl_CAR manytoone name=issueType link to=car.issueType column=issueTypeId / /manytoone ... /object Now if I have the following in my form's action page; cfset session.generalCAR.setissueType(form.issueTypeId) / then I get the following error; The TRANSFER argument passed to the setissueType function is not of type transfer.com.TransferObject. If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible. Huh? If I dump the session.generalCAR, then the method is there.. I tried by creating an issueType object with the following; session.issueType = application.transfer.new(car.issueType); And then I can successfully do this; cfset session.issueType.setissueType(form.issueTypeId) / But from my previous post(thread) that seems to have goteen a little butchered when Kevin's email client misbehaved I was given the advice that I didn't need to do this and that I should ust use the generalCAR.setissueType method, Have I missed something? mis-understood the replies - or am I just a completely mad nutter! -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
[transfer-dev] Re: function is not of type transfer.com.TransferObject
and sorry, I mis-typed in there: cfset session.generalCAR.setissueType(transfer.get(issueType, form.issueTypeId)) / something more like that =) On Fri, Nov 21, 2008 at 7:45 AM, Chris Peterson [EMAIL PROTECTED]wrote: you have to add an *object* there, not an ID. Try: cfset session.generalCAR.setissueType(transfer.get(issueType, type, form.issueTypeId) / when you run a 'set' against a related object, you have to 'set' the object, not the object's primary key value =) Chris Peterson On Fri, Nov 21, 2008 at 7:30 AM, Gavin Baumanis [EMAIL PROTECTED]wrote: Hi There , I seem to be having ongoing issue with getting transfer to to the most simplest of tasks. If I dump the object I see all the methods that are automatically created for me via transfer - so far so good and I can see the methods for setting / getting the fields I have declared in my XML. Specifically I see a method setisuetype issue type is a manytoone with the following declaration in my XML; object name=issueType table=tbl_issueType id name=id_tbl_issueType type=numeric / property name=issueType type=string / /object object name=generalCAR table=tbl_CAR manytoone name=issueType link to=car.issueType column=issueTypeId / /manytoone ... /object Now if I have the following in my form's action page; cfset session.generalCAR.setissueType(form.issueTypeId) / then I get the following error; The TRANSFER argument passed to the setissueType function is not of type transfer.com.TransferObject. If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible. Huh? If I dump the session.generalCAR, then the method is there.. I tried by creating an issueType object with the following; session.issueType = application.transfer.new(car.issueType); And then I can successfully do this; cfset session.issueType.setissueType(form.issueTypeId) / But from my previous post(thread) that seems to have goteen a little butchered when Kevin's email client misbehaved I was given the advice that I didn't need to do this and that I should ust use the generalCAR.setissueType method, Have I missed something? mis-understood the replies - or am I just a completely mad nutter! -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
[transfer-dev] Re: function is not of type transfer.com.TransferObject
Gavin, I often add a method to my decorator that accepts the ID for a manytoone relationship and then sets the proper object relationship using that ID. Something like cffunction name=setIssueTypeId access=public output=false returntype=void cfargument name=IssueTypeId type=numeric required=true cfset var issueType= getTransfer().get(IssueType,arguments.IssueTypeId) cfset getTransferObject().setIssueType(issueType) / /cffunction Some folks do not like this convention, but I do because it encapsulates the object composition process directly in the business object. Paul On Fri, Nov 21, 2008 at 5:02 AM, Chris Peterson [EMAIL PROTECTED]wrote: and sorry, I mis-typed in there: cfset session.generalCAR.setissueType(transfer.get(issueType, form.issueTypeId)) / something more like that =) On Fri, Nov 21, 2008 at 7:45 AM, Chris Peterson [EMAIL PROTECTED]wrote: you have to add an *object* there, not an ID. Try: cfset session.generalCAR.setissueType(transfer.get(issueType, type, form.issueTypeId) / when you run a 'set' against a related object, you have to 'set' the object, not the object's primary key value =) Chris Peterson On Fri, Nov 21, 2008 at 7:30 AM, Gavin Baumanis [EMAIL PROTECTED]wrote: Hi There , I seem to be having ongoing issue with getting transfer to to the most simplest of tasks. If I dump the object I see all the methods that are automatically created for me via transfer - so far so good and I can see the methods for setting / getting the fields I have declared in my XML. Specifically I see a method setisuetype issue type is a manytoone with the following declaration in my XML; object name=issueType table=tbl_issueType id name=id_tbl_issueType type=numeric / property name=issueType type=string / /object object name=generalCAR table=tbl_CAR manytoone name=issueType link to=car.issueType column=issueTypeId / /manytoone ... /object Now if I have the following in my form's action page; cfset session.generalCAR.setissueType(form.issueTypeId) / then I get the following error; The TRANSFER argument passed to the setissueType function is not of type transfer.com.TransferObject. If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible. Huh? If I dump the session.generalCAR, then the method is there.. I tried by creating an issueType object with the following; session.issueType = application.transfer.new(car.issueType); And then I can successfully do this; cfset session.issueType.setissueType(form.issueTypeId) / But from my previous post(thread) that seems to have goteen a little butchered when Kevin's email client misbehaved I was given the advice that I didn't need to do this and that I should ust use the generalCAR.setissueType method, Have I missed something? mis-understood the replies - or am I just a completely mad nutter! -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) -- Paul Marcotte Fancy Bread - in the heart or in the head? http://www.fancybread.com --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
[transfer-dev] Re: function is not of type transfer.com.TransferObject
Paul, I do the very same thing, I just didnt want to blow up anyone's mind so early in the morning =) Chris On Fri, Nov 21, 2008 at 12:52 PM, Paul Marcotte [EMAIL PROTECTED] wrote: Gavin, I often add a method to my decorator that accepts the ID for a manytoone relationship and then sets the proper object relationship using that ID. Something like cffunction name=setIssueTypeId access=public output=false returntype=void cfargument name=IssueTypeId type=numeric required=true cfset var issueType= getTransfer().get(IssueType,arguments.IssueTypeId) cfset getTransferObject().setIssueType(issueType) / /cffunction Some folks do not like this convention, but I do because it encapsulates the object composition process directly in the business object. Paul On Fri, Nov 21, 2008 at 5:02 AM, Chris Peterson [EMAIL PROTECTED]wrote: and sorry, I mis-typed in there: cfset session.generalCAR.setissueType(transfer.get(issueType, form.issueTypeId)) / something more like that =) On Fri, Nov 21, 2008 at 7:45 AM, Chris Peterson [EMAIL PROTECTED]wrote: you have to add an *object* there, not an ID. Try: cfset session.generalCAR.setissueType(transfer.get(issueType, type, form.issueTypeId) / when you run a 'set' against a related object, you have to 'set' the object, not the object's primary key value =) Chris Peterson On Fri, Nov 21, 2008 at 7:30 AM, Gavin Baumanis [EMAIL PROTECTED]wrote: Hi There , I seem to be having ongoing issue with getting transfer to to the most simplest of tasks. If I dump the object I see all the methods that are automatically created for me via transfer - so far so good and I can see the methods for setting / getting the fields I have declared in my XML. Specifically I see a method setisuetype issue type is a manytoone with the following declaration in my XML; object name=issueType table=tbl_issueType id name=id_tbl_issueType type=numeric / property name=issueType type=string / /object object name=generalCAR table=tbl_CAR manytoone name=issueType link to=car.issueType column=issueTypeId / /manytoone ... /object Now if I have the following in my form's action page; cfset session.generalCAR.setissueType(form.issueTypeId) / then I get the following error; The TRANSFER argument passed to the setissueType function is not of type transfer.com.TransferObject. If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible. Huh? If I dump the session.generalCAR, then the method is there.. I tried by creating an issueType object with the following; session.issueType = application.transfer.new(car.issueType); And then I can successfully do this; cfset session.issueType.setissueType(form.issueTypeId) / But from my previous post(thread) that seems to have goteen a little butchered when Kevin's email client misbehaved I was given the advice that I didn't need to do this and that I should ust use the generalCAR.setissueType method, Have I missed something? mis-understood the replies - or am I just a completely mad nutter! -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) -- Paul Marcotte Fancy Bread - in the heart or in the head? http://www.fancybread.com -- Hey! I dont tell you how to tell me what to do, so dont tell me how to do what you tell me to do! ~ Bender (Futurama) --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
[transfer-dev] Re: function is not of type transfer.com.TransferObject
Gavin, It looks like you really need to read: http://docs.transfer-orm.com/wiki/Managing_Relationships_and_Compositions.cfm And I would highly recommend looking at the tBlog example app: http://docs.transfer-orm.com/wiki/Example_Code.cfm#tBlog Which outlines all the different composition types, and how to utilise them. If you also read: http://docs.transfer-orm.com/wiki/Generated_Methods.cfm You will see that the arguments required for the methods generated do not match up to what you are passing in. Mark On Fri, Nov 21, 2008 at 11:30 PM, Gavin Baumanis [EMAIL PROTECTED] wrote: Hi There , I seem to be having ongoing issue with getting transfer to to the most simplest of tasks. If I dump the object I see all the methods that are automatically created for me via transfer - so far so good and I can see the methods for setting / getting the fields I have declared in my XML. Specifically I see a method setisuetype issue type is a manytoone with the following declaration in my XML; object name=issueType table=tbl_issueType id name=id_tbl_issueType type=numeric / property name=issueType type=string / /object object name=generalCAR table=tbl_CAR manytoone name=issueType link to=car.issueType column=issueTypeId / /manytoone ... /object Now if I have the following in my form's action page; cfset session.generalCAR.setissueType(form.issueTypeId) / then I get the following error; The TRANSFER argument passed to the setissueType function is not of type transfer.com.TransferObject. If the component name is specified as a type of this argument, its possible that a definition file for the component cannot be found or is not accessible. Huh? If I dump the session.generalCAR, then the method is there.. I tried by creating an issueType object with the following; session.issueType = application.transfer.new(car.issueType); And then I can successfully do this; cfset session.issueType.setissueType(form.issueTypeId) / But from my previous post(thread) that seems to have goteen a little butchered when Kevin's email client misbehaved I was given the advice that I didn't need to do this and that I should ust use the generalCAR.setissueType method, Have I missed something? mis-understood the replies - or am I just a completely mad nutter! -- E: [EMAIL PROTECTED] W: www.compoundtheory.com --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
[transfer-dev] Re: function is not of type transfer.com.TransferObject
On Nov 22, 10:20 am, Mark Mandel [EMAIL PROTECTED] wrote: Gavin, It looks like you really need to read:http://docs.transfer-orm.com/wiki/Managing_Relationships_and_Composit... And I would highly recommend looking at the tBlog example app:http://docs.transfer-orm.com/wiki/Example_Code.cfm#tBlog Which outlines all the different composition types, and how to utilise them. If you also read:http://docs.transfer-orm.com/wiki/Generated_Methods.cfm You will see that the arguments required for the methods generated do not match up to what you are passing in. Mark Just for the record I have read the docs at least two dozen times. I have read through the tBlog application almost as many. I'm certainly not stupid, by any means... it just simply isn't sinking in. Perhaps it is simply that I have no real-world OO experience. So trying to think (learn) objects and Transfer at the same time ... For an example of something that I don't get is; In the tBlog application there is the following code at the beginning of a lot of the templates (I.e listPost, listUser etc) transfer = application.transferFactory.getTransfer(); Is this necessary? Could I not just do this? application.transfer = application.transferFactory.getTransfer(); and store it once in the application scope? Is there any value in doing it in the instance scope as opposed to a persistent one? (I know application / session aren't (literally) persisted - but you know what I mean!) I can;t even remember where I got the code to put it nto the appliation scope. Perhaps it was from Bob Silverberg's tutorials... but I can't even find it in there at the moment... Then again - maybe there-in lies the problem - trying to take the examples of different people / architectures and trying to Though it did make sense to me at the time, that if I was going to the effort of doing things OO, then I should also be doing things with an appropriate framework / methodology from the get-go... as opposed to doing it simply and then having to refactor it later. I agree there is no reason to assume that Bob's way is the right way, or the only way... But the theory in his posts made sense to me (even if the code didn't). I am the kind of guy who likes rules / design standards. - it helps to keep me inline - not just my code. Anyway - looks like I'll go and read the examples apps again and the docs - again... tough to be honest ... I really feel like I am a flogging a dead horse at the moment. --~--~-~--~~~---~--~~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~--~~~~--~~--~--~---
