[
http://jira.jboss.com/jira/browse/JBIDE-535?page=comments#action_12381698 ]
Viacheslav Kabanovich commented on JBIDE-535:
---------------------------------------------
Here is copy of discussion in e-mail.
the wizard only shows wtp-provided servers
Wizard is to show all servers that appear in Servers view.
Does that mean 'wtp-provided', and what servers are not wtp-provided?
Wizard groups servers by runtimes, new runtime can be added here
(duplicating Preferences/Server/Installed Runtimes/Add)
When runtime selected, e.g. JBoss 4.2 Runtime, 'Target Server'
section of wizard shows servers based on it. New server can be created
(duplicating Servers view/New/Server).
Finally, when finished with a selected target server, the main wizard
action adds the project to it duplicating performance of
Servers view/Add and Remove Projects for an added project.
seem to be 100% duplicates of existing features in WTP
So, that
is true, just this action presents alternative working flow,
starting with a project in Project Explorer, and giving the opportunity
to create runtime and server as needed without opening Preferences
and Servers view.
the publish action is being run from the UI thread
Then
let's make it a background job. There was a case requirement
that made us to prefer UI thread. When JSF project is created by
wizard with option register in server, runnung on server had to be
immediately available. If publishing had been done in background
job, run action could have been started before publishing was
completed, which was undesirable.
some elements in the code lead me to believe this isn't even
intended to
work for JBoss servers, only Tomcat servers
This action was first developed long
before WTP's servers framework
appeared, and being gradually modified to become in the end
just a duplication of WTP's features, its code in some places
preserved relics that may give such impression
So, the question is to modify or to remove?
Slava
----- Original Message -----
Max Rydahl Andersen wrote:
This feature and other related features to the web "view" seem to be 100%
duplicates of existing
features in WTP and thus I rather remove/replace them if they don't work and/or
don't provide any
added value.
But yes - lets get these issues raised and sorted out if there is a
need for the feature.
/max
Who is in charge of the "Register Web Context In Server"
action when right-clicking a JSF project?
There are several issues here.
First, of course, is no documentation.
Second, the wizard only shows wtp-provided servers for some reason.
Third, the publish action is being run from the UI thread causing severe lockup.
(JBIDE-535)
Fourth, some elements in the code lead me to believe this isn't
even intended to work for JBoss
servers, only Tomcat servers, though there is no indication in the UI that this is true.
Fifth, and this one is probably my fault, this jira issue went
unassigned since April. I admit this one > is my fault but I'm used to searching
JIRA by things assigned to me. I'll try to be more diligent here.
Please someone get in touch with me as to how this is intended to
work. This action cannot be
allowed to remain the way it is, and I'd be glad to fix it if I understood what it
was supposed to be
used for.
- Rob Stryker
RHDS hangs on 30-60 seconds when register and unregister project to
JBoss server
--------------------------------------------------------------------------------
Key: JBIDE-535
URL:
http://jira.jboss.com/jira/browse/JBIDE-535
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Environment: Widows XP
RHDS build-333
Reporter: Anton Klimkovich
Assigned To: Viacheslav Kabanovich
Fix For: 2.0.0.CR1
1Create JSFKickStart for example
2 Add JBoss server
3 Right click on project ->Red Hat Developer Studio JSF->Register Web Context in
Server (Unregister)
4 In Target Server select JBoss server and press Finish button
RHDS hangs on 30-60 seconds.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira