Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: River Container (was surrogate container)
From: Greg Trasuk <trasukg@stratuscom.com>
In-Reply-To: <370EC3ED-6FC7-4FA4-ABB6-E018C1E822AC@gmail.com>
Date: Thu, 28 Nov 2013 14:44:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7030F36-F618-410A-99A6-BFA6EF2CA9E7@stratuscom.com>
References: <4D0FC0CA-779C-4498-8DBA-12A66BF32250@stratuscom.com>
 <12E20E22-95BE-44BE-AFCB-A52A2FE21384@gmail.com>
 <CF5D5632-5330-4584-AB8D-1D5A9DBB9152@stratuscom.com>
 <370EC3ED-6FC7-4FA4-ABB6-E018C1E822AC@gmail.com>
To: dev@river.apache.org


On Nov 28, 2013, at 12:59 PM, Dennis Reedy <dennis.reedy@gmail.com> =
wrote:

>=20
> On Nov 28, 2013, at 1159AM, Greg Trasuk <trasukg@stratuscom.com> =
wrote:
>=20
>>=20
>> I=92m all for bringing Rio in at the same time!  It=92s good to have =
choices. =20
>=20
> Perhaps what we should also focus on is to create (or move forward) =
either a standard archive (the SAR) or interfaces that define semantics =
for deployment. That way we can have multiple
>=20

Probably a good idea.  The way the river-container (probably needs a new =
name) is architected, we can add additional deployers that use alternate =
semantics or archive formats.  The first one I did handles services that =
are designed for =91com.sun.jini.start=92, but there=92s no reason we =
couldn=92t add others.  I=92m already thinking about re-implementing the =
Harvester-style API.  But even that=92s looking pretty dated.  That=92s =
what I mean when I say it=92ll make a nice test bed - for example, I=92d =
really like to be able to do

@Service
@ServiceAttributes( { @Name(=93Hello=94) })
public class HelloImpl implements Hello {
	public String sayHi(String name) {
		return =93Hi there =93 + name;
	}
}


>> Is the code provenance clear?
>=20
> In some places there are dual copyrights, from (1) Sun Microsystems =
and (2) to the original author or authors. The NOTICE contains =
contributions from:
>=20
> This product includes material developed by Asarian Technologies LLC.
>=20
> This product contains material developed by Elastic Grid LLC.
> (http://www.elastic-grid.com)
>=20
> This product includes material developed by Sun Microsystems, Inc.
> (http://www.sun.com).
>=20
> This product includes material developed by GigaSpaces, Inc.
> (http://www.gigaspaces.com).
>=20

I see it=92s Apache licensed.  Ideally we=92d have a CCLA in place from =
all the corporate contributors, but I personally don=92t know if that=92s =
required if the contributed code is ASL2.  We might have to consult more =
experienced Apache people.


Greg.

>=20
>> I think we can all agree that telling anyone to start writing =
services using only the JTSK is cruel and unusual punishment.
>=20
> Indeed.
>=20
> Regards
>=20
> Dennis
>=20