8:26 a.m.
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
By this I mean the buttons simply does not seem to do anything that
isn't already available from the normal import/export wizards.
I was not talking about the import/export not actually working. I assumed they work
within the limits discussed elsewhere.
I was just suggesting that since this search are not working well from within the
preferences pane no reason to have import/export
button just start the general import/export wizard when users can just use the normal
import/export.
The standard Eclipse export/import wizard (File>Export/Import>Preferences)
exports/imports Eclipse preferences. It doesn't export/import WTP and jBPM servers
because the jBPM and WTP plugin configure their own servers in a specific way (using
servers.xml and jbpm-installations.xml).
The runtime plugin exports/imports all standard Eclipse preferences as well as WTP and
jBPM servers. It does that in the following way:
When you click the Export button on the JBoss Runtimes preference page, the runtime plugin
does the following:
- converts WTP and jBPM server definition files (servers.xml and jbpm-installations.xml)
to string and set the specific the runtime preferences I have created in order to convert
those server definitions to the Eclipse preferences ("servers" and
"jbpms")
- calls the standard Eclipse export preference wizard that exports Eclipse preferences
including the "servers" and "jbpms" preferences
When you click the Import button on the JBoss Runtimes preference page, the runtime plugin
does the following:
- calls the standard Eclipse import preference wizard and imports Eclipse preferences
including the "servers" and "jbpms" preferences
- converts the "servers" and "jbpms" preference values to the
servers.xml and jbpm-installations.xml files and configures WTP and jBPM servers using WTP
and jBPM API.
JBDS also creates these servers when starting the first time. That is the reason why I
have added that functionality to the JBoss Runtimes preference page.
If we don't need to export/import WTP and jBPM servers (because we don't need them
or because WTP and jBPM will implement them), we can remove the Export/Import button from
the JBoss Runtimes preference page.
The search does stop, but it is not a very instant stop - it takes a
few seconds,
and sometimes many seconds.
Cancel is called for every directory. If a directory has a lot of children (especially of
the directory type), Cancel can be slow. Will try to call the Cancel action more
frequently.
> Do you think we need to show AS/Seam/Drools/jBPM runtimes when
the engine recognizes EAP/SOA-P ?
Wouldn't that be the most consistent ?
I will add them if you want.
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