Peter Courcoux wrote:
On Wed, 2003-10-29 at 08:27, Stephen McConnell wrote:
Alex Karasulu wrote:
When bootstrapping the Kernel I guess we use the system repository right?+1
When bringing up the application we use the application repository which is
referred to as the user repository. Are there any objections to calling
this the application repository? There could be reasons for separating
repositories for the various applications run by a user and in this light
the connotation of an application specific repository makes more sense to
me.
Steve.
Does it not make sense to have a single maven style repository? This
could provide access to versioned resources and keep them all in one
place. Separate user repositories for each application seems like it
might encourage or require duplication of common resources.
In my own environment I've had up to three seperate repositories in use. These included (a) maven's repo - linked to development, (b) a more stable merlin default application repository, (c) an test repository that I use for validating things like James before releasing.
The think is:
(a) we always have a default common shared application repository
which is basically ${merlin.home}/repository(b) we have option (already) to swtich in a different repository (e.g. the abstract merlin testcase switches in the maven repository as the default application repostory) depending on deployment requirements
(c) none of this is suggesting a different repo per app or anything like that - its simply more correct to refer to the repository in the code as the "applicable" repository - relacting an "application context"
Are there any implications for a security model?.
Yes.
Currently we have all permission assiged - but in the future a component will be given read access to the repository whereas we may want to control what permissions a repository itself has - e.g. a static repository than cannot perform remote updates as opposed to a dynamic repository.
Cheers, Steve.
Regards,
Peter
Alex
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
