[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Attachment: installer-step.png installer-step-new.png installer-step-edit.png -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Attachment: (was: installer-step-edit.png) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Attachment: (was: installer-step-new.png) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-425: ------------------------------------------ installer-step.png shows a JBossAS installation being picked up. This is good but what we should be looking for configuring is JBoss EAP and JBoss SOA-P installations. Each of these have different runtimes in them (JBoss EAP will have a JBoss AS and a Seam 1 and somtimes Seam 2), SOA-P the same but also a jbpm runtime that the jbpm plugins can/should use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Description: The installer need to be able to handle configuration of multiple JBoss AS runtimes at installation time. 1. installer-step.png shows 'Install JBoss Enterprise Application Platform' after modifications to let user configure locally available JBoss Application Servers. 1.1 List of JBoss AS's that will be configured after first JBDS start up. Content of this list can by filled automatic by Find action or one by one using Add buttons. Content of the list can be edited by Edit and Remove button. 1.1.1 Find action let user select folder where search of available JBoss Application Servers should be started. After folder is selected is searching available servers in folder hierarchy starting from one seleced by user. It generates Server Name for each found server as JBoss AS $version($index), where $version is a version of found server and $index is counter that is incremented every time when it finds version with $version that already has been found during search. So if in folder hierarchy selected for search there were three JBoss AS and each had the same version, three Servers would be found after Finding is finished: JBoss AS 4.2.2(1) JBoss AS 4.2.2(1). After finding list can be edited by Add, Remove buttons. 1.1.2 Add button shows dialog install-step-add.png. In first version user should fill all fields, in next name and version could be filled after server location is selected. Vlidation rules for this dialog are: check folder is exists, check that folder contains JBoss AS installation, check that JBoss AS installation and selected version is the same, check that there is no server with the same location, check there is no server with the same name. 1.1.3 Edit button shows dialog to edit selected item is servers list install-step-edit.png. Edit button is not available if several items selected in list. Validation rules is the same as fro Add dialog. 1.1.4 Remove button delete items selected in server list. 2. Browse buttons show the same system dialog to select folder install-step-browse.png. 3. Next button for installation wizard is always available no matter is server list contains items or not. 4. List collected on this step should be saved in .properties file as server1=$serverName1, $serverLoaction1, $version1 serverN=$serverNameN, $serverLoactionN, $versionN somewhere inside JBDS installation directory and used to register servers during virst start up. Priorities for Beta1 are all mentioned above except: Find action and getting version for JBoss AS from installation folder for version field initialization and verification in Add/Edit dialogs. was: The installer need to be able to handle configuration of multiple JBoss AS runtimes at installation time. The installer need to be able to handle configuration of multiple JBoss AS runtimes at installation time. 1. installer-step.png shows 'Install JBoss Enterprise Application Platform' after modifications to let user configure locally available JBoss Application Servers. 1.1 List of JBoss AS's that will be configured after first JBDS start up. Content of this list can by filled automatic by Find action or one by one using Add buttons. Content of the list can be edited by Edit and Remove button. 1.1.1 Find action let user select folder where search of available JBoss Application Servers should be started. After folder is selected is searching available servers in folder hierarchy starting from one seleced by user. It generates Server Name for each found server as JBoss AS $version($index), where $version is a version of found server and $index is counter that is incremented every time when it finds version with $version that already has been found during search. So if in folder hierarchy selected for search there were three JBoss AS and each had the same version, three Servers would be found after Finding is finished: JBoss AS 4.2.2(1) JBoss AS 4.2.2(1). After finding list can be edited by Add, Remove buttons. 1.1.2 Add button shows dialog install-step-add.png. In first version user should fill all fields, in next name and version could be filled after server location is selected. Vlidation rules for this dialog are: check folder is exists, check that folder contains JBoss AS installation, check that JBoss AS installation and selected version is the same, check that there is no server with the same location, check there is no server with the same name. 1.1.3 Edit button shows dialog to edit selected item is servers list install-step-edit.png. Edit button is not available if several items selected in list. Validation rules is the same as fro Add dialog. 1.1.4 Remove button delete items selected in server list. 2. Browse buttons show the same system dialog to select folder install-step-browse.png. 3. Next button for installation wizard is always available no matter is server list contains items or not. 4. List collected on this step should be saved in .properties file as server1=$serverName1, $serverLoaction1, $version1 serverN=$serverNameN, $serverLoactionN, $versionN somewhere inside JBDS installation directory and used to register servers during virst start up. Priorities for Beta1 are all mentioned above except: Find action and getting version for JBoss AS from installation folder for version field initialization and verification in Add/Edit dialogs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Description: The installer need to be able to handle configuration of multiple JBoss AS runtimes at installation time. 1. installer-step.png shows 'Install JBoss Enterprise Application Platform' after modifications to let user configure locally available JBoss Application Servers. 1.1 List of JBoss AS's that will be configured after first JBDS start up. Content of this list can by filled automatic by Find action or one by one using Add buttons. Content of the list can be edited by Edit and Remove button. 1.1.1 Find action let user select folder where search of available JBoss Application Servers should be started. After folder is selected is searching available servers in folder hierarchy starting from one seleced by user. It generates Server Name for each found server as JBoss AS $version($index), where $version is a version of found server and $index is counter that is incremented every time when it finds version with $version that already has been found during search. So if in folder hierarchy selected for search there were three JBoss AS and each had the same version, three Servers would be found after Finding is finished: JBoss AS 4.2.2(1) JBoss AS 4.2.2(1). After finding list can be edited by Add, Remove buttons. 1.1.2 Add button shows dialog install-step-add.png. In first version user should fill all fields, in next name and version could be filled after server location is selected. Vlidation rules for this dialog are: check folder is exists, check that folder contains JBoss AS installation, check that JBoss AS installation and selected version is the same, check that there is no server with the same location, check there is no server with the same name. 1.1.3 Edit button shows dialog to edit selected item is servers list install-step-edit.png. Edit button is not available if several items selected in list. Validation rules is the same as fro Add dialog. 1.1.4 Remove button delete items selected in server list. 2. Browse buttons show the same system dialog to select folder install-step-browse.png. 3. Next button for installation wizard is always available no matter is server list contains items or not. 4. List collected on this step should be saved in .properties file as server1=$serverName1, $serverLoaction1, $version1 serverN=$serverNameN, $serverLoactionN, $versionN somewhere inside JBDS installation directory and used to register servers during virst start up. Priorities for Beta1 are all mentioned above except: Find action and getting version for JBoss AS from installation folder for version field initialization and verification in Add/Edit dialogs. Getting version number can be a problem, so lets just ask it during installation. BTW now JBoss AS runtime wizard doesn't check version for selected JBoss AS folder. was: The installer need to be able to handle configuration of multiple JBoss AS runtimes at installation time. 1. installer-step.png shows 'Install JBoss Enterprise Application Platform' after modifications to let user configure locally available JBoss Application Servers. 1.1 List of JBoss AS's that will be configured after first JBDS start up. Content of this list can by filled automatic by Find action or one by one using Add buttons. Content of the list can be edited by Edit and Remove button. 1.1.1 Find action let user select folder where search of available JBoss Application Servers should be started. After folder is selected is searching available servers in folder hierarchy starting from one seleced by user. It generates Server Name for each found server as JBoss AS $version($index), where $version is a version of found server and $index is counter that is incremented every time when it finds version with $version that already has been found during search. So if in folder hierarchy selected for search there were three JBoss AS and each had the same version, three Servers would be found after Finding is finished: JBoss AS 4.2.2(1) JBoss AS 4.2.2(1). After finding list can be edited by Add, Remove buttons. 1.1.2 Add button shows dialog install-step-add.png. In first version user should fill all fields, in next name and version could be filled after server location is selected. Vlidation rules for this dialog are: check folder is exists, check that folder contains JBoss AS installation, check that JBoss AS installation and selected version is the same, check that there is no server with the same location, check there is no server with the same name. 1.1.3 Edit button shows dialog to edit selected item is servers list install-step-edit.png. Edit button is not available if several items selected in list. Validation rules is the same as fro Add dialog. 1.1.4 Remove button delete items selected in server list. 2. Browse buttons show the same system dialog to select folder install-step-browse.png. 3. Next button for installation wizard is always available no matter is server list contains items or not. 4. List collected on this step should be saved in .properties file as server1=$serverName1, $serverLoaction1, $version1 serverN=$serverNameN, $serverLoactionN, $versionN somewhere inside JBDS installation directory and used to register servers during virst start up. Priorities for Beta1 are all mentioned above except: Find action and getting version for JBoss AS from installation folder for version field initialization and verification in Add/Edit dialogs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-425: ------------------------------------------ I guess a Type is required (JBoss AS, EAP and SOA-P), but remember the versions for EAP and SOA-P are *different* from version numbers of JBoss AS .... No matter what, make sure that the name column is filled out with a decent default (e..g "JBoss EAP 4.2") and not just blank. Users should not have to type anything in all common cases. Yes. Seam we know how to, jbpm we need to hear from Koen what we should do. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Attachment: installer-step.png installer-step-edit.png installer-step-new.png -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-425: ------------------------------- Attachment: (was: installer-step.png) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBDS-425: ------------------------------- Attachment: patch.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Lex Dmitriev updated JBDS-425: ------------------------------ Attachment: rhds_edit_wiz.png rhds_new_wiz.png I would offer to use different icons for "edit" and "new" dialogs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Lex Dmitriev updated JBDS-425: ------------------------------ Attachment: (was: rhds_new_wiz.png) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBDS-425: ------------------------------- Attachment: screenshot-2.jpg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBDS-425: ------------------------------- Attachment: screenshot-4.jpg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBDS-425: ------------------------------------ I have some questions: 1. Why we need "Edit" button? I think it wouldn't be good if user can change type or version for Application Platform. 2. How can we find JBoss Application Servers? Loking for folder names and some specific files like "JBossORG-EULA.txt" is it enough? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Daniel Azarov resolved JBDS-425. -------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-425?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-425: ------------------------------------------ Thanks Greg. Daniel - looks like we don't have a good way of automatic finding installed appservers right now. Which config do you setup for the selected AS's ? Do you jus select the default config ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira