Quantcast
Channel: Adobe Community : Popular Discussions - LiveCycle Data Services
Viewing all articles
Browse latest Browse all 58696

Flex Remoting - Deeply Nested ArrayCollections not Stongly Typed

$
0
0

I have a Flex 3 app which uses remoting. All works relatively well except for the following...

 

I have a deeply nested object graph as follows:

( btw: each VO uses [RemoteClass(alias="com.mypackage.xxx")] meta tags )

 

The main class is called "BrandVO" which contains an ArrayCollection on ProductLineVOs.

each "ProductLineVO" has an ArrayCollection of "ProductVO"s

each "ProductVO" has an ArrayCollection of "CaseVO"s, "UseVO"s, and  "IngredientVO"s.

 

Pseudo Graphically:

 

+-BrandVO

+----ProductLineVO

+-------ProductVO

--------------CaseVO

--------------UseVO

--------------IngredientVO

+-------ProductVO

--------------CaseVO

--------------UseVO

--------------IngredientVO

+----ProductLineVO

+-------ProductVO

--------------CaseVO

--------------UseVO

--------------IngredientVO

+-------ProductVO

--------------CaseVO

--------------UseVO

--------------IngredientVO

...etc...

 

When I make the remoting call (AMF3) , I properly recieve back an ArrayCollection of BrandVOs...

(Debugging shows each item in the ArrayCollection [0]...[n] has a Value com.mypackage.BrandVO(@1234etc)

 

Expanding each BrandVO shows properly typed nested ProductLineVO elements...

(Debugging shows each item in the ArrayCollection [0]...[n] has a Value com.mypackage.ProductLineVO(@1234etc)

 

Expanding each ProductLineVO shows properly typed nested ProductVO elements...

(Debugging shows each item in the ArrayCollection [0]...[n] has a Value com.mypackage.ProductVO (@1234etc)

 

The problem then is when expanding each ProductVO, the nested CaseVOs, UseVOs, and IngredientVOs ( although they contain the proper data) are typed generically.

(Debugging CaseVOs shows each item in each ArrayCollection [0]...[n] has a Value Object (@1234etc )

(Debugging UseVOsshows each item in each ArrayCollection [0]...[n] has a Value Object (@1234etc )

(Debugging IngredientVOs shows each item in each ArrayCollection [0]...[n] has a Value Object (@1234etc )

 

I don't know why all the other VO's get typed correctly but CaseVOs, UseVOs, and IngredientVOs fail to be stongly typed and default to generic Objects.

 

I have checked the returning remoting call data ( with ServiceCapture ) and the objects coming back do have the correct types. The problem seems to be at the Flex level.

 

Anyone know why this would happen?

Is there a limit to object grpah depth beyind which objects get typed generically?

I thought perhaps is was because the ProductVO has 3 ArrayCollections ( CaseVOs, UseVOs, and IngredientVOs ), so I tried removing all but CaseVO and had the same problem... CaseVO was typed as Object.

 

Any help/thoughts would be gratly appreciated.

~e


Viewing all articles
Browse latest Browse all 58696

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>