[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, 1 month
[JBoss JIRA] Created: (JBIDE-2183) Ctrl+shift+G binding causing warnings - can it be avoided ?
by Max Rydahl Andersen (JIRA)
Ctrl+shift+G binding causing warnings - can it be avoided ?
-----------------------------------------------------------
Key: JBIDE-2183
URL: http://jira.jboss.com/jira/browse/JBIDE-2183
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 2.1.0.CR1
Reporter: Max Rydahl Andersen
Fix For: 2.1.0.GA
in latest cr1 I get the following in the Error log at startup:
eclipse.buildId=1.1.0.CR1
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK
Command-line arguments: -os win32 -ws win32 -arch x86
Warning
Tue May 06 15:03:32 CEST 2008
Keybinding conflicts occurred. They may interfere with normal accelerator operation.
Warning
Tue May 06 15:03:32 CEST 2008
A conflict occurred for CTRL+SHIFT+G:
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-1841) Error #1 while performing SchemaExport if server isn't started.
by Anton Klimkovich (JIRA)
Error #1 while performing SchemaExport if server isn't started.
---------------------------------------------------------------
Key: JBIDE-1841
URL: http://jira.jboss.com/jira/browse/JBIDE-1841
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 2.0.1
Reporter: Anton Klimkovich
Priority: Minor
Attachments: exception.txt, TestHib.zip
EXECUTE: Import attached java project.
EXECUTE: Open Hibernate Configuration View
EXECUTE: Right mouse click and select Add Configuration from context menu
EXECUTE: On Main tab select imported project and path to cfg.xml
EXECUTE: On Clathpath tab set path to hsqldb.jar
EXECUTE: On Mappings tab add path to mapping file.
EXECUTE: Press Apply button and Ok button
ASSERT: Hibernate configuration appear in Hibernate Configuration View
EXECUTE: Right mouse click on configeration in Hibernate Configuration View and select Run SchemaExport
FAILURE: java.sql.SQLException: socket creation error
Log attached.
--
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, 1 month