[JBoss JIRA] Created: (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
by Rob Stryker (JIRA)
Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
-------------------------------------------------------------------------------------------------
Key: JBIDE-7379
URL: https://jira.jboss.org/browse/JBIDE-7379
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.2.0.Beta2, 3.2.0.CR1
Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args.
Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for.
This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin.
It currently seems to be saving only servers and not the runtimes.
--
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
13 years, 5 months
[JBoss JIRA] Created: (JBDS-1229) ESB binary export from JBDS doesn't include source
by Stelios Koussouris (JIRA)
ESB binary export from JBDS doesn't include source
--------------------------------------------------
Key: JBDS-1229
URL: https://jira.jboss.org/browse/JBDS-1229
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: libmanagement
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Trying to export ESB binary along with the source code of
a) the esb actions
b) the referenced jars
The result of setting the references to other projects/jars via
ESB Project --> Properties --> Module Assembly and then
ESB Project --> Export --> ESB --> clicking the "export source files"
the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects.
--
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
13 years, 5 months
[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
13 years, 5 months
[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
13 years, 5 months
[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
13 years, 5 months