Re: [Exist-development] XSL PI and REST

[Dmitriy S. <sha...@gm...>]

Hi,

For now, PI instructions have higher priority than conf.xml settings, I
recommend to add option that will control that priority: <serializer
master="PI-conf" enable-xsl="no" - mean PI instruction will overwrite conf's
one, <serializer master="conf-PI" enable-xsl="no" - PI will be ignored
-- 
Dmitriy Shabanov
2010/6/1 José María Fernández González <jm...@us...>

> Hi Dmitryi,
>        the serializer already has that option at conf.xml level for XSL
> PIs, and that's the reason about these e-mails: the configuration option
> from conf.xml is not honored (i.e. is ignored) on REST because hardcoded
> defaults from REST module for this option (and others) are passed to the
> serializer, so global defaults are ignored/bypassed.
>
>
> On 06/01/10 14:21, Dmitriy Shabanov wrote:
>
>> Can we add on option auto-no (auto-yes, yes, no) at serializer
>> configuration? or something ... for now the behavior is quite clear -
>> files' PI instructions have higher priority, so we need on option to
>> change priority.
>>
>> 2010/5/31 José María Fernández González <jm...@us...
>> <mailto:jm...@us...>>
>>
>>
>>    Hi again,
>>            I opened bug #3008137 at Sourceforge about this issue, where
>>    I'm describing the problem, and a quick fix. If there is no
>>    objection, I would like to apply that fix on trunk on Wednesday.
>>
>>            José María
>>
>>    On 05/27/10 20:02, José María Fernández González wrote:
>>     > Hi everybody,
>>     > I have just realized that RESTServer enables XSL PI processing by
>>     > default, even when it is explicitly disabled in conf.xml through
>>     > '<serializer enable-xsl="no" ...'. Is there some (unknown) reason
>> for
>>     > this odd behavior? If it is not, I would like to fix it.
>>
>