beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kyle Marvin (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Resolved: (BEEHIVE-366) Define best practices for Spring / Controls integration
Date Thu, 05 May 2005 21:05:06 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-366?page=all ]
     
Kyle Marvin resolved BEEHIVE-366:
---------------------------------

    Resolution: Fixed

A sample webapp + prototype ControlFactory provider for wiring Spring into the Controls instantation
process has been checked in under samples/controls-spring as svn revision 168407.

> 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: Kyle Marvin
>      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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message