Andr? van Toly <[EMAIL PROTECTED]> wrote:
> At 10:30 +0100 12-03-2004, Michiel Meeuwissen wrote:
> >Andr? van Toly <[EMAIL PROTECTED]> wrote:
> >> >
> >> >Indeed. But now it is in core too. Where it actually was missing was in 
> >> the
> >> >xmlimporter application, I think.
> >>
> >> OK. I'll put it there.
> >> And this means it should not be in de
> >> /WEB-INF/config/modules directory but in the
> >> config/modules directory of the application?
> >> Because by default it is inactive?
> >
> >Yes, the install target of the application will put it there (if you use
> >it). Also in the package's zip it will be in WEB-INF/config (so unpackging
> >the zip will install the app).
> 
> I thought so.
> 
> >By default it can be set active in the application, because the application
> >makes not sense without it.
> >
> >If you wanted it inactive, you should not have installed it it the first
> >place, I figure..
> 
> OK. I get it. But what's the policy? For 
> instance: In 1.7 rc2 modules/communityprc.xml is 
> set to active although the application itself is 
> not installed (autodeploy=false) and generated a 
> warning in the log cause it is unable to find 
> it's builders, like message.

That is a bug then. I think the community applciation should be shipped
'installed' because it is for a long time the first example in the example
pages.

The other option is that it is not installed. It should not be 'half'
installed.

> And there are even more inactive configuration 
> files in the config/modules directory that as far 
> as i know don't have any applications related to 
> them. Currently in 1.7rc2:
> 
> communityprc.xml      active
> config.xml            active
> jdbc.xml              active
> linkchecker.xml               inactive
> mmadmin.xml           active
> mmbaseroot.xml                active
> mmflash.xml           inactive
> mmusers.xml           inactive
> rmmci.xml             inactive
> sendmail.xml          inactive
> stats.xml             inactive
> upload.xml            inactive
> xslconvert.xml                inactive


Modules can be 'inactive' if there are implemented e.g. in mmbase.jar but
not necessary for mmbase to run. Linkchecker might be an example of that.
You could swithc that to 'active'. There is as yet no 'linkchecker'
applicaiton in which it could be shipped 'active'.

Some of the xml's which you cite can probably moved to the scan-application
or removed altogether, because nobody seems to know where they are for.

A few months ago I already requested evaluation of those remaining
module-xmls, but did not harvest  much reactions.

 Michiel

-- 
Michiel Meeuwissen 
Mediapark C101 Hilversum  
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
 [] ()

Reply via email to