If you want to serialize your beloved DTOs, you can perfectly use Gas3 to
generate the as3 classes for your DTOs. Just apply the generator to the
correct set of classes.

What we *also* allow with GraniteDS is generating AS3 classes directly from
the JPA data model, and directly serialize/deserialize the JPA detached
objects to and from Flex.
Not everyone in the world wants to duplicate their model with DTOs, and
constantly copy/paste data from DTO to JPA objects. This duplication and
associated objects copying is often what make developers suffer much more
than having a coupling between the JPA model and the client model.


2014-04-04 15:49 GMT+02:00 Gary Yang <[email protected]>:

> I have modified those templates, it's working good for now, except the IMap
> thing, I didn't spend much time digging it, because it's just one line
> change after code generation for me.
>
> The other thing scare developers like me away at the first glance:
> I see from GAS part is that GraniteDS is trying to map Database entity to
> DTO directly, I have to say this is not good because this will keep client
> model structure locked up to DB, both developers will suffer eventually.
>
>
> -Gary
>
>
>
>
>
> On Fri, Apr 4, 2014 at 5:25 AM, Franck Wolff <[email protected]> wrote:
>
> > Gas3 (since version 2.3.2.GA) has LCDS templates and a
> LCDSAs3TypeFactory
> > which is generating AS3 Object fields for Java Maps (see this discussion
> in
> > the LCDS forum: http://forums.adobe.com/thread/1005496).
> >
> > Basically, the configuration (Ant task, I don't know much about FlexMojos
> > configuration options) is:
> >
> > <gas3
> >   as3typefactory="org.granite.generator.as3.LCDSAs3TypeFactory"
> >   entitytemplate="class:org/granite/generator/template/bean.gsp"
> >
> >
> entitybasetemplate="class:org/granite/generator/template/lcdsBeanBase.gsp"
> >
> interfacetemplate="class:org/granite/generator/template/interface.gsp"
> >     beantemplate="class:org/granite/generator/template/bean.gsp"
> >
> > beanbasetemplate="class:org/granite/generator/template/lcdsBeanBase.gsp"
> >     ...>
> >
> > However, it generates [Managed] beans, which can be unsuitable with
> > BlazeDS... If somebody can contribute BlazeDS templates / type factory, I
> > would be happy to add them in the next GraniteDS release (you can post
> them
> > on our JIRA here: https://jira.granitedataservices.com/browse/GDS).
> >
> > Franck
> > --
> > @graniteds
> >
> >
> >
> > 2014-04-04 0:20 GMT+02:00 Gary Yang <[email protected]>:
> >
> > > I think GAS will convert Java Map to Granite DS's IMap object, I have
> to
> > > change it back to object manually all the time.
> > >
> > >
> > > On Thu, Apr 3, 2014 at 6:16 PM, OmPrakash Muppirala <
> > [email protected]
> > > >wrote:
> > >
> > > > I dont specify a "generatorToUse" property.  What would it default
> to?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Thu, Apr 3, 2014 at 3:14 PM, OmPrakash Muppirala <
> > > [email protected]>
> > > > wrote:
> > > > >
> > > > > Chris,
> > > > >
> > > > > I do use the Gas3 generator in my projects, but I am not sure which
> > > > version I am using.  How can I find out?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > >
> > > > > On Thu, Apr 3, 2014 at 3:09 PM, Christofer Dutz <
> > > > [email protected]>
> > > > wrote:
> > > > >>
> > > > >> Hi,
> > > > >>
> > > > >> I'm currently finishing the task of supporting Jdk 1.7 and Maven
> 3.1
> > > and
> > > > 3.2 in Flexmojos.
> > > > >> A lot of trouble seem to be related to dependencies of the
> GraniteDS
> > > > Generator 1.x ... dropping this reduced the amount of trouble quite a
> > > lot.
> > > > >> I would therefore like to simply drop that generator.
> Unfortunately
> > I
> > > > don't quite know if this would break anything with you guys.
> > > > >>
> > > > >> What do you think?
> > > > >>
> > > > >> Chris
> > > > >
> > > > >
> > > >
> > >
> >
>



-- 
William Draï
Granite Data Services
24, rue de l'Est
75020 Paris
+33 (0)1 83 64 73 23
+33 (0)6 23 92 24 43
[email protected]

Reply via email to