-
Bug
-
Resolution: Done
-
Major
-
3.3.1.Final
-
None
-
Using forge from a windows command line I can successfully execute
jpa-generate-entities-from-tables --database-tables * --target-package ca.gerrymatte.health.model --hibernate-dialect org.hibernate.dialect.MySQL5InnoDBDialect --driver-class com.mysql.jdbc.Driver --driver-location D:/s/jclasses/drivers/mysql.jar --user-name root --user-password secret --jdbc-url jdbc:mysql://127.0.0.1/health ;
Using forge 3.3.1.Final included with Jboss Developer Studio 10.1.0.Final the dialog box that specifies which driver to use defaults to the mysql fabric driver. When I select the normal mysql driver and test the connection all is ok.
However when I click next the resulting screen shows the fabric driver is still being used and of course the connection fails to work. See the attached screen images.
Using forge from a windows command line I can successfully execute jpa-generate-entities-from-tables --database-tables * --target- package ca.gerrymatte.health.model --hibernate-dialect org.hibernate.dialect.MySQL5InnoDBDialect --driver- class com.mysql.jdbc.Driver --driver-location D:/s/jclasses/drivers/mysql.jar --user-name root --user-password secret --jdbc-url jdbc:mysql: //127.0.0.1/health ; Using forge 3.3.1.Final included with Jboss Developer Studio 10.1.0.Final the dialog box that specifies which driver to use defaults to the mysql fabric driver. When I select the normal mysql driver and test the connection all is ok. However when I click next the resulting screen shows the fabric driver is still being used and of course the connection fails to work. See the attached screen images.