[zzoss-devel] Re: application configuration

[Sandro Z. <san...@zz...>]

On Monday 12 May 2003 14:49, Christian Zonsius wrote:
> f=E4llt dir eine gute l=F6sung ein, wie wir das formular unter "configu=
re
> application" application spezifisch kriegen ? einfach eine
> configuration.php in die application zu legen w=E4re keine gute l=F6sun=
g. die
> eingabemasken mit der input.xml zu definieren schon besser, allerdings =
gibt
> es ja teilweise f=E4lle, wo danach noch was mit den config daten gemach=
t wird
> (z.b. die .htaccess-dist von conesys wird mit diesen daten ins applicat=
ion
> root geparst).
> das sollte man auch irgendwie sprachunabhaengig definieren k=F6nnen ...

Why do we have to provide the possibility to define individual applicatio=
n=20
parameters? All we need in "Configure Application" is that a user provide=
s us=20
with the root paths of the application - anything else is done within=20
packages aka the respective XML descriptors.

Parsing a .htaccess file with the data from "Configure Application" could=
 be=20
done with a new installer plugin package like=20
com.zzoss.installer.plugin.htaccess or even more general=20
com.zzoss.installer.plugin.config_builder. This plugin would do all the {=
ZI_}=20
replacements that are currently built into the Installer, so we gain high=
er=20
modularity.

I guess, we therefore have to extend the package.xml and add a=20
plugin-attribute to the file element, like

<filelist>
=09<file baseinstalldir=3D"/" plugin=3D"com.zzoss.installer.plugin.config=
_build"=20
name=3D"htaccess" />
</filelist>

or we make possible to define a pipe to specify the order of plugins that=
=20
should process the file:

<file baseinstalldir=3D"/" plugins=3D"plugin1|plugin2|plugin3" name=3D".h=
taccess" />

or we open the file element:

<file baseinstalldir=3D"/" name=3D".htaccess">
=09<plugin>plugin1</plugin>
=09<plugin>plugin2</plugin>
=09<plugin>plugin3</plugin>
</file>

Sandro