<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><br><br><hr id="zwchr"><blockquote id="DWT5989" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"David Bosschaert" <david@redhat.com><br><b>To: </b>"jboss-as7-dev@lists.jboss.org Development" <jboss-as7-dev@lists.jboss.org><br><b>Sent: </b>Monday, August 22, 2011 3:52:11 AM<br><b>Subject: </b>[jboss-as7-dev] Management Console: changing values that require a restart<br><br>Hi all,<br><br>Just like to get the general feeling about this.<br><br>In the Management Console and via the Detyped API you can in some cases <br>modify configuration that requires a restart in order to become <br>effective. I'd like to find out what the general feeling is about this:<br><br>Option 1: make it editable via the Console and display a message that <br>changing this configuration requires a restart.<br></blockquote>Anything that should be able to be changed should be able to be changed through the UI, so Option 1 is the way to go. Certainly, a message that says it won't take affect until you restart the server is good. We could also consider adding a step to the process that allows them to do the restart at that point, schedule a restart at a latter time, or just have the message.<br><blockquote id="DWT5990" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><br>Option 2: make it viewable only.<br><br>So option 2 is clearly the safest option, but has a drawback that people <br>can't use the console to specify this configuration, they'd have to <br>crack open the .xml and edit that.<br><br>Option 1 gives people a fancy editor over standalone.xml / domain.xml <br>but does have the disadvantage that the specified values don't get <br>applied until the restart is done.<br><br>How do we generally handle this? Obviously, the best thing to do is <br>change the behaviour so that the restart isn't needed by sometimes this <br>isn't the highest priority within the realm of time constraints...<br></blockquote>If we can change the behavior to not require a restart that would be preferable. If we could come up with a list of changes that do require a restart, we could do two things with it. We could document it in the administration guide, but we could also track it via Andiamo, and make determinations on which things would be the most beneficial to invest in making it that we don't have to do a restart, and change things over time (release to release).<br><br>Andy<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><br>Cheers,<br><br>David<br>_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></blockquote><br></div></body></html>