[JBoss JIRA] Created: (JBDS-876) Reverse engineering entities in a Sema project ties you to one database
11:30 a.m.
Reverse engineering entities in a Sema project ties you to one database
-----------------------------------------------------------------------
Key: JBDS-876
URL: https://jira.jboss.org/jira/browse/JBDS-876
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 2.1.0
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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
11:31 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-876) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBDS-876?page=com.atlassian.jira.plugi...
]
Shaun Appleton updated JBDS-876:
--------------------------------
Summary: Reverse engineering entities in a Seam project ties you to one database
(was: Reverse engineering entities in a Sema project ties you to one database)
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBDS-876
URL: https://jira.jboss.org/jira/browse/JBDS-876
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 2.1.0
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:17 p.m.
New subject: [JBoss JIRA] Moved: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen moved JBDS-876 to JBIDE-4974:
-------------------------------------------------
Project: Tools (JBoss Tools) (was: JBoss Developer Studio)
Key: JBIDE-4974 (was: JBDS-876)
Affects Version/s: 3.1.0.M3
(was: 2.1.0)
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:23 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4974:
---------------------------------------
Fix Version/s: 3.1.0.M4
Assignee: Alexey Kazakov
Priority: Minor (was: Major)
Shaun, I moved this to JBoss Tools since there is nothing JBDS specific about this issue.
To have hibernate-console.properties changes picked up on a prebuilt console
configuration, click the rebuild on hibernate console configuration.
That said, I agree the UI is not behaving correctly here.
Alexey, is the database connection actually used for anything beyond on the initial wizard
creation ?
If no, then shouldn't we simply remove it ?
If yes, what is it used for ?
(note, we can fix this by aligning the selected DTP connection with what JPA/Hibernate
tools knows about removing the need for custom connection settings in hibernate tools
properties)
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Alexey Kazakov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Alexey Kazakov commented on JBIDE-4974:
---------------------------------------
> Alexey, is the database connection actually used for anything
beyond on the initial wizard creation ?
No. It's used only in Seam Facet
Install Delegate. I'll remove it from Seam settings page.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Alexey Kazakov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:54 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Alexey Kazakov reassigned JBIDE-4974:
-------------------------------------
Assignee: Dmitry Geraskov (was: Alexey Kazakov)
I've removed this settings from Seam Settings page.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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
7:11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4974:
----------------------------------------
I don't understand the problem.
1. You created seam project with associated connection profile and console configuration.
2. Seam Generate Entities wizard generated entities for you based on the selected console
configuration.
(dbl click on the console configuration is console configuration tree shows you [Hibernate
Configured Connection] in database connection field?)
3. You changed assosciated connection profile
step 2 is not working now?
Seam's Connection Profile doesn't influence on the connection setting in the
wizard. The connection based on the selected Console Configuration.
So I think I misunderstood something...
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Shaun Appleton commented on JBIDE-4974:
---------------------------------------
Dmitry,
I think you are highlighting the problem exactly.
Seam's Connection Profile doesn't influence on the connection
setting in the wizard.
At step 3 I change the Connection profile in the Seam Settings dialog - expecting the
project to use my new setting.
But, as you say, Seam's Connection Profile has no influence on the connection setting
used to generate the hibernate entities.
So I can change my connection in Seam Settings dialog, expecting it to be used throughout
the project, but it has no affect - so why is it there?
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4974:
----------------------------------------
Missprint in 'styp'. Read as style.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4974:
----------------------------------------
The entities are generated based on the console configuration. The console configuration
connection based on the [Hibernate Configured Connection] (means that it configured by the
hibernate.properties file, hibernate.cfg.xml or persistence.xml - this depends on the
selected styp, but hibernate.properties is default for you). So it doesn't depend on
the connection profile set for the project.
There is not bug here.
You could see the connected db in the Hibernate Configuration view if you open your
console configuration.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Alexey Kazakov commented on JBIDE-4974:
---------------------------------------
Shaun, I have removed this unused settings from Seam Settings page at all.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.M4
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:41 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4974:
---------------------------------
Fix Version/s: 3.1.0.CR1
(was: 3.1.0.M4)
bulk move from M4 to CR1
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.CR1
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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:03 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Dmitry Geraskov resolved JBIDE-4974.
------------------------------------
Resolution: Done
Double click on console configuration and change connection profile.
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.CR1
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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
6:18 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4974:
---------------------------------
Component/s: Hibernate
Seam
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate, Seam
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.CR1
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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
7:55 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-4974) Reverse engineering entities in a Seam project ties you to one database
[
https://jira.jboss.org/jira/browse/JBIDE-4974?page=com.atlassian.jira.plu...
]
Dmitry Geraskov closed JBIDE-4974.
----------------------------------
Reverse engineering entities in a Seam project ties you to one
database
-----------------------------------------------------------------------
Key: JBIDE-4974
URL: https://jira.jboss.org/jira/browse/JBIDE-4974
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate, Seam
Affects Versions: 3.1.0.M3
Environment: JBDS linux and Windows
Reporter: Shaun Appleton
Assignee: Dmitry Geraskov
Priority: Minor
Fix For: 3.1.0.CR1
When I reverse engineer entities from a database you cannot change the database and
reverse engineer different entities.
It would appear reverse engineering entities ties you to one database
To replicate:
Create a Seam project and generate entities as described in
http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i...
section 3.5.1
Then select the project and change the database to a different running database by
changing the database connection profile in the seam settings. Verify the latest database
can be pinged.
Select the project and select File new generate entities and follow the dialogs through
until you get to the Generate Entities Dialog. A <couldn't connect to database>
error is shown in the database schema window.
i.e. the new database connection is not picked up.
It appears that when the database is changed in the Seam Settings connection profile the
hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer
the database is tried the old connection settings are used even though they have recently
been changed.
If this is a technical limitation then there should be some warning in the docs that
changing the database after generating the entities won't work. Plus have the
connections profile bit greyed-out so it can't be altered.
But ideally the hibernate-console.properties file should be synchronised with the Seam
Settings connection profile.
I tried deleting the hibernate-console.properties to try and force it to create a new
hibernate-console.properties file with the correct settings but file but that didn't
work either.
--
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
5925
days inactive
6038
days old
jbosstools-issues@lists.jboss.org
14 comments
5 participants
participants (5)
-
Alexey Kazakov (JIRA) -
Denis Golovin (JIRA)
-
Dmitry Geraskov (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Shaun Appleton (JIRA)