Hmmm... Sounds like configure() is called *before* the object is fully  
populated/hydrated. Try getMemento() before getEmailAddress()... Perhaps  
the getMemento() will force the object to be populated.

That would explain the getXXX() functions returning empty strings, and the  
setXXX() functions being ignored/overwritten.

Ken

On Jan 7, 2009 1:10pm, Matt Quackenbush <[email protected]> wrote:
> To be extra, extra, extra clear, configure() *is* running. I can set  
anything to the decorator itself that I want to inside of configure(),  
provided that it does not come from the TO. For instance...
>
>
>
>
>
>
> setConfirmAddress("[email protected]");
>
>
>
>
>
> That works perfectly fine. (ConfirmAddress is added to the decorator, not  
a property on the TO.)
>
> But the following does not...
>
>
>
>
>
>
> setConfirmAddress(getEmailAddress());
>
>
>
>
>
>
> Well, it "works", in that an exception is not thrown, but it results in  
an empty string being set rather than the value from the property.
>
> In addition, if I attempt to set a property on the TO, that seems to be  
completely ignored (as shown in the first example from my original post).
>
>
> >
>
>
>

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