Ah, ok, it is when the server is started up with a new deployments/
item, that is being added to the configuration and triggering the write.
On 4/4/11 8:42 AM, Brian Stansberry wrote:
That call is coming from the filesystem deployment scanner.
On 4/4/11 10:29 AM, Scott Stark wrote:
> I'm not sure what triggers the need to write out the standalone.xml in
> the testing I'm doing, but under some circumstance, a new setup of the
> server produces this warning, and then fails to start the next time
> because the interfaces section is all but missing. In fixing JBAS-9225,
> I'll add a comment to CommonXml.parseSimpleInterfaceCriterion that
> changes there need to be matched by changes to
> CommonXml.parseSimpleInterfaceCriterion
> CommonXml.writePropertyInterfaceCriteria.
>
> What would trigger a write of the standalone.xml if there are no admin
> commands being issued?
>