Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of
 SRS0=9ebR4J=DH=wonderly.org=gregg@yourhostingaccount.com designates
 65.254.253.78 as permitted sender)
Message-ID: <4A5CF1FB.3070709@wonderly.org>
Date: Tue, 14 Jul 2009 16:00:43 -0500
From: Gregg Wonderly <gregg@wonderly.org>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: OSGi RFC 119 Distributed OSGi - (Was [RE: OSGi and Jini])
References: <F5DF5420-6DCA-4873-A8E4-8E9F501D5CB3@mac.com>
 <4A44A1A1.4040201@zeus.net.au>
 <e736790906260808m4a0e451eqac270ea54c748b15@mail.gmail.com>
 <4A44EBA3.8030707@wonderly.org>
 <e736790906260918m23fd5751mbe27e445f7ec57e@mail.gmail.com>
 <0CC21688-E720-40BB-8237-D47B4DEE4F48@wonderly.org>
 <e736790906262107t30323f25m6f3369aa306083ec@mail.gmail.com>
 <4A4921FA.3030408@wonderly.org>
 <510143ac0907030226i22b4d6e9tf70857d357f115f4@mail.gmail.com>
 <e736790907030825m322488e0rcb75dfb347eab059@mail.gmail.com>
 <e736790907030930w289e3324wd251f0b7d1489de2@mail.gmail.com>
 <964EAC824495234A86F3C47DA8BD8AAD1776B4@sucden-exch.sucden.co.uk>
 <E099BB07-376A-4357-9920-7D2C77F57927@gmail.com>
In-Reply-To: <E099BB07-376A-4357-9920-7D2C77F57927@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Gregg Wonderly <gregg@wonderly.org>

Dennis, can you add any additional information about how configurations of 
multiple things are put together in either single files, or how multiple files 
are integrated together?  I do like the simplicity and the power of this.

It might also be interesting to see if a Scala version would be interesting or 
have any different capabilities since there are additional language features 
there too.

Gregg Wonderly

Dennis Reedy wrote:
> 
> On Jul 13, 2009, at 753AM, Tom Hobbs wrote:
>>
>>
>> Someone on the Jini-Users (or similar, I can't quite remember) a while
>> ago was talking about using Groovy classes to describe service
>> configuration.  Something like this sounds pretty neat, but anything
>> that needs to be recompiled for changes can take affect is likely to be
>> unworkable for obvious reasons.
> 
> I brought up the Groovy config support. Rio has switched over from the 
> Jini configuration file approach to now use Groovy classes. No 
> compilation is required, the Groovy classes are parsed when loaded by 
> the GroovyConfiguration utility. A simple example of a Groovy 
> configuration for Reggie follows:
> 
> @Component('com.sun.jini.reggie')
> class ReggieConfig {
> 
>     String[] getInitialMemberGroups() {
>         def groups = [System.getProperty(Constants.GROUPS_PROPERTY_NAME, 
> 'rio')]
>         return (String[])groups
>     }
> 
>     String getUnicastDiscoveryHost() {
>         return java.net.InetAddress.getLocalHost().getHostAddress()
>     }
> 
> }