Hi,<br><br>looking at this change, it looks like you &quot;just&quot; don&#39;t persist xml configuration(and as so making it read-only) <br>but that does not apply to the model itself for instance context.getResourceRegistrationForUpdate() would still work and not throw error that model is read only.<br>
<br>My impression was that we wanted to achieve also &quot;read-only&quot; model, probably this is task for the future...<br><br>Other than that, it looks good :)<br><br>--<br>tomaz<br><br><br><br><div class="gmail_quote">
On Sun, Jul 8, 2012 at 1:15 PM, Kabir Khan <span dir="ltr">&lt;<a href="mailto:kabir.khan@jboss.com" target="_blank">kabir.khan@jboss.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Brian asked me to get some feedback on this.<br>
<br>
The following commit <a href="https://github.com/jbossas/jboss-as/commit/435c862b9514bfcf0a036bb2b916ac3dc63b4f4a" target="_blank">https://github.com/jbossas/jboss-as/commit/435c862b9514bfcf0a036bb2b916ac3dc63b4f4a</a> implements the following new command line switches for <a href="https://issues.jboss.org/browse/AS7-4764" target="_blank">https://issues.jboss.org/browse/AS7-4764</a>:<br>

Standalone:<br>
--read-only-server-config<br>
<br>
Domain:<br>
--read-only-host-config<br>
--read-only-domain-config<br>
<br>
These work much the same as their &#39;standard&#39; counterparts, e.g. --server-config etc. apart from:<br>
*They allow an absolute path in addition to the relative path supported by --server-config etc.<br>
*The file passed in will never be overwritten, however the other history files do get persisted as usual so you can make changes to the config and copy the standalone.last.xml file to use that the next time you want to boot from a read-only config<br>

<br>
The reload operations now take the following parameters:<br>
-- use-current-domain-config (domain controller only)<br>
-- use-current-host-config (domain and host controllers)<br>
-- use-current-server-config<br>
The default value for all of these is false, and these parameters are only taken into account if --read-only-xxx-config was used. If false, the reloaded process is started with the initial, unchanged config that was passed in to --initial-xxx-config. If true, it uses the current model for the reloaded process (using the corresponding .last.xml file). The idea for the &#39;true&#39; path being that you might want to reboot into admin-only mode to make some changes which should take effect once the process is put back into normal mode.<br>

<br>
<br>
<br>
<br>
_______________________________________________<br>
jboss-as7-dev mailing list<br>
<a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br>
</blockquote></div><br>