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

Posted to dev@beehive.apache.org by "Kyle Marvin (JIRA)" <be...@incubator.apache.org> on 2004/12/01 16:17:30 UTC

[jira] Commented: (BEEHIVE-100) Configurable services definition

     [ http://nagoya.apache.org/jira/browse/BEEHIVE-100?page=comments#action_56060 ]
     
Kyle Marvin commented on BEEHIVE-100:
-------------------------------------

Great points, Brett.  

- The enumeration of available services is problematic in an implicit classloading system, unless there is some additional mechanism above it that provides insight into a jar's contents (i.e. the contextual services inside of it)

- If the relationship between service interfaces and providers is one-to-many (i.e. there are different implementations for different contexts), then implicit loading/conventions also break down.

I'm just hoping to keep two simple cases relatively simple:

- a contextual service that has a single provider for all contexts (ex. ControlBeanContext)

- a contextual service that has a single provider but is only available in a limited set of contexts (ex. HttpRequest)

I'll withdraw concerns about a config-file based approach... if we can come up w/ a model that supports merging multiple config files (i.e. potentially ones that describe the contents of a jar), so there is no single uber-config that an end user is forced to manage, or some indirection mechanism where the uber-config can "pull" definitions from elsewhere.

We should take a look at some of the HiveMind config stuff... it actually seems fairly flexible and useful and mind cover some of these use cases.

> Configurable services definition
> --------------------------------
>
>          Key: BEEHIVE-100
>          URL: http://nagoya.apache.org/jira/browse/BEEHIVE-100
>      Project: Beehive
>         Type: New Feature
>   Components: Controls
>     Versions: V1Alpha
>     Reporter: C Brett Bennett
>     Priority: Minor

>
> A simple scheme to allow for a container specific control container context to have a configurable set of services to be defined. This scheme can then be implemented within
> various containers, including standalone ones to define the services to be provided within
> those container.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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