[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562314#action_12562314 ] 

Snjezana Peco commented on JBIDE-7524:
--------------------------------------

> 1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with alot of whitespace (and its Runtimes not runtime)

Agree.

> 2) The import/export buttons does not seem to do anything beyound calling import/export dialog.

JBT Export/Import would need to export/import WTP and jBPM server definitions. That was working correctly before (JBDS 4.0.0.Beta1, for instance). Will check what was changed in the meantime (JBIDE-7373 and JBIDE-7370 include a lot of changes in the runtime plugin).

> 3) Search has a cancel button but it doesn't do anything

Can't reproduce on Windows and Linux. The Cancel button stops searching. Try to search the root folder and cancel it to check the issue.

> 4) Seam webapps seem to be picked up as seam runtimes - is that intended ?

The function has been copied from the installer. Will check and try to fix that.

> 5) Seam inside EAP is not detected
> 6) Drools inside SOA-P is not detected

Seam, AS, jBPM and Drools are part of EAP/SOA-P and aren't shown in the list that the user can see, but they are recognized and configured if they exist.
Do you think we need to show AS/Seam/Drools/jBPM runtimes when the engine recognizes EAP/SOA-P ?

> 7) The import/export of WTP servers seem to be a very bad hack...we probably have to live with it but at least we should try and make our import/export 
> simply wrap the relevant runtimes 

Runtime Export transfers WTP's servers.xml to the Eclipse preferences. Import loads these servers using the WTP API. The only problem is that the preference pages aren't refreshed and the user has to close/open Window>Preferences to see new runtimes. That's why I propose to move the JBoss Runtimes preference page to an Eclipse wizard, that would have the UI Max described in JBIDE-7527. The runtime plugin doesn't export/import the WTP/JBT Server Runtimes, but delegates that function to WTP.

> JBoss Tools Runtimes improvements
> ---------------------------------
>
>                 Key: JBIDE-7524
>                 URL: https://jira.jboss.org/browse/JBIDE-7524
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Max Andersen
>            Assignee: Snjezana Peco
>             Fix For: 3.2.0.Beta2
>
>
> After the discussion on mailing list we need to fix the current jboss tools runtime page/functionallity.
> I've found the following issues in my current testing:
> 1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with alot of whitespace (and its Runtimes not runtime)
> 2) The import/export buttons does not seem to do anything beyound calling import/export dialog.
> 3) Search has a cancel button but it doesn't do anything
> 4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
> 5) Seam inside EAP is not detected
> 6) Drools inside SOA-P is not detected
> 7) The import/export of WTP servers seem to be a very bad hack...we probably have to live with it but at least we should try and make our import/export simply wrap the relevant runtimes
> Furthermore these settings seem to not persist between workspaces and does not handle the original usecase of having runtimes configured when starting up a new workspace (requiring users to import/export is not the solution)
> I'm creating a few subtasks for this to outline the ideas.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira