On Tue, 27 Feb 2007 04:14:12 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
I don't think it should be applied to all properties, but the one
referred are worth it.
It's more or less all those that refers to a class that hibernate should
try and instantiate.
Others should be ok, at least since they have a value that you can
specifically set without hibernate
"breaking" during startup.
/max
On 26 févr. 07, at 18:21, Max Rydahl Andersen wrote:
Hi,
I've bumped into an issue with trying to override settings/properties
in tools too allow users to use
their existing config minus the appserver specific settigns (e.g. tx
manager lookup).
I've created http://opensource.atlassian.com/projects/hibernate/
browse/HHH-2452 and would like to hear
if someone can see any problem in ignoring empty string properties
(instead of as today try and do a class.forName(""))
----
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
