I've created an issue on Jira.
https://issues.apache.org/jira/browse/RIVER-379
Have you got any initial concepts, draft implementations, ideas etc?
Please post them on River-379
Cheers,
Peter.
Dennis Reedy wrote:
A 'container' is one small part of deployment. Sure Rio has a container (as do
all the projects you listed below), and you can start any of the stock River
services using Rio, but Rio is much more than that. If all you want is a
container use ServiceStarter.
Perhaps whats River needs a something that had been proposed much earlier, and
that is a standard service descriptor/archive that documents that meta data
associated with a service (artifacts, configuration, system requirements, etc
....). In this way developers dont require a standardized deployment container,
but can be confident that using a standardized archive and bundling format that
any 'container' can instantiate their service.
Gregg Wonderly wrote:
What would help the most is some more rigorous definitions for how
deployment occurs. The com.sun.jini.start interface is the only
tangible deployment signature for anything that might go into a
container.
I've suggested on this list before that this is an issue I feel we
need to discuss. I'd hope there is something which would could put
together as an SPI which containers could provide implementations of
so that not only can services be started, but they can interact with
the container to control lifecycle and Configuration needs.
