Differences between revisions 3 and 4
Revision 3 as of 2005-01-06 23:22:26
Size: 2490
Editor: MikeFoster
Comment:
Revision 4 as of 2009-09-20 23:24:32
Size: 2502
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
To support the second use case in the open source community, a sister site has been developed at [http://www.controlhaus.com ControlHaus]. It is proposed here that the creation of some starter -- or "system" controls be created and developed there, and pulled in to the Beehive distribution. To support the second use case in the open source community, a sister site has been developed at [[http://www.controlhaus.com|ControlHaus]]. It is proposed here that the creation of some starter -- or "system" controls be created and developed there, and pulled in to the Beehive distribution.
Line 13: Line 13:
 * "Seed" the [http://www.controlhaus.com ControlHaus] community so that other control projects will begin development there.  * "Seed" the [[http://www.controlhaus.com|ControlHaus]] community so that other control projects will begin development there.
Line 15: Line 15:
BEA Systems has several generally useful controls that were developed for the 8.1 Workshop product. They would like to donate and continue development of these controls in [http://www.controlhaus.com ControlHaus]. The implementations will be container independent implementations. The list of these controls is: BEA Systems has several generally useful controls that were developed for the 8.1 Workshop product. They would like to donate and continue development of these controls in [[http://www.controlhaus.com|ControlHaus]]. The implementations will be container independent implementations. The list of these controls is:
Line 24: Line 24:
By placing the development of system controls in [http://www.controlhaus.com ControlHaus] we can grow the control authoring community, and "seed" [http://www.controlhaus.com ControlHaus] with something real and useful. We may want to pull development on the system controls into Beehive at a later date. By placing the development of system controls in [[http://www.controlhaus.com|ControlHaus]] we can grow the control authoring community, and "seed" [[http://www.controlhaus.com|ControlHaus]] with something real and useful. We may want to pull development on the system controls into Beehive at a later date.
Line 26: Line 26:
The other goal mentioned above is to add some common useful controls to the distribution. The 4 controls listed above will go a long ways towards that goal. The proposal is that they are developed in separate [http://www.controlhaus.com ControlHaus] projects and built from source as part of the beehive build. The other goal mentioned above is to add some common useful controls to the distribution. The 4 controls listed above will go a long ways towards that goal. The proposal is that they are developed in separate [[http://www.controlhaus.com|ControlHaus]] projects and built from source as part of the beehive build.

System Controls

There are two general use cases for control authors:

  • Authoring business logic in a control for re-use
  • Authoring a generally useful (and often extensible) control for package and delivery

To support the second use case in the open source community, a sister site has been developed at ControlHaus. It is proposed here that the creation of some starter -- or "system" controls be created and developed there, and pulled in to the Beehive distribution.

Summary

It is important for Beehive to have some controls that simplify application development out of the box. The plan below will have two goals:

  • Add some of the most common useful controls to the Beehive distribution
  • "Seed" the ControlHaus community so that other control projects will begin development there.

BEA Systems has several generally useful controls that were developed for the 8.1 Workshop product. They would like to donate and continue development of these controls in ControlHaus. The implementations will be container independent implementations. The list of these controls is:

  • JDBC Control
  • Web Service Control
  • EJB Control
  • JMS Control

Details

By placing the development of system controls in ControlHaus we can grow the control authoring community, and "seed" ControlHaus with something real and useful. We may want to pull development on the system controls into Beehive at a later date.

The other goal mentioned above is to add some common useful controls to the distribution. The 4 controls listed above will go a long ways towards that goal. The proposal is that they are developed in separate ControlHaus projects and built from source as part of the beehive build.

They will be built into the Beehive distribution like so:

$BEEHIVE_HOME
  lib/
    controls/
      jdbc-control.jar (built from [http://www.controlhaus.com ControlHaus] source)
      web-service-control.jar (built from [http://www.controlhaus.com ControlHaus] source)
      jms-control.jar (built from [http://www.controlhaus.com ControlHaus] source)
      ejb-control.jar (built from [http://www.controlhaus.com ControlHaus] source)
      runtime/
        controls.jar

Open Issues

* How will the ControlPacks be versioned and certified?

Controls/SystemControls (last edited 2009-09-20 23:24:32 by localhost)