<useTransitiveDependencies>true</useTransitiveDependencies>

shouldn't that be false?

Here's what I learned about Gas3:

It handles java primitives/primitive-wrappers just fine, but anything
beyond that, and you start to have problems.  Thus, if you have a DTO
with:

public String getValue();

public long getId();  etc...no problem-o.  But if you have this:

public MyDomainObject getMyDomainObject();

it will follow that link, and try to generate As3 for MyDomainObject,
and if that class has get/set for other stuff that maven pulls in, it
starts to follow that and eventually it blows up on something.

Regards,
Davis

On Tue, Apr 7, 2009 at 7:22 PM, aparrish <[email protected]> wrote:
>
> All:
>
> I think this is a similar problem as I have been following this thread
> for a few days.
>
> [INFO] [flexmojos:generate {execution: default}]
> [INFO] flexmojos 3.0.0 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
> file
> [FATAL ERROR] org.sonatype.flexmojos.generator.GeneratorMojo#execute()
> caused a linkage error (java.lang.IncompatibleClassChangeError) and
> may be out-of-date. Check the realms:
> [FATAL ERROR] Plugin realm = app0.child-container
> [org.sonatype.flexmojos:flexmojos-maven-plugin]
> urls[0] = file:/Users/adamparrish/.m2/repository/org/sonatype/
> flexmojos/flexmojos-maven-plugin/3.0.0/flexmojos-maven-
> plugin-3.0.0.jar
>
> I get the above error when trying to call the generate plugin on some
> very simple DTOs. Unfortunately it isn't obvious to me as to how to
> make the configuration ONLY generate my DTOs into AS instead of all
> the transient dependencies.
>
> Any thoughs? Here is my config for the plugin:
>
> <plugin>
>                                <groupId>org.sonatype.flexmojos</groupId>
>                                <artifactId>flexmojos-maven-plugin</artifactId>
>                                <extensions>true</extensions>
>                                <executions>
>                                        <execution>
>                                                <goals>
> <!--                                                    <goal>optimize</goal> 
> -->
>                                                        <goal>generate</goal>
>                                                </goals>
>                                                <configuration>
>                                                        <includeJavaClasses>
>                                                                
> <includeClass>snip...</includeClass>
>                                                        </includeJavaClasses>
>                                                        
> <useTransitiveDependencies>true</useTransitiveDependencies>
>                                                </configuration>
>                                        </execution>
>                                </executions>
>                        </plugin>
>
> On Apr 6, 11:08 pm, Davis Ford <[email protected]> wrote:
>> I think there may be a more apt reason to use DTO.  I was just reading
>> Sebastien's blog, and he points it out on this 
>> page:http://www.adobe.com/devnet/flex/articles/fullstack_pt2_03.html
>>
>> On Mon, Apr 6, 2009 at 10:30 AM, Vincent Vandenschrick
>>
>>
>>
>> <[email protected]> wrote:
>>
>> > Hi Davis,
>> > In that case, you have to go with a /thin/ domain model where your
>> > business objects are not more than value objects. This is actually a
>> > foremost design decision and in that case, you are right. But I
>> > /personally/ don't like these types of models since you are forced to
>> > break OO encapsulation sooner or later...
>>
>> > Regards,
>> > Vincent
>>
>> > PS: I also like design discussions
>>
>> > Davis Ford a écrit :
>> >> Hi Vincent -- I like design discussions :)
>>
>> >> In this case, I really don't think it warrants an extra layer.  That,
>> >> to me, seems like more maintenance.  If my entity objects are fairly
>> >> simple -- and they are, why do I need an extra layer of transformation
>> >> when Gas3 gets me *almost* all the way there.
>>
>> >> In any event, I've been exchanging with Franck on the graniteds list,
>> >> and he's just released a fix for the URL issue, and he is going to add
>> >> annotation support to allow control for generation.
>>
>> >> Currently, if you specify a field as transient:
>>
>> >> private transient Object someObject;
>>
>> >> Gas3 will ignore it in the generation.  However, this is no good, b/c
>> >> it conflicts with JPA.  If it is marked as transient in JPA it will
>> >> also ignore it for the database, which is not what I want.  If he adds
>> >> a custom annotation, I can control it via that, and all is well.
>>
>> >> Regards,
>> >> Davis
>>
>> > --
>> > Vincent Vandenschrick
>> >  Jspresso Framework
>> >  http://www.jspresso.org
>>
>> --
>> Zeno Consulting, Inc.
>> home:http://www.zenoconsulting.biz
>> blog:http://zenoconsulting.wikidot.com
>> p: 248.894.4922
>> f: 313.884.2977
> >
>



-- 
Zeno Consulting, Inc.
home: http://www.zenoconsulting.biz
blog: http://zenoconsulting.wikidot.com
p: 248.894.4922
f: 313.884.2977

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to