[JBoss JIRA] Created: (JBIDE-473) JBoss AS ignores context root property of dynamic web project
by Viacheslav Kabanovich (JIRA)
JBoss AS ignores context root property of dynamic web project
-------------------------------------------------------------
Key: JBIDE-473
URL: http://jira.jboss.com/jira/browse/JBIDE-473
Project: JBoss Tools
Issue Type: Feature Request
Reporter: Viacheslav Kabanovich
Open editor for Tomcat Server (double click Tomcat node in Servers view). The editor has two tabs - Overview and Modules. In Modules tab, it is possible to select a registered web project and call dialog for changing path (context root) property by Edit button. Then, for example, if project's name is MyProject but path is set to /OurProject, in order to access the application running on Tomcat server one has to type in browser an address like http://localhost:8080/OurProject rather than http://localhost:8080/MyProject.
Red Hat studio defines menu action 'Register Web Context in Server', which invokes dialog that allows to set context root property. That works fine with Tomcat server, but fails with JBoss AS, because it seems that its implementation ignores this property of web project when deploying it. Hence, the request is to develop this functionality of JBoss AS to the level of Tomcat server.
Context root property is accessible through class org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities with methods
public static void setServerContextRoot(IProject project, String contextRoot)
public static String getServerContextRoot(IProject project)
--
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
12 years, 1 month
[JBoss JIRA] Created: (JBIDE-8276) Suggest removing related servers when removing RSE connection
by Libor Zoubek (JIRA)
Suggest removing related servers when removing RSE connection
-------------------------------------------------------------
Key: JBIDE-8276
URL: https://issues.jboss.org/browse/JBIDE-8276
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Libor Zoubek
Assignee: Rob Stryker
If a server is created using deltacloud it is related to RSE connection. If user removes RSE Connection and then tries to start server, he gets error about possibly deleted connection, which is fine. Is it possible to suggest him deleting related servers when deleting RSE Connection like it is when server runtime is deleted?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (JBIDE-2625) add an "application stop/application start" option to jboss server view
by Francisco Jose Peredo Noguez (JIRA)
add an "application stop/application start" option to jboss server view
-----------------------------------------------------------------------
Key: JBIDE-2625
URL: https://jira.jboss.org/jira/browse/JBIDE-2625
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
Sometimes, and application just enters an infinte loop (because of a programming error, because it can not find a class, etc) in those cases one needs to stop all the application server but sometimes, the problem can be solved simply by stopping that particular application, fixing the problem, and starting it again, and, since one doesn't have to restart Jboss, it takes a lot less time.
--
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
12 years, 1 month
[JBoss JIRA] (JBIDE-10550) [UI][Usability] Streamline UI for server editor and all possible options
by Rob Stryker (Created) (JIRA)
[UI][Usability] Streamline UI for server editor and all possible options
------------------------------------------------------------------------
Key: JBIDE-10550
URL: https://issues.jboss.org/browse/JBIDE-10550
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
The Server Editor has often been called "too busy" with unrelated settings populating it in a rather disorganized fashion. Less-often used settings, such as which pollers to use, or manually setting ports, have often been suggested that they be hidden a bit so as not to distract users.
With several jiras open for adding additional settings (ex: expose management port? or, for openshift, automatically git-add new files before commit?), simply throwing them into the Server Editor would only serve to clutter it further. A uniform UI with a real design and intuitive location for new settings should be created, with clear outlines for what belongs in the server editor (very little) vs what is a more advanced setting and can be hidden (though still not too far... user should not need to go 'DIG' to find it).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-9830) Option to handle deployment directories manually
by Kevin Formsma (Created) (JIRA)
Option to handle deployment directories manually
------------------------------------------------
Key: JBIDE-9830
URL: https://issues.jboss.org/browse/JBIDE-9830
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Eclipse Indigo Release, Windows 7
Reporter: Kevin Formsma
Assignee: Rob Stryker
Currently, JBoss Tools adds the deployment folder to the scanner list. When using custom deploy folders, an option to disable the automatic deployment of the folder and have the user manually configure the JBoss AS instance to scan the custom directory would be great. This option would by default, not be enabled to preserve existing behavior.
The use case for this is my team uses the JBoss AS 4.2 Prefix deployment scanner to deploy items in a predetermined order. When using the custom deploy directory, the Prefix deployment scanner doesn't seem to be used. I'm more than happy to setup the scanner myself, but then the AS tries deploying the items twice. Once for my scanner, and then another for the actions of JBoss Tools.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (JBIDE-9794) Add a CLI batch file feature
by Scott Stark (JIRA)
Add a CLI batch file feature
----------------------------
Key: JBIDE-9794
URL: https://issues.jboss.org/browse/JBIDE-9794
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: AS7
Reporter: Scott Stark
Assignee: Rob Stryker
This is a feature request to support a "CLI Batch" file that contains a collection of admin commands that will be run through the cli interface. There will need to be a remote/local notion to support the openshift case of having this file be in the application git repo and applied when pushed vs applied to a local server by invoking the cli tool.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month