Hi Yanni,<br><br><div class="gmail_quote">On Fri, Nov 25, 2011 at 7:22 PM, Yanni Chiu <span dir="ltr">&lt;<a href="mailto:yanni@rogers.com">yanni@rogers.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 25/11/11 3:56 PM, Yanni Chiu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Any ideas why Fuel is looking for OldClass, yet there are no instances<br>
of OldClass in the de-serialized object graph.<br>
</blockquote>
<br></div>
There are no instances, but the class object itself is being held in various places in the Pier kernel.<br></blockquote><div><br></div><div>This can be the problem. Can you update these references to point NewClass?</div>
<div><br></div><div>I want to support in fuel 1.8 some way of specifying that a class has been renamed. Something like:</div><div><br></div><div>FLMaterializer newDefault</div><div>� � classRenames: { #OldClass -&gt; #NewClass }</div>
<div>� � materializeFrom: aFile.</div><div><br></div><div>Would this solve your problem?</div></div><br><div>cheers,</div><div>Mart�n</div>