Last message here concerning building a DOM.
On reading I will use the pull parser and only validate if I get an
exception. The xsd files
are in the GEOSERVER_DATA_DIR/security/..., users can user their own
tool for validating
if the modify the xml files manually, I will point out this fact in
On Thu, Jun 9, 2011 at 11:25 AM, wrote:
>> Oh, I thought you were using xstream, which does not build a DOM,
>> uses a pull parser which is faster.
>
> You have the choice,
> XStream xstream = new XStream(new DomDriver());
Yep, thought it's a discouraged approach (because it's slow)
>>
>>>
>>>
Zitat von Andrea Aime :
> On Thu, Jun 9, 2011 at 10:47 AM, wrote:
>> Please read below
>>
>> Zitat von Andrea Aime :
>>
>>> On Thu, Jun 9, 2011 at 6:37 AM, wrote:
This is more a design question:
FileWatcher checks for external modifications of a file. But if
tgeoserver
On Thu, Jun 9, 2011 at 10:47 AM, wrote:
> Please read below
>
> Zitat von Andrea Aime :
>
>> On Thu, Jun 9, 2011 at 6:37 AM, wrote:
>>>
>>> This is more a design question:
>>>
>>> FileWatcher checks for external modifications of a file. But if
>>> tgeoserver code is writing the content of this
Please read below
Zitat von Andrea Aime :
> On Thu, Jun 9, 2011 at 6:37 AM, wrote:
>> This is more a design question:
>>
>> FileWatcher checks for external modifications of a file. But if
>> tgeoserver code is writing the content of this file itself, how can I
>> tell the FileWatcher NOT to ind
On Thu, Jun 9, 2011 at 6:37 AM, wrote:
> This is more a design question:
>
> FileWatcher checks for external modifications of a file. But if
> tgeoserver code is writing the content of this file itself, how can I
> tell the FileWatcher NOT to indicate that the file is modified forcing
> an additi
This is more a design question:
FileWatcher checks for external modifications of a file. But if
tgeoserver code is writing the content of this file itself, how can I
tell the FileWatcher NOT to indicate that the file is modified forcing
an additional reload.
Proposals
1) add a method
setK
