On Thu, 3 Jan 2002, Nicola Ken Barozzi wrote:
> > Cool! Will invesitgate further. Maybe we can set the context
> > path for fop processing then!!
> >
> > If you already have more insight in this please give me a direct
> > mail or post to cocoon-dev.
>
> Ok so Configuration is static and here is the relevant code taken from the
> FOP ant task:
>
> org.apache.fop.configuration.Configuration.put("baseDir",
Hm... that's ugly! So we cannot really change this inside the pipeline
in the serializer setup.
[snip]
> What do you think is better to put as a relative value?
> The problem is that Configuration is static for now, so I can to set the
> base dir to the Constants.DEFAULT_CONTEXT_DIR or to a configured param;
> anyway only one per VM. :-(
exactly ...does not make much sense this way
> I think that the best is a configuration param, so that in the future when
> Configuration is not static anymore we don't break contracts; the fixed conf
> basedir is used for all if present, if not each file is resolved with its
> relative url.
> Comments?
Well, I'm not quite sure if it makes sense to introduce a parameter for
this. It will be deprecated sooner or later anyway (when the fop
configuration is not static anymore).
So I'd propose to set the fop basedir on serializer setup to the servlet
context dir. Although still quite ugly this is half-way. But we should
make clear that this is a interim sollution that will changed sooner
or later. So this should definitly only make it into HEAD.
But it helps...
So I'm +1 for the servlet context dir as basedir
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
