[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-874?page=co...
]
Mark Spritzler commented on HBX-874:
------------------------------------
Well, I didn't say I have all the answers. :)
What about a kind of proxy object? I know in IntelliJ, I can create a Connection and do
Database stuff, but you probably already do that now.
But if we had a proxy object that would stand in as the InitialContext, and instead of
having an actual Registry, it returned another proxy for a DataSource, that was just a
wrapper around a JDBC Connection, so it would appear as if it was a true DataSource, but
just wrapped and hidden away nicely. Again this is my fantasyland here, not sure if it is
practical or would actually work.
Ability to add configuration information for database when config
file points to a DataSource
---------------------------------------------------------------------------------------------
Key: HBX-874
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-874
Project: Hibernate Tools
Type: Improvement
Components: consoleconfiguration
Versions: 3.2beta9
Environment: Hibernate 3.2, Postgres 8.2.3
Reporter: Mark Spritzler
When setting up the Hibernate Console to use a hibernate.cfg.xml or point to a
persistence unit, if either configurations point to a DataSource JNDI name, then the
console cannot create a SessionFactory/EntityManagerFactory. There should be a way to put
the database connectivity information on the configuration for the console for just these
cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira