[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2319. ----------------------------------- Resolution: Rejected This is not necessary. The default is already login. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2319: ------------------------------------ So, really, the only 2 options for a user are disabled and enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2319: ------------------------------------ You are right there are 3 options, but from a usability and documentation (which is realize is semantics on this) is to only indicate the 2 options to change (why add login when it disappears from the config file) and explain the default behavior in documentation when the either of enabled/disabled are not specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Ted Jones edited comment on TEIID-2319 at 12/4/12 10:56 AM: ------------------------------------------------------------ That is the typical behavior of modules in AS7. If a value is set to the default, it is not written out to the standalone.xml. Even if you explicitly set the value in the standalone.xml to the default, it would not be re-written to the config after an update from the cli or other client. All three options are available from a client standpoint though. was (Author: tejones): That is the typical behavior of modules in AS7. If a value is set to the default, it is not written out to the standalone.xml. Even if you explicitly set the value in the standalone.xml to the default, it would not be re-written to the config after an update from the cli or other client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-2319: ---------------------------------- Because if they set the value to enabled or disabled, they need a way to get back to the login option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-2319: ---------------------------------- The standalone.xml is not the client.. the client is the CLI, web console or RHQ plugin. The user should never *have* to muck with the standalone file. All options should be available in the clients. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2319: ------------------------------------- Van, there are three options (login, enabled, disabled). Whether standalone.xml saves it or not is not a question, it is how AS7 persists configuration, that does not mean that option is not available. As Ted said, no user is editing the standalone.xml directly, they should use one of the client tools. If they are using one of the client tools and going from "disabled" to "login", they need to specify that to change it. Removing from document, saying to user there is only two options is not correct. Even we specify three options on client tools, if the user wants learn what is that "login" option, they would certainly refer back to document. Configuration != Documentation IMO, this was not a productive conversation, we should leave document as is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2319: --------------------------------------- Van that's not the issue. The salient stuff here is that: 1. The default for the transport is LOGIN, so config/script changes are not needed. 2. As Ramesh states clearly, Configuration != Documentation - so we do not want to embellish the provided teiid standalone xml/cli unnecessarily 3. As Ted states, users should typically not modify the xml configuration directly. The documentation should avoid recommending that approach. 4. Default values are still valid to document as the user may need to switch back to that value if they've changed to a non-default. So from here the question is just what documentation changes, if any, are needed clarify socket encryption. All other doc related issues should probably spawn a different issue/forum topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2319: --------------------------------------- It's perfectly valid to move in that direction and can be spawned as a new issue. Any of our docs that recommend editing the xml config directly are just taking a short cut and/or were basically a direct port from the old docs. As for removing all of the xml snippets, that seems unnecessary as showing the resultant xml in some places can be instructive (just as with the AS docs), but a non-xml update method should be shown (which probably means CLI in the core docs). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira