You can always create a typed ActionScript VO. Since you'll have to go from
ResultSet to typed object on the Java side before you can use the built-in
marshaller, you may as well just marshal straight from your resultSet to
AMF.
-Josh
2009/4/15 Daniel Freiman
>
>
> Yeah, it just felt inelegant
Yeah, it just felt inelegant to do manual, untyped serialization.
2009/4/13 Josh McDonald
>
>
> You could put them in a list of HashMaps, which should get serialised into
> an Array of simple name-value objects on the way to the Flex client?
>
> -Josh
>
> 2009/4/14 Daniel Freiman
>
>>
>>
>> Yea
You could put them in a list of HashMaps, which should get serialised into
an Array of simple name-value objects on the way to the Flex client?
-Josh
2009/4/14 Daniel Freiman
>
>
> Yeah, something more raw. If the ResultSet was natively serializable (w/
> multiple rows of data), I'd be happy.
Yeah, something more raw. If the ResultSet was natively serializable (w/
multiple rows of data), I'd be happy. I've found from previous iterations
of this project, that raw-ish data was the way to go here, and previous
languages I used easily allowed for that.
- Dan
2009/4/13 Tim Rowe
>
>
>
Have you already read into use of Transfer Objects and Data Access Objects, or
are you looking for a solution a little more raw than that?
Tim Rowe
Software Engineer
carsales.com Ltd
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
5 matches
Mail list logo
