river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: OSGi RFC 119 Distributed OSGi - (Was [RE: OSGi and Jini])
Date Wed, 15 Jul 2009 05:01:54 GMT
Gee, that looks easy Dennis,

We could also support using java source too in JDK 1.6 or later as the 
compiler API is included, but groovy looks so much like java (less 
semicolon) it's not funny!

I can't see any reason why we can't use Groovy?  Users can choose with 
their feet.

What was the objection?

+1 Peter.



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()
>     }
>
> }
>
>
>
>
>


Mime
View raw message