See inline...
On 07/31/2013 06:08 AM, Sanne Grinovero wrote:
> # Hibernate:
>
> Probably the best finding is the 'Shared non-thread-safe content'
> finding in the class 'EntityManagerFactoryRegistry'. In general, the
> inconsistent and mixed synchronisation findings are not very good, but
> the (
Discussed OGM development, progress on the new website design, and other
topics..
[11:17] Meeting ended Thu Aug 1 16:16:57 2013 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[11:17] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/20
Overall I am pretty confident you are not using the latest as we
discussed on IRC. But some comments inline...
On Thu 01 Aug 2013 10:30:04 AM CDT, Christian Bauer wrote:
- show quoted text -
Yes I think this is still a bug. I'll fix this. Its because of the
concept of Returns. I should loo
wrote:
> On 01.08.2013, at 19:01, Steve Ebersole wrote:
>
>>> 2. If there is only one ResultSet returned by the SP, I should be able to
>>> call StoredProcedureQuery#getResultList() without first calling
>>> hasMoreResults(). This maps to JDBC CallableStatement#excut
First, you lump sequences and table-based sequence together here, but I
assure you sequences (real database sequences) are read inline with the
current transaction. In the case of a real sequence, the database
already handles the isolation of the generated values outside
transactional context.
Mainly discussed LoadPlan progress...
[10:45] Meeting ended Thu Aug 15 15:44:07 2013 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[10:45] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-08-15-15.01.html
[10
Mostly discussed database matrix testing...
[10:35] Meeting ended Thu Aug 22 15:33:27 2013 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[10:35] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-08-22-15.00.html
I prefer HHH or HQL as well.
On 08/27/2013 06:20 AM, Sanne Grinovero wrote:
> My vote goes to #2 as long as we use a shorter code. HQL-1 doesn't
> looks too bad.
>
> In case we incorporate this in ORM I'd change them to HHH- but we can
> discuss that if/when that happens.
>
> On 27 August 201
nits that can easily fit under one key.
On Tue 27 Aug 2013 09:22:51 AM CDT, Gunnar Morling wrote:
> Cool, thanks everyone for your feedback.
>
> Let's go for HQL in all the parser modules then. I'll register that
> prefix at https://community.jboss.org/wiki/HowToLogInJBossProj
I am contemplating duplicating[1] our existing JPA API jars to use a
better GAV naming scheme, specifically the GAV naming scheme we plan on
adopting for any new JPA specs. We have used completely different
naming scheme for 1.0 then we did for 2.0 and 2.1. And even for 2.0 and
2.1 we used th
On Tue 27 Aug 2013 10:16:38 AM CDT, Emmanuel Bernard wrote:
> +1 to have a suffix not related tot he draft. Like you I have pushed
> spec jars that did not reflect eh state of a draft necessarily.
>
> BTW, why retrofit that scheme? Why not just apply it for 2.1?
Well applying it for 2.1 is in fact
Well thats the beauty of duplicating (in theory). Nothing really to
fight. Now if we were doing relocation, yes I'd agree with you :)
On 08/27/2013 10:28 AM, Emmanuel Bernard wrote:
> On Tue 2013-08-27 10:22, Steve Ebersole wrote:
>> On Tue 27 Aug 2013 10:16:38 AM CDT, Emmanuel
right? I.e. the spec would never be updated
> from say 2.2 to 2.2.1 (but to 2.3 in this case)?
>
>
> 2013/8/27 Steve Ebersole <mailto:st...@hibernate.org>>
>
> I am contemplating duplicating[1] our existing JPA API jars to use a
> better GAV naming scheme, spec
ce mode. In
> which case the spec lead could use micro or some prefix like M1.
> But we don't know if that will happen for JPA nor which one will be
> chosen.
>
> Emmanuel
>
> On Tue 2013-08-27 10:55, Steve Ebersole wrote:
> > I don't ever f
Mostly discussed LoadPlans.
[10:36] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-08-29-15.04.html
[10:36] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-08-29-15.04.txt
[10:36]
Given an XProperty, is there a way to ask for annotations which are
defined only locally on that declared property (not on any super classes)?
Basically given this situation:
@MappedSuperclass
public class Super {
...
@Convert( converter=Converter1.class )
public String getIt() {
composite paths.
On Thu 29 Aug 2013 02:57:05 PM CDT, Emmanuel Bernard wrote:
> On Thu 2013-08-29 14:22, Steve Ebersole wrote:
>> Given an XProperty, is there a way to ask for annotations which are
>> defined only locally on that declared property (not on any super classes)?
>
&
use
PropertyHolder#resolveAttributeConverter to pass what it needs to pass.
WDYT?
On Thu 29 Aug 2013 03:06:37 PM CDT, Gunnar Morling wrote:
> 2013/8/29 Emmanuel Bernard <mailto:emman...@hibernate.org>>
>
> On Thu 2013-08-29 14:22, Steve Ebersole wrote:
> > Given an XProperty,
On Fri 30 Aug 2013 06:05:37 AM CDT, Emmanuel Bernard wrote:
>>
>>
>> 2) The 'declaringClassName' passed in to SimpleValueBinder#setType
>> is Sub. So maybe we can leverage that. But
>> org.hibernate.cfg.annotations.PropertyBinder#makePropertyAndValue
>> (the main caller of this method) has explici
from one use case to another (basics, composites,
plurals).
On Fri 30 Aug 2013 07:47:36 AM CDT, Emmanuel Bernard wrote:
> On Fri 2013-08-30 6:27, Steve Ebersole wrote:
>>
>> On Fri 30 Aug 2013 06:05:37 AM CDT, Emmanuel Bernard wrote:
>>>>
>>>>
>&g
erride always overrides. The is just
>> not the case here with converters. Plus how AttributeOverride works
>> does not need to vary from one use case to another (basics,
>> composites, plurals).
>>
>>
>> On Fri 30 Aug 2013 07:47:36 AM CDT, Emmanuel Bernard wrote
nAnnotationReader is only about reading
> the XML and converting it into annotations.
>
> I understand that implementing the rules based on the annotations is
> more complex than annotation override.
>
> On Fri 2013-08-30 8:44, Steve Ebersole wrote:
>> Its not that easy. This is not
10:52:40 AM CDT, Emmanuel Bernard wrote:
> On Fri 2013-08-30 10:13, Steve Ebersole wrote:
>> Hit send too early...
>>
>>
>> On 08/30/2013 09:55 AM, Steve Ebersole wrote:
>>> Also, unless we have some normalization rules, my point was that
>>> we literally
org.hibernate.annotations.common.reflection.XAnnotatedElement
On Tue 03 Sep 2013 05:22:22 PM CDT, Steve Ebersole wrote:
> After looking through this some more, I think what you say could
> almost work. But:
>
> 1) Still need a way to determine the declarer of a property rather
FYI, unless I hear otherwise:
https://hibernate.atlassian.net/browse/HCANN-56
On Tue 03 Sep 2013 11:01:02 PM CDT, Steve Ebersole wrote:
>
>
> org.hibernate.annotations.common.reflection.XAnnotatedElement
>
> On Tue 03 Sep 2013 05:22:22 PM CDT, Steve Ebersole wrote:
>> After
Gah, stupid.
Its the declared/non-declared status of the method/field that is
important here, not the annotations...
On Tue 03 Sep 2013 11:08:16 PM CDT, Steve Ebersole wrote:
> FYI, unless I hear otherwise:
> https://hibernate.atlassian.net/browse/HCANN-56
>
> On Tue 03 Sep 2013 11:
...
@Embedded
@Convert( attributeName="city", converter=Converter2.class )
public Address homeAddress;
}
Unless we somehow kept "proximity info" or "location info" about the
conversion in PropertyHolder.
On Wed 04 Sep 2013 01:27:21 AM CDT, Emmanuel
What is the proper way to release hibernate-commons-annotations? Do we
just use Maven release plugin?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
d
have enough info to fully resolve the converter to use properly.
There are similar concerns in ComponentPropertyHolder, but maybe a
discussion of the above will shed light on those concerns too.
On Wed 04 Sep 2013 02:44:40 PM CDT, Steve Ebersole wrote:
>
> I am still a bit confused on ho
XProperty "works", but pretty sure it breaks
down in the composite path cases due to the ordering of the calls
(really need the inner most converts applied first).
As of now, 4.3 Beta4 is hung up on getting this sorted out.
On Wed 04 Sep 2013 11:43:19 PM CDT, Steve Ebersole wrote:
Discussed finishing up AttributeConverter resolution, LoadPlan progress
and some JPA TCK points.
[10:46] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-09-05-15.03.html
[10:46] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freen
one per path-part). The down
side to this is that at no time do we have an overview of the overall
converts for a property path (aside from walking the composite path to
actually resolve the converter to use).
>
> any problem with this approach ?
>
>>
>>
>>
>&
morrow. Anyone familiar with those bits of code willing to
look this over in the next 12 hours if I go through the steps of
creating the PR?
On 09/05/2013 12:10 PM, Steve Ebersole wrote:
> On Thu 05 Sep 2013 11:52:22 AM CDT, Shaozhuang Liu wrote:
>>> Also, I am not sure that iterating prop
https://github.com/hibernate/hibernate-orm/pull/591
On Thu 05 Sep 2013 10:06:14 PM CDT, Shaozhuang Liu wrote:
> I can give it a try
> -
> Best Regards,
>
> Strong Liu
> http://about.me/stliu/bio
>
> On 2013Sep 6, at 8:15 AM, Steve Ebersole wrot
We will need to make a slight change to execution of native SQL queries
in order to pass the JPA 2.1 TCK. The new TCK tests that execution of a
native SQL query does an "auto flush".
The problem with this is that, unlike with HQL/JPQL, we do not know the
tables affected by a native SQL query (
I never heard alternatives, so this is now implemented as described
below.
https://hibernate.atlassian.net/browse/HHH-8487
On Tue 10 Sep 2013 12:05:35 AM CDT, Steve Ebersole wrote:
> We will need to make a slight change to execution of native SQL
> queries in order to pass the JPA 2
I had planned on releasing 4.3 Beta4 today, but JBoss's Nexus repo is
under the weather. Let's assume it will be fixed by tomorrow and plan
on the release then.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailma
Quite a few discussions around JPA 2.1. Discussed ongoing tooling work:
maven/gradle plugin development, migration of "JPA Metamodel Generator"
project into ORM. And more.
[10:44] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-09-12-15.01
Get your hot fresh Beta release...
http://in.relation.to/Bloggers/HibernateORM430Beta4Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: https://hibernate.atlassian.net/browse/HHH-8445
I'd like to get opinions on this. Essentially the JPA spec
(StoredProcedureQuery) is silent on how/if calling database functions
through this API is supposed to be supported. I asked for clarification
of this from the rest of the EG, but got
StoredProcedureQuery spq = ...;
spq.registerStoredProcedureParameter( 1, Calendar.class, ParameterMode.IN );
spq.setParameter( 1, aGregorianCalendar, TemporalType.DATE );
We have some failures against the TCK for this scenario. There are 2
ways to solve this, and I wanted to get opinions on the
e are my 0.02$ which need to be taken with a grain of salt since I am not
> so familiar with the
> procedure call stuff.
>
> On 17 Jan 2013, at 6:15 PM, Steve Ebersole wrote:
>
>> In my opinion, ideally the JPA spec would have defined a separate method
>> to register a &q
Discussed plans for merging hibernate-core and hibernate-entitymanager
mostly (how, when, etc)...
[11:14] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-09-19-15.00.html
[11:14] Minutes (text):
http://transcripts.jboss.org/meeting/irc.free
I had to hook into processing within
JPAOverriddenAnnotationReader so I took the opportunity to reorganize
the code.
As part of that there were 2 pieces of code in particular that I could
not figure out the purpose of:
1) We were excepting as a sub-element of
. The code even had a comment a
So what I did earlier does not work for Collections. Collections go
through a very different code path (even ElementCollection which i found
very odd). That code does not use the pieces of PropertyBinder and
SimpleValueBinder that got changed.
Even more oddly, the only time I see uses of
Pro
After stepping through the code, I can answer the last question. The
method simply badly named and element collections route through there
also.
On Sat 21 Sep 2013 11:19:50 AM CDT, Steve Ebersole wrote:
> So what I did earlier does not work for Collections. Collections go
> through
The spec specifically says that javax.persistence.Query#setLockMode
should throw an IllesgalStateException when called on a query that
represents a native query. Our implementation has not done that
historically since we do have (to varying degrees) the ability to apply
locking to the SQL.
Ho
Anyone have compelling reasons to continue to call
org.hibernate.engine.internal.Nullability#checkNullability when deleting
an entity?
To a lesser degree, how about reasons for calling
org.hibernate.engine.internal.ForeignKeys.Nullifier#nullifyTransientReferences
when deleting?
___
Why/how? I do this routinely.
On 09/24/2013 12:26 PM, Emmanuel Bernard wrote:
> I am still stuck on that one. I cannot import Hibernate ORM in IntelliJ IDEA
> :(
>
> On 17 mai 2013, at 03:28, Emmanuel Bernard wrote:
>
>> yes the projects themselves can use JDK 7.
>>
>> On Fri 2013-05-17 11:59, G
o it for the sake of
> verifying it is a nice out-of-the-box experience for new contributors.
>
> Frankly this "least pain" strategy for the occasional contributor is
> what I still consider an nice point of Maven.
>
>
> On 24 September 2013 18:29, Steve Ebersole wrote:
&g
Mostly discussion of JPA 2.1 TCK progress
[10:20] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-09-26-15.01.html
[10:20] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-09-26-15.0
At this point I think we are far enough along with LoadPlans and
EntityGraph work to move that over to upstream master. Given that the
rest of the 2.1 TCK is in good shape I'd like to do that as soon as
possible. So I'd like to plan out how/when to get this moved over from
my fork to upstream
Since I have not heard back I went ahead and tried merging master to
the HHH-8276 branch. But I see 11 failures then. Gail had mentioned
that the tests were down to zero failures. Is there something special
I need to do?
On Fri 27 Sep 2013 04:26:11 PM CDT, Steve Ebersole wrote:
> At t
With HV or BV enabled, generally speaking Nullability#checkNullability
no-ops anyway..
On 10/02/2013 08:36 AM, Emmanuel Bernard wrote:
> On Mon 2013-09-23 17:07, Steve Ebersole wrote:
>> Anyone have compelling reasons to continue to call
>> org.hibernate.engine.inter
Various topics discussed today.
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-03-14.57.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-03-14.57.txt
Log:
http://transcrip
I thought I remember someone (Brett? Strong?) going through an cleaning
up references to logging libraries we no longer use. But I still see
entries in libraries.gradle in master for:
slf4j_api: "org.slf4j:slf4j-api:${slf4jVersion}",
slf4j_log4j12: "org.slf4j:slf4j-lo
I tentatively scheduled 4.3.0.Beta6 (which is looking likely to be the
first CR) for November 6th which is the 4 week timebox. Trouble is,
that this is the day I am scheduled to fly back from Rome.
So all in all, this release is likely to happen early or late.
__
What is gained needs to be balanced by what you are giving up.
OGM itself is new, but at the end of the day its a JPA provider which is
not new. Basing on Java 7 will limit adaption from folks wanting to
drop OGM in to their app as replacement for their JPA provider to give
it a spin in certai
Per subject. Please dont push anything to upstream master until the
release is done. Thanks.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Get the details at
http://in.relation.to/Bloggers/HibernateORM430Beta5Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Done. Sorry this one took so long. Discovered a problem mid-release
this time.
Anyway, push away..
On Wed 09 Oct 2013 01:02:48 PM CDT, Steve Ebersole wrote:
> Per subject. Please dont push anything to upstream master until the
> release is done.
We actually made use of the topics feature of the bot today :) One got
missed by the bot...
[11:38] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-10-14.55.html
[11:38] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenod
Here is the list of proposed topical guides i started:
https://github.com/hibernate/hibernate-orm/wiki/ProposalTopical-Docs
On Thu 10 Oct 2013 11:47:03 AM CDT, Steve Ebersole wrote:
> We actually made use of the topics feature of the bot today :) One
> got missed by the bot...
>
I just pushed the initial work getting Asciidoctor building through Gradle.
I have done zero styling or layout etc. This is just the initial
ability to generate Asciidoctor docs via Gradle.
At the moment there is just one doc (the ServiceRegistry guide that is
still WiP) that is rendered to ju
generateRegistryGuideHtml task I
mentioned before...
It obviously still needs editing and layout work, but if there is any
content you'd like to see that is not there or any content you'd like
to see expanded... let me know...
On Mon 14 Oct 2013 08:21:34 PM CDT, Steve Ebersole wrote:
>
Reference : https://hibernate.atlassian.net/browse/HHH-2907
I'd like to get people's feedback on the idea of re-purposing
org.hibernate.annotations.Generated as discussed on HHH-2907. As
mentioned in the Jira, my inclination is to do the re-purposing.
Also, thoughts on the distinction between
On 10/17/2013 07:24 AM, Gunnar Morling wrote:
>
> I think I'd keep it simple and with one way of specifying the
> generator and see how it works. If there is demand for the other
> option it could be added later on.
My concern there is that virtually noone aside from me really
knows/understand
Today's meeting focused mainly on JPA 2.1 EntityGraphs and getting that
support knocked out.
[11:39] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-17-14.58.html
[11:39] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.
Gail is correct. extra-lazy is something else completely.
On Oct 22, 2013 4:00 PM, "Gail Badner" wrote:
> As far as I can tell, "extra-lazy" applies to the collection itself, not
> its elements. lazy="extra" is defined on , , , ,
> .
>
> Currently, an extra-lazy collection can be configured hav
Discussed tasks related to ORM 4.3 release...
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-24-14.57.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-24-14.57.txt
Log:
ht
On Oct 25, 2013 10:26 AM, "Hardy Ferentschik" wrote:
> * What should be the next version of the annotation processor? I guess it
could just use the main ORM version, so
> we would make a version jump from 1.3.0.Final to 4.3.x
4.3.x
> * Should we move the docbook sources to the documentation m
On Fri 25 Oct 2013 12:42:15 PM CDT, Hardy Ferentschik wrote:
>>> * Should we move the docbook sources to the documentation module and create
>>> a new "book", next to devguide, manual
>>>and quickstart? I guess there are pro and cons for each approach. I
>>> would lean towards moving the meta
I wanted to highlight a new feature in 4.3 as it came about from
performance testing efforts. Its a way to hopefully help track down
potential performance problems in applications that use Hibernate. In
this way it is similar to statistics, but it operates per-Session
(though certainly custom
Adding tenantIdentifier to persister is absolutely wrong. Think of
persisters as scoped to the SessionFactory while tenancy is per Session.
Now because an EntityKey is logically per session as well we may be able to
remove from there. Again *logically*. I'll have to look at the ways in
which En
I won't be able to make the irc meeting today
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
2/381/changes>
Changes:
[Steve Ebersole] HHH-8720 - Create an index for the topical guides
[Steve Ebersole] HHH-8692 - Document value generation feature
--
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
S
First CR for JPA 2.1 support...
http://in.relation.to/Bloggers/HibernateORM430CR1Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I started today on removing the separate calls to javac to execute
Annotation Processors in the Hibernate ORM build. From Gradle it is
working fine. However when I try to enable Annotation Processing in
IntelliJ, it complains about the "module cycle" between hibernate-core
and hibernate-testi
This looks to be a bug in the JPA metamodel generator:
Caused by: java.lang.ClassCastException:
com.sun.tools.javac.code.Symbol$TypeSymbol cannot be cast to
javax.lang.model.element.TypeElement
at
org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor$ContainsAttributeTypeVisitor.visitDecla
Ah, I see. I applied metagen to tests in envers, not main. Seems an
odd error given that condition. Hardy?
I fixed my mistake.
On Fri 22 Nov 2013 06:39:06 PM CST, Steve Ebersole wrote:
> This looks to be a bug in the JPA metamodel generator:
>
> Caused by: java.lang.ClassCast
http://discuss.asciidoctor.org/Gradle-plugin-and-permgen-td1040.html#a1069
On Nov 23, 2013 2:11 PM, "Scott Marlow" wrote:
> Has anyone seen the below error doing a "./gradlew build
> :release:distZip"?
>
> Is there a way to skip building ":documentation:asciidoctor" during a
> release?
>
> Build
Sorry. Hit send too soon. Yes we have known of this issue. The ljnk
above is to the discussion I started on the asciidoctor list. I will try
their work around monday.
On Nov 23, 2013 8:37 PM, "Steve Ebersole" wrote:
> http://discuss.asciidoctor.org/Gradle-plugin-and-permgen-td10
s before I started making changes. Scott, Hardy.. as far as
I can tell you guys did this part of the test code. Any memories of that?
On 11/19/2013 06:51 PM, Steve Ebersole wrote:
>
> Anyone know why this test continues to fail intermittently?
>
> -- Forwarded message --
projects that use testing w/o core? AFAIK, no, but
> correct me if I'm overlooking something.
>
> Brett Meyer
> Software Engineer
> Red Hat, Hibernate ORM
>
> - Original Message -
> From: "Steve Ebersole" <mailto:st...@hibernate
on this? It seems the CI tests are
> passing again
> and I am not sure whether I ever wrote any locking tests. If so, I completely
> forgot about it.
>
> —Hardy
>
>
> On 24 Jan 2013, at 15:46, Steve Ebersole wrote:
>
>> I looked at this some more.
>>
>&
generateSources.
[1] http://issues.gradle.org/browse/GRADLE-2966
On Fri 29 Nov 2013 04:12:18 AM CST, Gunnar Morling wrote:
> We've removed the dependency to hibernate-testing from OGM now as it
> indeed wasn't actually used.
>
> --Gunnar
>
>
>
> 2013/11/25 Steve Ebe
Dec 2013 10:46:20 AM CST, Hardy Ferentschik wrote:
>
> On 2 Jan 2013, at 16:07, Steve Ebersole wrote:
>
>> So I am also working on reverting the change to use -proc:both with a
>> single compile phase. However, what we will end up with is still a
>> single -proc:onl
On Tue 03 Dec 2013 04:39:43 AM CST, Hardy Ferentschik wrote:
>
> On 2 Jan 2013, at 18:12, Steve Ebersole wrote:
>
>> Well technically it is not valid according to the javac spec, which was
>> David's point (which I assume who you are referring to).
>
> What is
For various reasons I need to cut a second CR for 4.3. I will do that
release on Thursday the 5th.
Prior to that I need to make sure that both the JPA TCK and the
persistence portions of the EE TCK (within WidlFly) pass; trouble is
that the jobs which run the persistence portions of the EE TCK
I found a few spare minutes to work on this a little and move it into
the next stage with some actual interfaces, impls and usages to help
illustrate some of the proposed concepts.
https://github.com/sebersole/JdbcSession
The README.md is very up-to-date and detailed. Would be good to get
inp
When is the last time we have synced merged master to the metamodel branch?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
-- I can give it another shot.
>
> Brett Meyer
> Software Engineer
> Red Hat, Hibernate ORM
>
> - Original Message -
> From: "Steve Ebersole"
> To: "hibernate-dev"
> Sent: Wednesday, December 4, 2013 1:39:39 PM
> Subject: [hibernate-dev] ma
Can't (read you should be!) you use
org.hibernate.engine.spi.SessionImplementor#generateEntityKey ?
Its signature hides the values from Session actually kept on the
genernated EntityKey:
public EntityKey generateEntityKey(Serializable id, EntityPersister
persister);
That signature has not ch
I am starting the 4.3 CR2 release, please hold off from pushes for a bit
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Feel free to push again. I am finished with the repo at this point.
Need to get daughter from school and will finish up release
(announcements) tonight.
On Thu 05 Dec 2013 01:17:59 PM CST, Steve Ebersole wrote:
> I am starting the 4.3 CR2 release, please hold off from pushes for a
Per subject, Hibernate ORM 4.3.0.CR2 has just been released.
http://in.relation.to/Bloggers/HibernateORM430CR2Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
low that to drive the "before/after completion"
callbacks (the org.hibernate.Transaction would still potentially manage
actually calling commit/rollback on the
TransactionManager/UserTransaction). In short, does any one see
problems with this approach?
On Wed 04 Dec 2013 11:27:10
chronization(Synchronization sync),
> I see:
>
> Throws: RollbackException - Thrown to indicate that the transaction has been
> marked for rollback only.
>
> That would make it a JTA spec requirement.
>
> More feedback coming...
>
> ----- Original Message -
>&g
JB point of view, the EJB container will eventually notice
> > that the transaction is marked for rollback only when the EJB bean
> > invocation completes but its not clear (to me) what this means at the
> > JPA level.
> >
> > Might be worth asking the JBossTS team, this
On Fri 06 Dec 2013 05:10:10 PM CST, Gail Badner wrote:
>
> It would be nice to make the return value generic:
>
> public T accept(PreparedStatementQueryOperation operation, Class
> resultClass);
95 times out of 100 inside Hibernate code we really can't take advantage
of the parameterized type.
1 - 100 of 3669 matches
Mail list logo
