OK, this may be yet another hard-to-describe issue.

Our app is built using Fusebox 5.5.  In our onApplicationStart()
method, we initialize two relevant objects:
the transferFactory and then main transfer object (the
transferFacotry.getTransfer() ).  We also have a URL parameter we can
pass into a request to refresh the application (basically, it calls
onApplicationStart() again).

I have two different objects that our application can currently
create: applications and releases.  When I create either one and then
try to go to the page that displays the details of that record, I get
an error: The value returned from the getByID function is not of type
<myPath>.releaseDecorator.  If I refresh the application by using the
URL parameter, that page then works just fine.

In my getByID() function, I call this:
<cfset local.objRelease =
arguments.transferObject.get("releases.releases",arguments.releaseID)
/>

I decided to dump out local.objRelease  to see  what's being returned,
and it's interesting.  Before I refresh the application, the object
being returned is of type Transfer.com.TransferObject (which seems
wrong).

When I then refresh the application, the object being returned is
type: <myPath>.releaseDecorator (extends: <myPath>.BaseDecorator

So, I guess the question is why newly-saved object (release) reports
as a TransferObject instead of what it's supposed to,
releaseDecorator, until I refresh the application variables?



-- 
-----------------------------------------
Scott Brady
http://www.scottbrady.net/

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to