Eddie,
Is it possible to decouple the Control interfaces for these controls from the specific implementations. It strikes me that the beehive developer focus is on the Control interface and the Control implementation is replaceable. I would think that developers would like to rely on a stable and common Control interface for staple controls like jdbc and jms...but not want to be dependent on the implementations. For instance, one may want to have a J2EE JSR 109 based implementation of the web service control versus an Axis based implementation. Can you comment?
matt
Eddie O'Neil wrote:
All--
I'd like to propose that we move the code / samples / tests / documentation for the four core system controls from www.controlhaus.org into the Beehive SVN repository.
These four controls would include those at:
jdbc.controlhaus.org ejb.controlhaus.org jms.controlhaus.org webservice.controlhaus.org
We would put these into:
trunk/systemcontrols
under the:
org.apache.beehive.controls.system.[jdbc|ejb|jms|webservice]
packages.
I've just received confirmation that the code grant covering these four controls (and all supporting files) has been received and recorded by the ASF, so we should be clear of any legal / copyright issues given that this code currently is BEA copyright in the controlhaus SVN repository. We *will* change this to the ASF copyright before it's 'in the repository.
I for one am totally +1 on this -- it will be great to have all of the code shipping with a Beehive distribution together in a single repository with shared test / doc infrastructure, etc.
Eddie
