[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
The attached patch includes the following changes:
- when calling the Search and Import action, the Preferences dialog is closed and opened
again which solves the problem with refreshing preference pages
Now you can create servers and runtimes using the Search button, export, import them and
the changes will be visible immediately.
- Runtime is renamed to Runtimes in the links
- the Seam recognizer is improved (web aplications are not recognized as Seam Runtimes)
- Cancel is called more frequently
- created a jira and patch for the problem with export/import Seam preferences (see
https://jira.jboss.org/browse/JBIDE-7577)
- when the runtime plugin recongizes EAP or SOA-P, the user is notified if the runtime
includes Seam, Drools and/or jBPM (see runtimeDialog.png)
In order to see the difference between the standard Eclipse Export/Import preferences and
JBoss Runtimes Export/Import preferences, you can do the following:
- create some Seam, Drools, JBoss AS, WTP, jBPM runtimes
- call File>Export>Preferences
- call File>Export>Preferences
- choose "JBoss Runtimes" preferences (or Export All Preferences)
- export the preferences to a file (testEclipseStandard.epf, for instance)
- call Window>Preferences>JBoss Tools>JBoss Runtimes
- click the Export button
- export the preferences to a file (testJBossRuntimes.epf, for instance)
- close Eclipse
- restart Eclipse in a new workspace
- call File>Import>Preferences
- choose the "JBoss Runtimes" preferences (or Import All Preferences)
- point to the file you previously exported using the standard Eclipse Export
wizard(testEclipseStandard.epf)
- import the preferences
You will see that WTP servers and jBPM runtimes aren't imported. They aren't
imported with the standard Eclipse Import wizard even if you use the testJBossRuntimes.epf
file.
- close Eclipse
- restart Eclipse in a new workspace
- call Window>Preferences>JBoss Tools>JBoss Runtimes
- click the Import button
- point to the file you previously exported using the JBoss Runtimes Export action
(testJBossRuntimes.epf)
- import the preferences
Now, all the runtimes including WTP and jBPM servers are imported correctly (the patch for
https://jira.jboss.org/browse/JBIDE-7577 has to be applied in order Seam Runtimes to work)
and shown immediately.
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.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira