It looks like I deleted it off of the message but this relates to Transfer v1.1 Final, and I'm using ColdFusion MX7.
On Dec 9, 2:51 pm, Ryan Lynch <[email protected]> wrote: > I was going to file this in the issue tracker for Transfer, but it > doesn't appear that I can so here goes: > > Summary: > > Creating an object definition with an id (in this case with a name of > "id") of type binary results in the following error when a new > transfer object is created using the transfer.new() function: > > "The argument ID passed to function setid() is not of type binary." > > Here is the id definition for the object from the transfer.xml file: > > <id name="id" column="Id" type="binary" /> > > Possible cause and solution: > > Looking at the stack trace, the following line in the init() function > defined in the generated object defintion passes the incorrect > argument to the setid() function: > > setid(getNullable().getNullString(getClassName(), "id")); > > The correct code should be: > > setid(getNullable().getNullBinary(getClassName(), "id")); > > Changing this line manually fixes the problem. This is the only fix I > have at the moment as I can't override the init() function using a > decorator as that function is also defined in > transfer.com.TransferDecorator, and I'm not familiar enough with the > transfer source to find where the object definitions are generated and > fix the problem there. If someone could point me to where that occurs > in the source I'll gladly take the time to generate a patch. -- 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 [email protected] 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
