ehlo.
it would really nice if there was an option to avoid validation,
I usually check xml validity with the IDE anyway (you don't
need to check it again and again when you're in production, and
morevoer a reduced startup time means more productive debugging ;-)
Good point. Personally, I've alre
ehlo.
My take on env vars has less to do with make and more of my school of
thought keeping dependency binaries out of CVS. I view CVS as a
_source_ control medium, not a build repository. Env vars are the
logical choice for making clean builds when engaging in that school of
thought.
And
ehlo.
Not that i think you are not aware of it, but I think i can for sure
state that the Gavin King writing that blog is not Hibernate Gavin King
;)
... but does MS know that?
dozen
---
This SF.net email is sponsored by: VM Ware
With VMw
ehlo.
The patch allowing to choose the access method and/or order is
submitted to JIRA. The URL is:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-270
Resulting patch has following external options:
1. hibernate.access.order in hibernate.conf
Possib
ehlo.
Just one wish: I like the search order idea, it makes it easier to use.
But we should also have the possibility to specify the strategy very
explicitly for each class and even property.
Yes, I agreed.
But for now I going to develop a more simple
solution (and I believe it would sati
ehlo.
I'm very openminded this patch. However, you need to submit it
(a) in diff format, so I can see exactly what changed ... and use patch to
patch the curent code!
(b) upload it to JIRA, not post it to the list
Fine. I'll submit the patch this weekend.
dozen
P.S. ... JIRA? what is JIRA? I h
ehlo.
Background:
As it is known, Hibernate uses accessors (getters/setters) to
access object properties. This is noted as a RIGHT THING
in documentation, since it raises incapsulation. That's right,
but I have a few real-world examples that show that direct field
access c
