[Apache Beehive Wiki] New: Controls/SystemControls

[be...@incubator.apache.org]

   Date: 2004-11-10T17:13:02
   Editor: MikeFoster <mf...@bea.com>
   Wiki: Apache Beehive Wiki
   Page: Controls/SystemControls
   URL: http://wiki.apache.org/beehive/Controls/SystemControls

   no comment

New Page:

= 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 [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. 

== 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 [http://www.controlhaus.com 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 [http://www.controlhaus.com ControlHaus].  The implementations will be container independent implementations.  The list of these controls is:

 * DB Control
 * Web Service Control
 * EJB Control
 * JMS Control

== Details ==

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. 

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 built into 2 "Control Packs" in [http://www.controlhaus.com ControlHaus] for distribution.  The packaging would look like this:

In [http://www.controlhaus.com ControlHaus] 
 * starter-cp.jar (DB Control and Web Service Control).  This is the most generally useful set.  This really solidifies the SOA story for Beehive.
 * j2ee-cp.jar (EJB Control and JMS Control).  Note, these don't rely on a J2EE container locally, and can call out remotely to a J2EE server (they have interesting Tomcat use-cases).

These will be built into the Beehive distribution like so:
{{{
$BEEHIVE_HOME
  lib/
    controls/
      starter-cp.jar (built from [http://www.controlhaus.com ControlHaus] source)
      j2ee-cp.jar (built from [http://www.controlhaus.com ControlHaus] source)
      runtime/
        controls.jar
}}}
The StarterControlPack and J2EEControlPack would be two separate projects in [http://www.controlhaus.com ControlHaus].  

== Open Issues ==

* How will the ControlPacks be versioned and certified?