Sahoo wrote:
> Jerome Dochez wrote:
>>
>> On Jul 25, 2008, at 6:23 PM, Sahoo wrote:
>>
>>> Jerome,
>>>
>>> Can you please explain use of sub-directories like web, ejb under
>>> modules directory. Who decides which modules go under what sub-dir?
>> modules private to a container go into the subdir, anything shared go
>> in modules.
> Statically determining what modules are needed for a particular
> container may not always lead to correct result, as the system can
> wire stuff differently.
as the system evolve based on user's installation of extensions, we
might indeed have a few modules installed in different places, we neeed
to be able to survive duplicate module installation.
>>> How is it decided? How does it affect packaging spec?
>> I don't think it does but I can check.
>>> Finally, does the overhead in implementation have enough return of
>>> investment?
>> well, it's a user feature, I think it would be nice to be able to
>> replace or delete containers by just removing a sub-dir and have v3
>> continue working fine without any reconfiguration (assuming no
>> applications were deployed to that container of course).
> I don't get the basic use case. What happens to IPS metadata when user
> uses something like "rm" to remove files installed via UC?
of course it would not work but I certainly hope that you are not
considering UC the "only" way to update or extend the application
server. If we are very successful, a lot of users might provide
extensions, few through the UC.
overall, I think it's a good exercise we ensure v3 can work correctly
with several repositories, it limits the assumptions made that we have
all our modules located in one place.
jerome
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>