[
http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12371793 ]
Michael Yuan commented on JBIDE-702:
------------------------------------
Max,
To answer your question in email: Yes, there is always a java:/DefaultDS in JBoss AS. It
points to the bundled HSQL by default and the JDBC driver is already in the classpath.
However, the bundled HSQL is not accessible from outside of the AS. In fact, it is wiped
clean with each server re-start. So, there is little point running
"generate-entities" against it. Instead, the app will just map objects to DB
tables -- it is the dev mode people use very often. Perhaps we should just disable
generate-entities when the connection profile is not set. Thanks.
cheers
Michael
No connection specified, use defaultDs from jboss ?
---------------------------------------------------
Key: JBIDE-702
URL:
http://jira.jboss.com/jira/browse/JBIDE-702
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Reporter: Max Andersen
Suggestion from Yuan is that if users doesn't specify any connection preferences we
should use the defaultDs.
Issues I see with this is that then our project will no longer "control" the
datasource and what connection properties that is in it ?
when we add generate-entities it should pick up what connection data is relevant.
Which one will be the master ? today in seam-gen it is spread out and I don't like to
make that worse...
e.g. in seam-gen there is
1) the actual datasource in jboss
2) the connection properties in build.properties
3) the connection properties in hibernate.console properties
None of these are reliably possible to keep in sync afaik - neither manually or
automatically
--
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