Adrian Brock wrote:
The question is how easy is it to do all this overriding of
repository implementations to change behaviour and
not loose some aspect of the behaviour.
e.g. To programmatically create a module like on the other thread.
The tools of a repository are not defined by the spec,
Adrian Brock wrote:
I see a number of possible use cases here
(I'll continue with appserver example):
1) Fully JSR 277
The appserver and JavaEE specs are updated to fully understand
JSR277/294. In this case, the JavaEE deployment process would
probably make use of a JSR 277 repository.
2) P
On Wed, 2008-06-11 at 22:31 -0700, Stanley M. Ho wrote:
> >> 3) QoS - what tools are available for the repository
>
> The Java Module System implementation will come with a standard tool to
> manage module archives in the repository, e.g. install/uninstall, etc.
> Is there any particular aspect
On Wed, 2008-06-11 at 22:31 -0700, Stanley M. Ho wrote:
> >> 2) Model - parent/child or peer
>
> I think you meant the module system inteorp model, not the repository
> delegation model. Right?
>
I don't see the difference? Hierarchical or Peer delegation
policies between repositories are ortho
On Wed, 2008-06-11 at 22:31 -0700, Stanley M. Ho wrote:
> Hi Adrian,
>
> Adrian Brock wrote:
> > My critisms of using the JSR277 repositories to do the integration
> > included:
>
> I want to better understand your concerns around developing
> repositories, since I believe some of your concerns
Hi Adrian,
Adrian Brock wrote:
My critisms of using the JSR277 repositories to do the integration
included:
I want to better understand your concerns around developing
repositories, since I believe some of your concerns have already been
addressed in the draft API.
* There are already lot
Hi Adrian,
Adrian Brock wrote:
On Mon, 2008-04-28 at 20:16 -0700, Stanley M. Ho wrote:
2. Requirements
1. It shall be possible for an OSGi container to implement the
Java Module System.
2. It shall be possible for a JAM module to express an import
dependency on any Mod
On Mon, 2008-04-28 at 20:16 -0700, Stanley M. Ho wrote:
> 2. Requirements
> 1. It shall be possible for an OSGi container to implement the
> Java Module System.
> 2. It shall be possible for a JAM module to express an import
> dependency on any Module Definition in any Jav
