On 2/22/17, 10:59 AM, "PKumar" <[email protected]> wrote:
>As suggested, I am planning to create one class for handling the >rgisterClassAlias related code. This class will hold array of VO class & >alias name that need to register for AMF de-serialization. I will call >registerClassAlias on same array before calling blazeDS call. That's fine for starters, but IMO, it would be a bonus if you could introspect the top-level class and find all the sub-types via Reflection. That would reduce pain on the developers forgetting to add one of their sub-types to the list. Thanks, -Alex
