3:57 a.m.
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
8:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ 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
12:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12371954 ]
Denis Golovin commented on JBIDE-702:
-------------------------------------
Seam-gen never puts the connections properties in build.properties file, there is only
jboss.home in it.
Seam-gen->Generate entities always use default parameters
http://jira.jboss.org/jira/browse/JBIDE-708
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
2:51 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12371968 ]
Max Andersen commented on JBIDE-702:
------------------------------------
what does seam-gen has to do with this ?
seam-gen is broken when it comes to multiple projects and our seam wizard doesn't
handle the profile concept in seamgen....
seam-gen afaik picks up the settings from the build.properties in seam it self (which is
bad imo)
but again; i don't understand what this issue has to do with using defaultDs when no
connection are specificed?
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
4:30 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12374486 ]
Michael Yuan commented on JBIDE-702:
------------------------------------
I think we can do one of the following:
1. If the user does not select a connection profile when she generates the project, we
will generate a default DS file for her project. The generated DS points to the DefaultDS
in JBoss (the same DS Seam-gen produces).
2. If the user needs to run generate-entities later, we will tell her that
generate-entities cannot be run against the default embedded DS. She will need to select a
real connection profile for her project before he can generate entities.
What do you think?
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
4:44 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12374488 ]
Michael Yuan commented on JBIDE-702:
------------------------------------
In my previous comment, I meant to say that the default DS generated for #1 will NOT be
under the control of RHDS. That is why #2 will detect an empty connection profile and ask
the user to create one. The newly created profile will override the default one.
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
2:22 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=comments#action_12376331 ]
Max Andersen commented on JBIDE-702:
------------------------------------
this would require changes in seam-gen to work since it is seam-gen that controls the name
of used datasource ;(
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
5:49 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=all ]
Max Andersen updated JBIDE-702:
-------------------------------
Fix Version/s: LATER
move to later - seam-gen expects datasource to be same as project name.
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
Fix For: LATER
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
5:51 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=all ]
Max Andersen updated JBIDE-702:
-------------------------------
Component/s: seam-gen
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, seam-gen
Reporter: Max Andersen
Fix For: LATER
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
9:04 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-702) No connection specified, use defaultDs from jboss ?
[ http://jira.jboss.com/jira/browse/JBIDE-702?page=all ]
Max Andersen resolved JBIDE-702.
--------------------------------
Fix Version/s: 2.0.0.CR1
(was: LATER)
Resolution: Partially Completed
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, seam-gen
Reporter: Max Andersen
Fix For: 2.0.0.CR1
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
6736
days inactive
6815
days old
jbosstools-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Denis Golovin (JIRA) -
Max Andersen (JIRA)
-
Michael Yuan (JIRA)