On Wed, 2003-10-29 at 20:01, Alex Karasulu wrote:
> <snip/>
>
> > 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.
> >
> > Are there any implications for a security model?.
> [Karasulu, Alex]
>
> Your right the whole purpose for a repository is for keeping things in one
> place. However keep in mind that this so called application repository is
> really a artifact cache for the application and not a REPOSITORY REPOSITORY
> like ibiblio etc where you snarf down dependencies. The application
> repository is the local disk cache of all the dependencies pulled down from
> the remote repo.
>
> But your question still holds does it make sense to "allow" multiple
> artifact cache' one per application. I don't really know the answer to this
> right now because I have not encountered the use cases. The safest approach
> I think is to allow for it and leave it up to the user to decide and
> configure. What do you think?
>
> Alex
>
I'm trying to think of reasons to have multiple repositories. Security
may be one.
The system repository contains the bootstrapping resources so multiple
versions of merlin could be run, which may be important if merlin
changes dramatically.
I started to look at this as I was embedding merlin as a component
service in a turbine app of mine. The question was:- should we have a
complete merlin installation in webapp/WEB-INF? Steve suggested that
this is normally a read-only location which would have implications for
programmatic updating of artifacts in a repository. If we were moving
out of the WEB-INF directory then it made sense to perhaps think of a
local repository which could hold artifacts for any merlin component. I
was therefore very interested in your work on kernel context and
builder.
I don't know the answer but consider the following structure :
Merlin
|--- James
|--- Jetty
|--- webapp
|--- Merlin
|--- webapp
|--- Merlin
|--- Ldapd
|--- FtpServer
I guess this is possible. It's mainly a problem if you are running
multiple webapps with individual merlin installations. However, Turbine
has its own AvalonComponentService available to each webapp, which by
default makes the structure a one Merlin installation per Turbine
webapp.
I think that it could be done either way, and should almost certainly be
permitted. However, I think I might lean toward the option of a single
repository if possible and make it the default.
It might make sense to ask what all the various users think, and if its
likely whether multiple instances of merlin will be run in practice.
Keeping it all in WEB-INF for now does make it easier for my
TurbineAvalonMerlinComponentService. No trying to load stuff from
outside the web-app context!
Thoughts anyone?
Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Courcoux <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
