[
http://jira.jboss.com/jira/browse/JBIDE-1841?page=all ]
Max Andersen updated JBIDE-1841:
--------------------------------
Summary: Improve error message when performing SchemaExport and an exception occurs
(e.g. SQL exception) (was: Error #1 while performing SchemaExport if server isn't
started.)
Issue Type: Feature Request (was: Bug)
we can improve the handling of the error, but we can unfortunately not detect if it is
becasue the db is not there...just that an SQL exception occurred which could mean alot of
things:
db not started
username/password not matchin
error in scheam creation
...etc.
Improve error message when performing SchemaExport and an exception
occurs (e.g. SQL exception)
-----------------------------------------------------------------------------------------------
Key: JBIDE-1841
URL:
http://jira.jboss.com/jira/browse/JBIDE-1841
Project: Tools (JBoss Tools)
Issue Type: Feature Request
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