[
https://issues.jboss.org/browse/JBAS-8133?page=com.atlassian.jira.plugin....
]
Jason Greene reopened JBAS-8133:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
Clear, understandable relationship between the domain management API
and the contents of the domain configuration files
-----------------------------------------------------------------------------------------------------------------------
Key: JBAS-8133
URL:
https://issues.jboss.org/browse/JBAS-8133
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Fix For: No Release
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
> One of the drawbacks of the WebSphere API is that it is not always clear
> what gets modified on the file system when running certain commands. It
> is common practice to save a WebSphere config, then make the edits in
> the console and save the difference for reference. Then develop your
> wsadmin jython scripts so that the changes made by the script match
> those made manually in the console. WebSphere 7 made improvements in
> this space so that the admin console can show you the jython that makes
> the same change you made in the console. I would like to be able to look
> at a JBoss config file and write the API commands knowing exactly what
> it will change on the file system. Having the command line API match
> that used by the domain controller would make things more predictable
> when using both in one's environment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira