I'm playing with OGM on AS7, well trying to. I currently am trying to
use Hibernate 3.6.6.Final, latest OGM master source, latest AS7 master
source (plus these changes https://github.com/jbossas/jboss-as/pull/138).
I'm getting a "No Dialect mapping for JDBC type: 4" error during
Should I be using an earlier version of Hibernate 3.x perhaps?
Test code is here http://pastie.org/2348071 (contains persistence.xml
I am the CUBRID open source RDBMS Project Manager. Our parent company NHN has extensively been using Hibernate in its services together with CUBRID Database Server.
Here I would like to attach the CUBRIDDialect.java class file which supports CUBRID version 8.3.0 and higher (8.3.0, 8.3.1, and current stable 8.4.0) that we want to submit to Hibernate project.
If I should create an issue in JIRA, please let me know which project is the most appropriate.
CUBRID Project Manager.
If someone wanted to include both Hibernate 3 + Hibernate 4 in the same
project, that might be easier if the Hibernate 4 artifacts had a version
number in it or was changed for every new major release. I don't think
Maven supports building two versions of the same artifact (at the same
For the persistence provider name,
org.hibernate.ejb.HibernatePersistence, I'm wondering if we could have a
org.hibernate.ejb.HibernatePersistence4 in addition, that could be used
to uniquely reference Hibernate 4.x persistence providers.
I assume this is too late in the Hibernate 4 cycle to change, but wanted
to bring the idea up.
Changing the artifact names would impact other projects that depends on
Hibernate4 and would need to sync up with the changes as well.
What do you think?
I'm done with the serialization protocol. At least, it's in a good shape and should be integrated with trunk
It uses Avro and is now integrated with both JGroups and JMS backends.
I've abstracted Avro from our serialization logic so we can write alternative prototypes. I'd be interested to see a Protocol Buffer alternative for example. If anyone is interested, check out SerializationProvider and it's inplementation AvroSerializationProvider
Not everything is polished, I've created a list of follow up issues to be fixed before 4.0. https://hibernate.onjira.com/browse/HSEARCH-757
These a good candidates for community contribution.
I have one minor question
Should hibernate.search.jms.indexNameProperty that be part of the protocol or left separate like today?
I'll send a pull request in the next few minutes
I've done a first analysis for the state to transfer. It's not too bad.
This doc is cryptic but people familiar with Lucene should get what I mean:
It describes the state to pass around for each operation and detail what Document and Fieldable contain state wise and what would be transferred.
The two big annoyances are:
both of them can be the source of a Field.
While we can envision some strategies for Reader (worse case being we read the data and ship it over). I have not yet analyzed the implications of TokenStream.
For the rest with a smart enough state machine and possibly some private attribute reading, we should be able to serialize / deserialize Documents and Fieldables
I'm just starting to ask questions about this issue on the jira
I asked where the joda-time-1.6.2.jar is in the deployment.
Any other questions we should ask?
http://pastebin.com/SR3jsxGp contains the call stack for a
ClassNotFoundException of org.hibernate.hql.internal.ast.HqlToken (from
https://issues.jboss.org/browse/AS7-1433). The exception message isn't
shown but the jira has that.
I tried the supplied test case against Hibernate 4.0.0.Beta3 and don't
have the same problem. Does anyone know of a Hibernate 4.0.0.Beta4
change that could of caused this?
Perhaps we need to set the TCCL to the hibernate CL when constructing
the HqlBaseLexer as a workaround (the Hibernate classloader depends on
the antlr classloader module, so that should work).
Whatever the solution is, I'd like to better understand what changed to
On 08/03/2011 11:44 AM, Strong Liu wrote:
> Hi there,
> I get envers embedded into as7 :D
> see below:
> 1. org.hibernate module and org.hibernate.envers module depends on each other.
We might make the Hibernate to envers dependency optional in the
<module name="org.envers" optional="true"/>
So, that it is possible for the envers module to be removed for some
reason (I cannot think of why at the moment but just a thought).
> 2. org.hibernte.envers module automaticly injected into app when it is a jpa project.
This is where it gets tricky to package envers with the app. Have you
synced up with AS7 (7.0.1) master yet? I have another change coming
that could impact yours (in queue waiting to be merged).
Anyway, start with packaging envers as a standalone module and try
bringing a envers test into the as7/testsuite/compat/* based on the
current embedded test (there are only two tests and one is @Ignored).
> 3. org.jboss.as.testsuite.integration.jpa.hibernate.envers.BasicEnversTestCase in as7/testsuite/integration passes
Nice work! :-)
> 4. use org.hibernate.integrator.internal.ServiceLoader instead java.util.ServiceLoader to load META-INF/services file
> this custom ServiceLoader uses ClassLoaderService.
> sounds okay?
> Scott, question, if there is envers.jar embedded in app too, will app class loader see it before the envers.jar in org.hibernate.envers module?
As mentioned above, special care is needed to avoid having two envers
classloaders in the app deployment. We might have to make further
changes to not inject envers into the app, if the app already has its
own hibernate + envers.
> Best Regards,
> Strong Liu<stliu at redhat.com>
> On Aug 3, 2011, at 6:25 PM, Strong Liu wrote:
>> Begin forwarded message:
>>> can you send your test app to me?
>>> use cases:
>>> 1. envers and hibernate core in as7
>>> 2. envers jar in app, and hibernate core in as7
>>> 3. envers and hibernate core in app
>>> #1 is almost done, just need some code clean up
>>> (Scott, we missed services="import", that's why ClassLoaderService can't find resource in envers/META-INF/services)