[JBoss JIRA] Created: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step
2:58 p.m.
HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root of
class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the same
selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed outside
CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) - To
load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
4:47 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Dmitry Geraskov reassigned JBIDE-4918:
--------------------------------------
Assignee: Dmitry Geraskov
HIbernate Configuration File (cfg.xml) New Wizard should walidate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
4:50 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should walidate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Dmitry Geraskov updated JBIDE-4918:
-----------------------------------
Component/s: Hibernate
Fix Version/s: LATER
HIbernate Configuration File (cfg.xml) New Wizard should walidate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
8:54 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk updated JBIDE-4918:
----------------------------------------
Summary: HIbernate Configuration File (cfg.xml) New Wizard should validate file name
on first step (was: HIbernate Configuration File (cfg.xml) New Wizard should walidate
file name on first step)
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
9 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-4918:
---------------------------------------------
just about 4 - the empty cfg.xml is valid.
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
1:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-4918:
--------------------------------------
sure it is, but if there is hibernate.properties file with properties. Have you ever tried
to run hibernate enabled projects without configuration? It should throw exceptions,
shouldn't it? I'm just curious.
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
5:20 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/jira/browse/JBIDE-4918?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4918:
--------------------------------------------
about 4, you can also just point to a datasource or give Hibernate a connection then those
settings aren't relevant. So the warning needs to be worded properly so they don't
think they *must* fill it in.
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/jira/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
2:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Dmitry Geraskov commented on JBIDE-4918:
----------------------------------------
About point 4.
Really the configuration is optional as we have some other ways to configure database
connection.
The the warning messages could disturb juniour user instead of help him.
Also we have rather informative exception messages which will help on case of problems.
So the point 4 is rejected :)
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
2:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Dmitry Geraskov commented on JBIDE-4918:
----------------------------------------
About point1:
if any other folder outside source folder is selected in Package
Explorer, wizard should select first source folder available in project
I think this
is true only if project selected. If not source folder(or it's child) selected - it
should be the same in the wizard.
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: LATER
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
2:39 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Dmitry Geraskov resolved JBIDE-4918.
------------------------------------
Fix Version/s: 3.2.next
(was: LATER)
Resolution: Done
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: 3.2.next
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
2:39 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Dmitry Geraskov reassigned JBIDE-4918:
--------------------------------------
Assignee: Jiri Peterka (was: Dmitry Geraskov)
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Jiri Peterka
Fix For: 3.2.next
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
5:30 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-4918:
---------------------------------------
Fix Version/s: 3.2.0.M1
(was: 3.2.x)
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: 3.2.0.M1
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
6:24 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4918) HIbernate Configuration File (cfg.xml) New Wizard should validate file name on first step
[
https://jira.jboss.org/browse/JBIDE-4918?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen resolved JBIDE-4918.
----------------------------------------
Resolution: Done
HIbernate Configuration File (cfg.xml) New Wizard should validate
file name on first step
-----------------------------------------------------------------------------------------
Key: JBIDE-4918
URL: https://jira.jboss.org/browse/JBIDE-4918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: 3.2.0.M1
Several notes about hibernate.cfg.xml from Hibermate documentation:
1. hibernate runtime looking for configuration file 'hibernate.cfg.xml' in root
of class path, so user place 'hibernate.cfg.xml' to 'default package' i.e.
into source folder it will in case of
SessionFactory sf = new Configuration().configure().buildSessionFactory();
additional info is here
(http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-con...)
2. Hibernate configuration file can have any name and placed anywhere in CLASSPATH. In
this case it can be loaded by code
SessionFactory sf = new
Configuration().configure(${path-to-file-in-classpath}).buildSessionFactory();
Considering that, withatd should:
1. Provide default values based on current selection in Package Explorer
- if package or source folder is selected in Package explorer wizard should have the
same selection in wizard
- if any other folder outside source folder is selected in Package Explorer, wizard
should select first source folder available in project
2. Now validation of selected file name take place on second step, that should be done on
first one.
3. Validation should be not so strict but more informative:
- File extension must be .xml (error) - File extension should be .xml
- If location for file is not within src folder (warning) - Configuration placed
outside CLASSPATH will not be available at run-time
- If location is src root and file name is 'hibernate.cfg.xml' (no errors or
warnings) - This wizard allows you to create a configuration for Hibernate Console
- If location is src root and file name is not 'hibernate.cfg.xml' (warning) -
To load Configuration from '${filename}' you'll have to pass file name to
Configuration.configure() method
- If location is within src root but not src root and file name is not
'hibernate.cfg.xml' (warning) - To load Configuration from '${filename}'
you'll have to provide path file to Configuration.configure() method (not sure if that
true)
(Messages need to be discussed)
4. Second Step validation should warn that DB Dialect, DB Driver Class and URL should be
entered
--
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
5783
days inactive
6052
days old
jbosstools-issues@lists.jboss.org
12 comments
4 participants
participants (4)
-
Denis Golovin (JIRA) -
Dmitry Geraskov (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Vitali Yemialyanchyk (JIRA)