[hibernate-dev] Hibernate Search documentation build problem
Hi all, I have problem with the documentation build of Hibernate Search : [INFO] --- maven-jdocbook-plugin:2.3.5:generate (default-generate) @ hibernate-search-documentation --- 15 [main] INFO org.jboss.jdocbook.profile.ProfilerImpl - applying DocBook profiling [C:\Dev\hibernate-search\hibernate-s earch-documentation\target\docbook\work\profile\en-US\master.xml] Error on line 27 column 19 of file:/C:/Dev/hibernate-search/hibernate-search-documentation/src/main/docbook/en-US/master .xml: Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence. On got it either on master or 4.1.0.Fiinal tag Does this ring a bell to someone ? Thanks Niko ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Running Gradle build against an Infinispan version passed as command line parameter?
Hi, I'd like to have a CI job that tests Hibernate Infinispan integration against the latest Infinispan 5.1. So, I'm wondering if there's a way in which you can define the Infinispan version to use via command line. Something like: ./gradlew clean build -DinfinispanVersion=5.1.7-SNAPSHOT The above command does not currently work, but wondered if there's a way to achieve something like that? Cheers, -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Running Gradle build against an Infinispan version passed as command line parameter?
That doesn't seem to work. It's still using the version defined in the configuration file. On Aug 23, 2012, at 3:08 PM, Steve Ebersole wrote: > Try -P instead of -D. Not sure it will work, but -P is the means to set > project variables. > > On Thu 23 Aug 2012 08:02:28 AM CDT, Galder Zamarreño wrote: >> Hi, >> >> I'd like to have a CI job that tests Hibernate Infinispan integration >> against the latest Infinispan 5.1. >> >> So, I'm wondering if there's a way in which you can define the Infinispan >> version to use via command line. Something like: >> >> ./gradlew clean build -DinfinispanVersion=5.1.7-SNAPSHOT >> >> The above command does not currently work, but wondered if there's a way to >> achieve something like that? >> >> Cheers, >> -- >> Galder Zamarreño >> Sr. Software Engineer >> Infinispan, JBoss Cache >> >> >> ___ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] SessionFactory building, 5.0-style
The initial design I had for building a SessionFactory using the new metamodel was 3 steps: 1) build ServiceRegistry 2) build Metadata 3) build SessionFactory using both ServiceRegistry and Metadata This changed a little as actually implemented in the metamodel branch: 1) build "boot strap" service registry 2) build basic service registry 3) build MetadataSources 4) build Metadata 5) build SessionFactory using both basic service registry and Metadata I would like to change this slightly based on JPA 2.1 work and integrating that with containers (mainly through planning with Scott for JBoss AS). Essentially Scott and I made a change proposal to JPA EG for how managed EMF bootstrapping happens to better account for stuff in the container's environment not being available until certain times. It is a typical "hole in the interaction of specs" deal. Long story short, we want to make boot strapping of an EMF into 2 distinct phases. Whether or not that gets accepted/approved, we will implement this approach for Hibernate EMF bootstrapping and JBoss AS will leverage it. The 2 phases are meant to account for container resources not being available or the need to delay classloading. The changes I propose would just be ordering: -- phase 1 -- 1) build "boot strap" service registry 2) build MetadataSources -- phase 2 -- 3) build basic service registry 4) build Metadata 5) build SessionFactory using both basic service registry and Metadata -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Running Gradle build against an Infinispan version passed as command line parameter?
better to use "sed" to change the version number defined in the libraries.gradle On Aug 23, 2012, at 9:15 PM, Galder Zamarreño wrote: > That doesn't seem to work. It's still using the version defined in the > configuration file. > > On Aug 23, 2012, at 3:08 PM, Steve Ebersole wrote: > >> Try -P instead of -D. Not sure it will work, but -P is the means to set >> project variables. >> >> On Thu 23 Aug 2012 08:02:28 AM CDT, Galder Zamarreño wrote: >>> Hi, >>> >>> I'd like to have a CI job that tests Hibernate Infinispan integration >>> against the latest Infinispan 5.1. >>> >>> So, I'm wondering if there's a way in which you can define the Infinispan >>> version to use via command line. Something like: >>> >>> ./gradlew clean build -DinfinispanVersion=5.1.7-SNAPSHOT >>> >>> The above command does not currently work, but wondered if there's a way to >>> achieve something like that? >>> >>> Cheers, >>> -- >>> Galder Zamarreño >>> Sr. Software Engineer >>> Infinispan, JBoss Cache >>> >>> >>> ___ >>> hibernate-dev mailing list >>> hibernate-dev@lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > > > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev - Best Regards, Strong Liu http://about.me/stliu/bio ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search documentation build problem
I have been able to reproduce that on OpenJDK 7 and Oracle's JDK 7. JDK 6 works fine for me. Obviously JDK 7 reads UTF-8 differently but I don't know how to fix that on our end. Anyone knows? On 23 août 2012, at 12:30, Nicolas Helleringer wrote: > Hi all, > > I have problem with the documentation build of Hibernate Search : > > [INFO] --- maven-jdocbook-plugin:2.3.5:generate (default-generate) @ > hibernate-search-documentation --- > 15 [main] INFO org.jboss.jdocbook.profile.ProfilerImpl - applying DocBook > profiling [C:\Dev\hibernate-search\hibernate-s > earch-documentation\target\docbook\work\profile\en-US\master.xml] > Error on line 27 column 19 of > file:/C:/Dev/hibernate-search/hibernate-search-documentation/src/main/docbook/en-US/master > .xml: > Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence. > > On got it either on master or 4.1.0.Fiinal tag > > Does this ring a bell to someone ? > > Thanks > > Niko > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search documentation build problem
We had similar issues before. Probably a little iconv will help :-) Is there a Jira issue? I can have a look. --Hardy On 23 Jan 2012, at 5:03 PM, Emmanuel Bernard wrote: > I have been able to reproduce that on OpenJDK 7 and Oracle's JDK 7. > JDK 6 works fine for me. > > Obviously JDK 7 reads UTF-8 differently but I don't know how to fix that on > our end. Anyone knows? > > On 23 août 2012, at 12:30, Nicolas Helleringer wrote: > >> Hi all, >> >> I have problem with the documentation build of Hibernate Search : >> >> [INFO] --- maven-jdocbook-plugin:2.3.5:generate (default-generate) @ >> hibernate-search-documentation --- >> 15 [main] INFO org.jboss.jdocbook.profile.ProfilerImpl - applying DocBook >> profiling [C:\Dev\hibernate-search\hibernate-s >> earch-documentation\target\docbook\work\profile\en-US\master.xml] >> Error on line 27 column 19 of >> file:/C:/Dev/hibernate-search/hibernate-search-documentation/src/main/docbook/en-US/master >> .xml: >> Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence. >> >> On got it either on master or 4.1.0.Fiinal tag >> >> Does this ring a bell to someone ? >> >> Thanks >> >> Niko >> ___ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] JPA callback listeners and CDI
On 20 août 2012, at 11:41, Hardy Ferentschik wrote: > > On 18 Jan 2012, at 7:30 PM, Steve Ebersole wrote: > >> 2) The way this is currently implemented, using JPA now has a dependency >> on the CDI API being available on the classpath. We need to decide if >> that is unreasonable. The other option is to handle it like we do for >> BeanValidation and use messy reflection to isolate the dependency. > > I am not a big fan of the hard dependency to CDI. If there is no other option > I think we should > go for the reflection approach. I don't think it is too messy. Pretty > straight forward imo. I would also mimic what we did for the integration with Bean Validation. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync master out to metamodel?
okay, I have ( finally ) merged master onto metamodel, now time to rebase your changes :D On Aug 23, 2012, at 4:13 AM, Steve Ebersole wrote: > Ok, this is getting too frustrating. Strong I need you to do this > merge when you get back online. I threw away my attempts. > > > On Wed 22 Aug 2012 02:27:54 PM CDT, Steve Ebersole wrote: >> Ok, Strong this one I cannot get past: >> >> * What went wrong: >> Execution failed for task ':hibernate-core:generateMainLoggingClasses'. >>> Compilation failed; see the compiler error output for details. >> >> The compilation failures include all forms of not being able to find >> classes. Some of them are our classes: >> >> /home/steve/projects/hibernate/4/hibernate-orm/hibernate-core/src/main/java/org/hibernate/engine/jdbc/internal/JdbcServicesImpl.java:190: >> error: cannot find symbol >>private final SQLStateType sqlStateType; >> ^ >> symbol: class SQLStateType >> location: class ExtractedDatabaseMetaDataImpl >> >> >> Some of them straight-up JDK classes: >> >> /home/steve/projects/hibernate/4/hibernate-orm/hibernate-core/src/main/java/org/hibernate/engine/jdbc/internal/JdbcServicesImpl.java:194: >> error: cannot find symbol >>private final LinkedHashSet typeInfoSet; >> ^ >> symbol: class LinkedHashSet >> location: class ExtractedDatabaseMetaDataImpl >> /home/steve/projects/hibernate/4/hibernate-orm/hibernate-core/src/main/java/org/hibernate/engine/jdbc/internal/JdbcServicesImpl.java:204: >> error: cannot find symbol >>Set extraKeywords, >>^ >> symbol: class Set >> location: class ExtractedDatabaseMetaDataImpl >> >> Something is seriously wrong here... >> >> On Wed 22 Aug 2012 02:19:24 PM CDT, Steve Ebersole wrote: >>> Ugh. >>> >>> Running into all kinds of Gradle problems due changes Strong made to >>> master. >>> >>> >>> >>> On 08/22/2012 01:07 PM, Hardy Ferentschik wrote: Go ahead. I should be able to rebase my stuff easily. --hardy On 22 Aug 2012, at 18:57, Steve Ebersole wrote: > Any objections to me syncing master branch out to metamodel later > today? > > -- > st...@hibernate.org > http://hibernate.org > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev >>> >> >> -- >> st...@hibernate.org >> http://hibernate.org > > -- > st...@hibernate.org > http://hibernate.org > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev - Best Regards, Strong Liu http://about.me/stliu/bio ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] JPA callback listeners and CDI
Emmanuel, What do you think about the idea outlined before of having an EntityListenerFactory in the JPA spec similar to BV's ConstraintValidatorFactory? I think the situation in JPA is very similar to BV and feel it would make sense to solve the problem similarly in both cases. This would also avoid a direct dependency from JPA to CDI altogether (implementation-wise). The JPA spec would just require the EE container to plug in a CDI-aware factory, similar to what we've been discussing for BV constraint validators. WDYT? --Gunnar Am 23.08.2012 17:11 schrieb "Emmanuel Bernard" : ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Eclipse-specific execution filters in POMs
I know a lot of you don't use Eclipse, but... Its Maven plugin (M2E) does not have connectors for several of Hibernate 3.3's lifecycle mappings. The only way to get the IDE to ignore them is to add the following (as an example). What are your opinions of having IDE-specific areas, like this, in the parent POM? org.eclipse.m2e lifecycle-mapping 1.0.0 org.jboss.maven.plugins maven-injection-plugin [1.0.2,) bytecode ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] JPA callback listeners and CDI
Looks good in theory but I see two hindrance - JPA and BV already define a way to interact with each other and the CDI integration has been mirrored consistency is good in this case - we could convince the JPA EG but that will require time an energy on something that already works ok If we end up with spare time, we could try. On 23 août 2012, at 18:10, Gunnar Morling wrote: > Emmanuel, > > What do you think about the idea outlined before of having an > EntityListenerFactory in the JPA spec similar to BV's > ConstraintValidatorFactory? > > I think the situation in JPA is very similar to BV and feel it would make > sense to solve the problem similarly in both cases. This would also avoid a > direct dependency from JPA to CDI altogether (implementation-wise). The JPA > spec would just require the EE container to plug in a CDI-aware factory, > similar to what we've been discussing for BV constraint validators. > > WDYT? > > --Gunnar > > Am 23.08.2012 17:11 schrieb "Emmanuel Bernard" : ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search documentation build problem
Nicolas, we have opened https://hibernate.onjira.com/browse/HSEARCH-1183 if you could run mvn -v and paste your output in the issue that would help. Emmanuel On 23 août 2012, at 12:30, Nicolas Helleringer wrote: > Hi all, > > I have problem with the documentation build of Hibernate Search : > > [INFO] --- maven-jdocbook-plugin:2.3.5:generate (default-generate) @ > hibernate-search-documentation --- > 15 [main] INFO org.jboss.jdocbook.profile.ProfilerImpl - applying DocBook > profiling [C:\Dev\hibernate-search\hibernate-s > earch-documentation\target\docbook\work\profile\en-US\master.xml] > Error on line 27 column 19 of > file:/C:/Dev/hibernate-search/hibernate-search-documentation/src/main/docbook/en-US/master > .xml: > Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence. > > On got it either on master or 4.1.0.Fiinal tag > > Does this ring a bell to someone ? > > Thanks > > Niko > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Concept of "service availability"
Ok, going to start working this up on master tomorrow. We will just
tackle the "going away" problem if/when it actually arises.
On Tue 21 Aug 2012 05:55:31 PM CDT, Steve Ebersole wrote:
> Everyone else ok with this idea?
>
> On Tue 21 Aug 2012 08:27:25 AM CDT, Steve Ebersole wrote:
>> Not so concerned about shutdown situations.
>>
>> More, imagine a custom ConnectionProvider implementation provided by
>> user. And the use case of upgrading that implementation "in flight".
>> I think thats the OSGi use case. And not so sure Hibernate should be
>> implementing this self healing. I guess it depends how deeply we want
>> to support the OSGi model above and beyond JSE/JEE
>>
>> Obviously a used ConnectionProvider just going away is going to render
>> the SessionFactory using it broken.
>>
>> On Tue 21 Aug 2012 08:22:11 AM CDT, Scott Marlow wrote:
>>> On 08/20/2012 11:19 PM, Steve Ebersole wrote:
This ties together a few different discussions that have been going on
simultaneously on the mailing list that I think are all related.
Right now to configure certain services (select one impl over another)
users generally give the FQN for that impl Class. For example to use
C3P0 connection pooling users would say:
hibernate.connection.provider_class =
org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
We have discussed why this is bad even before any of the OSGi
discussions and the solution we wanted to shoot for was that of naming
"selectors" such that the user would instead say:
hibernate.connection.provider_class = c3p0
And "c3p0" here would be interpreted to mean "instantiate and
configure
the
org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
Class". But that still means a limited set of short name values *and*
still gives us a problem (iiuc) under OSGi due to visibility.
So what I propose instead is a way for service implementors to be
registered under a short name via discovery. The main piece to
this is
the "registry" (which is also a service under the
BootstrapServiceRegistry):
interface AvailableServiceRegistry extends Service {
public Class
findAvailableServiceImplementor(Class serviceRole, String
selector);
}
class AvailableServiceRegistryImpl
implements AvailableServiceRegistry,
ServiceRegistryAwareService {
private Map> availableImplementors =
...;
@Override
public Class
findAvailableServiceImplementor(Class serviceRole, String
selector) {
// purposely simplistic :)
return availableImplementors.get( serviceRole ).get(
selector );
}
@Override
public void injectServices(ServiceRegistryImplementor
serviceRegistry) {
final LinkedHashSet
notifiers =
serviceRegistry.getService( ClassLoaderService.class
).loadJavaServices(
ServiceAvailabililtyNotifier.class );
for ( ServiceAvailabililtyNotifier notifier : notifiers ) {
for ( ServiceAvailabililty availability :
notifier.getAvailabilities() ) {
// again, purposely simplistic
Map serviceImplementors =
availableImplementors.get( availability.getRole() );
serviceImplementors.put(
availability.getSelector(),
availability.getImplementor()
);
}
}
}
}
Outstanding question... Especially in OSGi, where service bundles
can be
added/removed, how do we best account for cleaning up no-longer valid
references (even more importantly perhaps, what the hell does it
mean to
Hibernate when a ConnectionProvider implementation, for example,
that is
in use gets taken away?!?). Perhaps this is just where an
OSGi-specific
Hibernate ServiceRegistry implementation would come into play.
>>>
>>> Adding Jesper as we were talking about how to handle "quiescence
>>> shutdown" at the AS level, which sounds related. Once we take the
>>> ConnectionProvider away, I would expect the Hibernate
>>> session(s)/session factory to be broken. If/when the
>>> ConnectionProvider comes back, Hibernate would need to re-establish
>>> it. I'm thinking that we need a neutral (autonomic) API/SPI for
>>> attempting to re-establish the ConnectionProvider.
>>>
>>> For the most part, a "quiescence shutdown" of the AS, would mean
>>> keeping the ConnetionProvider alive until the end (of the planned
>>> shutdown). I'm thinking that being able to re-establish the
>>> ConnectionProvider would still be useful (for AS "quiescence
>>> shutdown"), especially if something goes wrong du
Re: [hibernate-dev] org.hibernate.jpa.test.packaging.PackagingTestCase
Ok, so it does do some filtering. However...
task copyBundleResources (type: Copy) {
ext.bundlesTargetDir = file( "${buildDir}/bundles" )
from file('src/test/bundles')
into bundlesTargetDir
filter(ReplaceTokens, tokens: [
buildDirName: buildDir.absolutePath,
'db.dialect': 'org.hibernate.dialect.H2Dialect',
'jdbc.driver': 'org.h2.Driver',
'jdbc.user': 'sa',
'jdbc.pass': '',
'jdbc.url': 'jdbc:h2:mem:db1;DB_CLOSE_DELAY=-1;MVCC=TRUE',
]);
doFirst {
bundlesTargetDir.mkdirs()
}
}
It always filters to a static set of values. Meaning, those values
could be put directly in the resource(s) being filtered. Or even
handled via ${propName} handling.
On Thu 16 Aug 2012 09:12:53 AM CDT, Steve Ebersole wrote:
> Not in the one I looked at. But good point, I'll look at the others.
>
> On Thu 16 Aug 2012 03:18:30 AM CDT, Hardy Ferentschik wrote:
>> Does it not do some filtering as well when the copy occurs. That's
>> the only thing I can think which would prevent us to use the src/test
>> bundles.
>>
>> --hardy
>>
>>
>>
>> On 15 Aug 2012, at 19:50, Steve Ebersole wrote:
>>
>>> Forgot to mention, the reason I am asking is that the current set up
>>> makes it more difficult to test in IDE. If you change one of these
>>> src/test/bundles files, you have to switch to command line, run gradle
>>> compilation (because it is a custom gradle task that copies the files
>>> over) before I can run those tests in IDE.
>>>
>>> On Wed 15 Aug 2012 12:46:48 PM CDT, Steve Ebersole wrote:
org.hibernate.jpa.test.packaging.PackagingTestCase uses ShrinkWrap to
facilitate "packaged" JPA tests. It uses metadata from
src/test/bundles, BUT it gets the copies moved over to target/bundles.
I am curious why it uses the target/bundles copy rather than the
src/test/bundles original?
>>>
>>> --
>>> st...@hibernate.org
>>> http://hibernate.org
>>> ___
>>> hibernate-dev mailing list
>>> hibernate-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> --
> st...@hibernate.org
> http://hibernate.org
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Eclipse-specific execution filters in POMs
hibernate doesn't use maven build anymore, so don't think this applies anymore? about m2e - upcoming version of m2e will allow storing these things *externally* to the pom.xml making this problem go away. /max On 23 Aug 2012, at 18:42, Brett Meyer wrote: > I know a lot of you don't use Eclipse, but... > > Its Maven plugin (M2E) does not have connectors for several of Hibernate > 3.3's lifecycle mappings. The only way to get the IDE to ignore them is to > add the following (as an example). What are your opinions of having > IDE-specific areas, like this, in the parent POM? > > > > > > org.eclipse.m2e > lifecycle-mapping > 1.0.0 > > > > > > > > org.jboss.maven.plugins > > > > maven-injection-plugin > > > [1.0.2,) > > > > bytecode > > > > > > > > > > > > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] envers / new metamodel
Hello Steve, I think I could start working on metamodel branch at the beginning of September. Is it acceptable for you? I don't want to postpone 4.1.7 release. JIRA task has been already registered: https://hibernate.onjira.com/browse/HHH-7490. Best Regards, Lukasz __ Information from ESET NOD32 Antivirus, version of virus signature database 7412 (20120823) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
