Gotcha... so if we go that route, we'd have to set aside some time for the initial build. Using JSON doesn't win us anything since it'll introduce other work anyway.
Yes it seems like most everyone uses GAS3 for POJO generation now. -- Lou On Sun, 17 Apr 2016 09:08:32 -0700 OmPrakash Muppirala <bigosma...@gmail.com> wrote: > On Apr 16, 2016 10:53 PM, "Lou" <lh.fx...@gmail.com> wrote: > > > > Do you recall how long it took to build this? It sounds awesome. > > The initial setup took a while becuse of all the trial and error. Once we > got a prototype running end to end, it became easy after that. > > I forgot to mention that we are using GraniteDS GAS3 plugin to automatate > the generation of AS3 classes from the POJO classes. Everytime a new pojo > is made available, a maven plugin runs and creates the corresponding AS3 > class. > > Thanks, > Om > > > > > -- > > Lou > > > > On Sat, 16 Apr 2016 22:35:51 -0700 > > OmPrakash Muppirala <bigosma...@gmail.com> wrote: > > > > > On Apr 16, 2016 10:17 PM, "Paul Hastings" <paul.hasti...@gmail.com> > wrote: > > > > > > > > On 4/17/2016 9:46 AM, OmPrakash Muppirala wrote: > > > >> > > > >> I have couple of apps running REST services which serve AMF > responses. > > > >> Works exceedingly well! > > > > > > > > > > > > curious as to the logic for that. can you explain a bit more? > > > > > > > > > > The server side logic is in Java. The REST call results in a a few > POJOs > > > generated. Using the AMF serializer jars from BlazeDS, we convert the > > > POJOs into AMF objects and return them as the response. > > > > > > We have two clients, one in HTML/JS and one in Flex. The HTML/JS app > hits > > > the same endpoint, but requests a JSON response. The Flex app > requests > > > an AMF reaponse. > > > > > > We threw in an XML response to have a human readable response for > > > debuggging purposes. > > > > > > Hope that helps. > > > > > > Thanks, > > > Om
