You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Kenneth Tam (JIRA)" <be...@incubator.apache.org> on 2005/02/26 00:56:49 UTC

[jira] Assigned: (BEEHIVE-366) Define best practices for Spring / Controls integration

     [ http://issues.apache.org/jira/browse/BEEHIVE-366?page=history ]

Kenneth Tam reassigned BEEHIVE-366:
-----------------------------------

    Assign To: Kenneth Tam

> Define best practices for Spring / Controls integration
> -------------------------------------------------------
>
>          Key: BEEHIVE-366
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-366
>      Project: Beehive
>         Type: Task
>   Components: Controls
>     Versions: V1Alpha
>     Reporter: Kenneth Tam
>     Assignee: Kenneth Tam
>      Fix For: V1

>
> Spring provides (among other things) a popular configuration and wireup mechanism for POJOs, in particular for JavaBeans.  Beehive Controls provide (also among other things) a simplifying model for authoring rich JavaBeans.  We need to define a set of best practices for using these two technologies together.
> Open issues:
> 1) how can Spring configuration files be used to control configuration and wireup of controls?
> 2) how do ids in Spring map to control ids?
> 3) how are arbitrary J2SE 5.0 annotations (particularly in the form of controls property sets) expressable in Spring?
> 4) how is nested control instantiation and configuration handled in the presence of Spring?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira