Doh I just realized that the .car files are now directories :), that
answers my last question.
So what I'd like to see in addition to keeping installed apps in a
different repository is a solution to the server being shutdown when
any configuration fails. I think if we keep user install
configurations in a separate repository we could say any
configurations that failed to start from the user repository should
not force the server to shutdown.
- sachin
On Apr 6, 2006, at 9:55 AM, Sachin Patel wrote:
And just so I get my terminology straight... is the term "config-
store" obsolete now? Or is there still a technical distinction
between a config-store and repository?
- sachin
On Apr 6, 2006, at 9:26 AM, Sachin Patel wrote:
So I just launched 1.1 and have a couple of questions... So it
looks like the repository now hosts both configurations and
runtime/user jars. This is really good but my concern is now that
user apps are not located in a separate location and when looking
for a given application I was overwhelmed and took me more time
then it should to find my app. So the question is would it be
possible to provide multiple repositories and configurations would
be deployed to it? I'm not sure if this is possible or how
complex it would be if it were possible and wether these multiple
repo's could be made aware of each other.
Secondly is there an equivalent to index.properties? If I wanted
to uninstall an app, where can I find the fully qualified artifact
ID?
Second question is that in 1.0 web apps were exploded so users if
wanted could easily modify running content if they wanted. This
is no longer and I assume this is because both webcontainer have
moved to using the configuation classloader is this assumption
correct?
Thanks.
- sachin
