Hi,
There are several deprecated methods on Session:
* public Object load(Class theClass, Serializable id, LockMode lockMode)
* public Object load(String entityName, Serializable id, LockMode lockMode);
* public void lock(Object object, LockMode lockMode);
* public void lock(String entityName, Ob
Hi guys,
Taking this comment as a starting point
http://vladmihalcea.com/2015/04/27/how-does-hibernate-read_only-cacheconcurrencystrategy-work/comment-page-1/#comment-3404
To reduce cache entities hydration, we could simply use the:
"hibernate.cache.use_reference_entries" setting, but that's too
Any of you have seen this issue? Shall I open a ticket?
2015-05-04 0:03 GMT+03:00 Petar Tahchiev :
> Hi guys,
>
> I finally managed to reproduce it - here's a small application that will
> generate the provided exception:
>
> https://github.com/paranoiabla/hibernate-hsql-issue
>
> Please notice t
I cannot see any harm.
> On 04 May 2015, at 23:34, Steve Ebersole wrote:
>
> I recently have seen a bunch of attempts (and questions about) using JPA
> callbacks with SessionFactory. At the moment, a user would need to
> manually enable the proper event listeners to get this to work. I am
> th
Hi,
When an entity is updated for the
"CacheConcurrencyStrategy.NONSTRICT_READ_WRITE", the cache entry is removed
twice:
1. Once from update:public boolean update(Object key, Object value, Object
currentVersion, Object previousVersion)
throws CacheException {
remove( key );
return fa
Hi,
When an entity is updated for the
"CacheConcurrencyStrategy.NONSTRICT_READ_WRITE", the cache entry is removed
twice:
1. Once from update:
public boolean update(Object key, Object value, Object currentVersion, Object
previousVersion)
throws CacheException {
remove( key );
retur
Hello all,
I actually have multiple questions on the subject.
# Module name
The Maven artifact id of the modules we're producing for WildFly 8 is
aptly named "org.hibernate.ogm:hibernate-ogm-modules-wildfly8".
I still think that's a good choice, as deploying modules is an
operation which is stri
> # EAP versions
>
> We're also producing modules for JBoss EAP6, but AFAIR these need some
> ove and I'm not sure if it's worth the effort - it might not need to
> much work and I'm happy to look at it if you want to, but in case we
>fix it these should have proper integration tests [next]:
I thi
Hi,
Answers inline.
--Gunnar
2015-05-05 13:04 GMT+02:00 Sanne Grinovero :
> Hello all,
> I actually have multiple questions on the subject.
>
> # Module name
>
> The Maven artifact id of the modules we're producing for WildFly 8 is
> aptly named "org.hibernate.ogm:hibernate-ogm-modules-wildfly8
On 5 May 2015 at 12:33, Davide D'Alto wrote:
>> # EAP versions
>>
>> We're also producing modules for JBoss EAP6, but AFAIR these need some
>> ove and I'm not sure if it's worth the effort - it might not need to
>> much work and I'm happy to look at it if you want to, but in case we
>>fix it these
On 5 May 2015 at 12:39, Gunnar Morling wrote:
> Hi,
>
> Answers inline.
>
> --Gunnar
>
> 2015-05-05 13:04 GMT+02:00 Sanne Grinovero :
>>
>> Hello all,
>> I actually have multiple questions on the subject.
>>
>> # Module name
>>
>> The Maven artifact id of the modules we're producing for WildFly 8
Had a quick chat with Sanne on IRC :)
The reason it seemingly works with WF 8 + ORM 4.3.7 is that the bug I have
been talking about (HHH-9451) is not triggered by any of the integration
tests running on WF but only by a unit test in the MongoDB module.
Thus we agreed to not go through the hazzle
On 5 May 2015 at 13:30, Gunnar Morling wrote:
> Had a quick chat with Sanne on IRC :)
>
> The reason it seemingly works with WF 8 + ORM 4.3.7 is that the bug I have
> been talking about (HHH-9451) is not triggered by any of the integration
> tests running on WF but only by a unit test in the Mongo
In regards to the first 2 sets, yes I agree.
In regards to your second point, see the discussion on
https://hibernate.atlassian.net/browse/HHH-9761 first. One idea was to
keep those methods as an "untyped API". Another option would be to add
another byId (etc) method for untyped operations, some
Petar, I have just been focusing on other things the past 3 days or so.
Chill :)
I will look at this this week. If you happen to have a chance to debug it
any further by then, that would rock. FWIW, I do not think it is in any
way related to the duplicate secondary table warnings. Those are
com
Please don't remove deprecated methods if there is no real need!
On 5 May 2015 at 14:12, Steve Ebersole wrote:
> In regards to the first 2 sets, yes I agree.
>
> In regards to your second point, see the discussion on
> https://hibernate.atlassian.net/browse/HHH-9761 first. One idea was to
> ke
Why? Why even deprecate methods then?
On Tue, May 5, 2015 at 8:18 AM, Sanne Grinovero wrote:
> Please don't remove deprecated methods if there is no real need!
>
>
>
> On 5 May 2015 at 14:12, Steve Ebersole wrote:
> > In regards to the first 2 sets, yes I agree.
> >
> > In regards to your seco
FWIW, those hooks in Hibernate 5 already exist, based on Jandex 1, of
course :)
We are not currently using Jandex. That was work happening under the
metamodel redesign, which we had to push to 6.0.
When we do start using Jandex, the plan is to use the provided Jandex as a
base. But the problem
> What is "end of deployment"? Is that the end of phase-2 in our 2-phase
> JPA bootstrap design? If so, that should be fine.
Yes, the end of phase-2 in our 2-phase JPA bootstrap design should occur
before (WildFly) deployment is complete.
___
hibern
On Tue, May 05, 2015 at 08:36:27AM -0500, Steve Ebersole wrote:
> Why? Why even deprecate methods then?
+1
--Hardy
pgplBvr0yyAdf.pgp
Description: PGP signature
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailm
20 matches
Mail list logo
