[ 
https://issues.apache.org/jira/browse/FLEX-34138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933262#comment-13933262
 ] 

Gary Yang commented on FLEX-34138:
----------------------------------

would you please take a look at FLEX-34137 please? For this case I would expect 
dividing modules can let me use binding collections without introducing UI 
components.

Here's how I use Java Spring modules:
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-webmvc</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-context-support</artifactId>
        </dependency>


        <dependency>
            <groupId>org.springframework.flex</groupId>
            <artifactId>spring-flex-core</artifactId>
        </dependency>

        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-mapper-asl</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-oxm</artifactId>
        </dependency>
I think it's better.

Thanks.

> Divide Flex into several modules so that it can be used more widely
> -------------------------------------------------------------------
>
>                 Key: FLEX-34138
>                 URL: https://issues.apache.org/jira/browse/FLEX-34138
>             Project: Apache Flex
>          Issue Type: Wish
>            Reporter: Gary Yang
>
>  Just some thoughts, might be worth discussing more:
> Flex divided into multiple modules:
> Flex tools: 1) Mxml to AS;2)Meta process;3)Other code generation and 
> automation; 4) Maven integration;
> Flex Data: 1) Binding and List Synchronizing; 2) 0 UI component; 3) Pure 
> model reacting repeatable model; 
> Flex UI: 1) UI components and skinning; 2) States; 
> Serverside ---- bridge between server domain and presentation domain 1) DTO; 
> 2) Model synchronizing;



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to