Do you know when JBoss Logging 3.1.0.GA will hit the road. I can't really
release Hibernate Commons Annotations nor Core etc until we have the final
version. I mean we could but we might have to redo it.
Emmanuel
On 4 nov. 2011, at 16:05, David M. Lloyd wrote:
> Yeah let's target 3.1.0.GA for
Original Message
Subject: Re: [jboss-as7-dev] [hibernate-dev] Which JBoss Logging version
to use in AS and Hibernate Core
Date: Fri, 04 Nov 2011 10:05:21 -0500
From: David M. Lloyd
To: jboss-as7-...@lists.jboss.org
Yeah let's target 3.1.0.GA for everything. The final 1.0.0.GA
Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
Hibernate (Core) module. The "org.jboss.logging" module happens to be
"3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
sync with the AS7 version of JBoss Logging.
https://github.com/jbossas/jboss-as/blob/m
On Thu, 03 Nov 2011 20:48:50 +0100, Sanne Grinovero
wrote:
> I'm used to methods formatting like this in the code:
>
> gridDialect.removeAssociation( getCollectionMetadataKey() );
+1 Like Sanne is saying, this is what most of the code base uses, so stick
to it!
> it's also what is mandate
What a mess a simple thing like logging had become :-(
On Fri, 04 Nov 2011 14:06:33 +0100, Sanne Grinovero
wrote:
> With some small changes we can move Hibernate Search to JBoss Logging
> 3.1.0.Beta3,
> and this will work fine even for the outdated Infinispan 5.0, but a
> deployed application
With some small changes we can move Hibernate Search to JBoss Logging
3.1.0.Beta3,
and this will work fine even for the outdated Infinispan 5.0, but a
deployed application won't work on AS 7.0:
it requires an application server having Logging 3.1, or will need to
bundle this and isolate from the AS
I asked about AS7 on the AS7 mailing list; quoting David Lloyd's
answer: "AS7 is going to use 3.1.x. "
But at an early experiment showed that mixing Infinispan 5.0.x (Using
Logging 3.0.x) with Search forcing a version of 3.1.x wasn't going to
work.
I have upgraded the dependencies in Infinispan 5.
How does this relate to the bugs in the logging tools, like the one with
the
wrong debug line numbers.
Aligning with AS might be a good idea, but only if we don't introduce
regressions
in the logging.
--Hardy
On Fri, 04 Nov 2011 12:30:54 +0100, Emmanuel Bernard
wrote:
> JBoss AS 7.1 is
JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
// logging
logging:'org.jboss.logging:jboss-logging:3.1.0.Beta3',
logging_generator:
'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
## Timeline and work to do
Hibernate Core goes final next week if things go as planned. So it's time for
us to gear towards a CR2 and release it right after Core goes final. I have
done some JIRA cleanup and everything I think is important is tagged as fix
version 4.0.0.CR2. Please have a look,
I read about the UniqueKeyValidator. Will it throw me an exception or
hibernate will handle on its own and save only one entry n not duplicate
entries?
Thanks
Ankita
On 4 November 2011 12:43, Ankita Patil wrote:
> Hi,
> I already have an id as the primary key for the table say XYZ.
>
> Now, I w
Hi,
I already have an id as the primary key for the table say XYZ.
Now, I want to set a field or a combination of two fields as a unique key
so that when i try to save say 2 entries in the DB with same value for the
unique key field then only one entry should be made in the table with one
primary
12 matches
Mail list logo
