Wrong JdbcServicesImpl configuration with problematic connection
by Dmitry Geraskov
Hey, guys,
I decided to write to this list to force this mistake to be fixed in Beta1.
There is a widely used class JdbcServicesImpl in hibernate4.
In the configure(Map configValues) it gets Connection object and does
the configuration. But what if the connection can't be established? It
do some steps in case of SQLException. But there are could be other
reasons of connection problem. For example missing
Driver(ClassNotFoundException), but this exception isn't handled. Why I
think it should be handled here?
Look at SchemaExport. It has an option "export" to database. And in case
this option is set to false we don't need the connection and Driver to
make it generate schema script successfully. But we still need some
configuration data from JdbcServices. And actually in hibernate 3 it
works nice without db connection. I guess it also would work in
hibernate4 too, but only if connection can't be established because of
SQLException, but not any other problem.
Dmitry Geraskov
12 years, 10 months
Change maven repository location in gradle
by Dmitry Geraskov
Hey, guys,
I tried to build hibernate source yesterday and I faced a problem with
gradle.
How can I let it the maven repository location (preferably without
changing common build.gradle)? (I don't use default
'user.home/.m2/repository)
Any ideas?
Dmitry Geraskov
12 years, 10 months
[BVAL]
by Emmanuel Bernard
Guys I'm considering releasing the specification document as a Git repository.
I am wondering if the document should share the same Git repo as beanvalidation-api or if these two should be kept separated. In other words, do these share the same release / tag cycle all the time?
WDYT?
Note that even if we agree that it should be one (of which I'm not convinced yet), I'd like to keep history from both and I'm not sure we can do that.
12 years, 10 months
remove old/deprecated cache spi?
by Strong Liu
the following spi were deprecated in release 3.3, should we remove them in this beta1 release?
org.hibernate.cache.spi.Cache
org.hibernate.cache.spi.CacheConcurrencyStrategy
org.hibernate.cache.spi.CacheProvider
org.hibernate.cache.spi.NonstrictReadWriteCache
org.hibernate.cache.spi.ReadOnlyCache
org.hibernate.cache.spi.ReadWriteCache
org.hibernate.cache.spi.TransactionalCache
-----------
Strong Liu <stliu(a)hibernate.org>
http://hibernate.org
http://github.com/stliu
12 years, 10 months
[HSEARCH] Problem with JBoss logging
by Davide D'Alto
Hi,
I'm working on the inclusion of JBoss Logging in HIbernate Search
(http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-675).
I've included in the pom this two dependencies:
...
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
<version>3.0.0.Beta5</version>
</dependency>
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging-processor</artifactId>
<version>1.0.0.Beta5</version>
</dependency>
...
But when I run maven test I have several exceptions during
compilation like these:
...
[ERROR] /home/davide/workspaces/contributions/hibernate-search/hibernate-search/src/main/java/org/hibernate/search/annotations/ClassBridge.java:[70,43]
incompatible types
[ERROR] found : org.hibernate.search.annotations.TermVector
[ERROR] required: org.hibernate.search.annotations.TermVector
[ERROR] /home/davide/workspaces/contributions/hibernate-search/hibernate-search/src/main/java/org/hibernate/search/annotations/ClassBridge.java:[76,24]
incompatible types
[ERROR] found : org.hibernate.search.annotations.Boost
[ERROR] required: org.hibernate.search.annotations.Boost
...
This is the project with the dependecies in the pom:
https://github.com/DavideD/hibernate-search/commits/HSEARCH-675
Do I need other dependencies?
Thanks,
Davide
12 years, 10 months
MetadataImpl ctor
by Steve Ebersole
Hardy, et al.
I have been working mostly on low-hanging fruit in this metamodel code
getting a handle on the code y'all wrote.
I wanted to discuss one proposal for change in particular. Currently
the ctor for MetadataImpl decides whether to process HBM or annotations
first and then processes all of that type completely, then moves on to
the other type.
What I wanted to propose instead was that we process the incoming data
more in chunks (for lack of better vocab). Basically the thought is
that there is a natural order to the things based on the nature of how
they relate to each other and their potential inter-dependence.
I think psuedo code works well here to illustrate what I propose.
Currently we do (assuming HBM as precendence):
MetadataImpl(...) {
processHibernateMappings(...);
processAnnotations(...);
}
processHibernateMappings(...) {
for ( allHibernateMappingFiles ) {
process( individualHibernateMapping );
}
}
I understand why we did it this way. Its exactly what the legacy code does.
More what I had in mind though is:
MetadataImpl(...) {
// auxiliary database objects are independent
processAuxiliaryDatabaseObjects(...);
// type definitions are independent
processTypeDefinitions(...);
// filters potentially depend on type definitions
processFilterDefinitions(...);
// id gen definitions potentially depend on type definitions
processIdentifierGenerators(...);
...
}
processAuxiliaryDatabaseObjects(...) {
// TODO : not sure "source precedence" means anything other than
// in regards to entity definitions
for ( allSources ) {
selectBinder(...).bindAuxiliaryDatabaseObjects(...);
}
}
There are a couple of reasons why it seems better to me to do it this
way. There are 2 bigs ones imo:
1) The fact that we know all the things we need to perform each
processXXX before we do it, which is a general theme in this start up
redesign. An example of where this is helpful is in type definitions
(on the hbm side at least). Currently users need to ensure, themselves,
that all type definitions are added before attempting to add entities,
id generators, etc that try to reference those types. The proposed
approach would allow the code to be more user helpful because it would
do that for them.
2) Partially a consequence of the first, we can validate as we go.
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
12 years, 10 months
R: Re: compile hibernate4 alpha3 using java5
by gioacchinomauri＠libero.it
Thanks,
Is it written somewhere in the site or in some blog post ?
----Messaggio originale----
Da: steve(a)hibernate.org
Data: 01/06/2011 23.50
A: "gioacchinomauri(a)libero.it"<gioacchinomauri(a)libero.it>
Cc: <hibernate-dev(a)lists.jboss.org>
Ogg: Re: [hibernate-dev] compile hibernate4 alpha3 using java5
Hibernate 4 requires Java 6
On Jun 1, 2011 4:11 PM, "gioacchinomauri(a)libero.it" <gioacchinomauri(a)libero.it> wrote:
> Hi there,
>
> is it possible to compile hibernate4 using java5 ? I've seen there is some
> errors on alpha3 but i don't know if java5 should be supported or not.
>
> To be more specific i got errors on "org.hibernate.build.gradle.inject.
> InjectionAction" because it uses an "@Override" annotation against a method
> declared in an interface ("org.gradle.api.Action") which is not allowed in
> java5 (see here: http://dertompson.com/2008/01/25/override-specification-
> changes-in-java-6/).
>
> I posted a similar message on hibernate users forum but i think it's the wrong
> place, so sorry for the double question.
>
>
> Thanks
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
12 years, 10 months
