Activate URL links on blog
by Vlad Mihalcea
Hi,
Since we are now moderating the forum and disallow new users from posting,
we can activate links on the forum to increase user experience.
What do you think?
Vlad
9 years, 12 months
Hibernate ORM and Java 8 usage
by Steve Ebersole
The use of Java 8 features in Hibernate ORM is starting to expand. Luckily
it is still constrained to just tests.
However these usages make development in an IDE more and more difficult.
Previously this was isolated to hibernate-infinispan. Now[1] this has
crept into hibernate-entitymanager. We need to have a plan here. Either
we stop using Java 8 anywhere, or we move to Java 8 and rely on
AnimalSniffer to make sure we are still compatible.
Votes? Other options?
[1]
https://github.com/hibernate/hibernate-orm/commit/c2ece0108ed52d5e3a227ed...
9 years, 12 months
Issue a warning if field and getter annotation styles are mixed?
by Gunnar Morling
Hi,
Would it be feasible to raise a warning or error in cases where
mapping annotations are given on an element not matching the default
access type for that entity and @Access has not been given explicitly
either?
The most common case of this issue which I saw several times happen is
where @Id is given at the field level but some other mapping
annotations are given on property getters. The latter are silently
ignored in that case, resulting in mapping errors tough to understand
for those not super-deep into the details of access type retrieval. A
warning might help them.
Any thoughts?
--Gunnar
9 years, 12 months
Oracle running on CI
by Sanne Grinovero
Hi Steve,
when explicitly setting the Dialect to an empty string I have several
failures; when leaving it as-is I believe this run was valid though,
at least that's the feeling I'm getting from the kind of failures:
http://ci.hibernate.org/view/ORM/job/hibernate_orm_master_oracle/ws/hiber...
Some tests are failing, but a significant amount is passing just fine
and the logs seem to indicate that it's using the Oracle testing
instance.
Also, setting the dialect seems consistent with other matrix configurations?
Thanks,
Sanne
9 years, 12 months
Not letting Jenkins auto-close PRs upon build failures
by Gunnar Morling
Hi,
Not sure whether that's a new behaviour, but it's super annoying that
the pull request builder automatically closes pull requests if there
is a build failure. Can we change this so the PR stays open, please?
The current behaviour is highly frustrating, you need to re-open the
PR again after fixes, and in the worst case a PR falls through the
cracks because it's moved out to the "Closed" tab right away. It's
especially bad for contributor PRs where the failure is caused by
ourselves, e.g. build environment issues.
Thanks,
--Gunnar
9 years, 12 months
Is the the optional=false @OneToOne lazy retrieval still relevant
by Vlad Mihalcea
Hi,
I remember that for a bidirectional @OneToOne relationship, the optional =
false attribute could instruct Hibernate to always generate a Proxy
(because this association cannot be null),
so, if the fetch is LAZY, it would not generate a secondary query upon
fetching the parent-side entity.
I tested it with the latest Hibernate, and when fetching the parent entity
it always generates the secondary select for the child entity too.
Is this optimization not relevant anymore or is it an issue?
Vlad
9 years, 12 months
should immutable entities in the second level cache be invalidated when they are removed from the database?
by Scott Marlow
I missed adding the WildFly clustering configuration for the Hibernate
immutable-entity cache. I opened WFLY-5923 [1] for adding the cache but
am unsure of whether org.hibernate.annotations.Immutable means that the
application handles clearing the 2lc of stale immutable entities or if
that should happen automagically when immutable entities are removed
from the database.
In a cluster, I expect that the performance of caching
immutable-entities, would be faster if we assume they will not be
invalidated from the 2lc (e.g. let applications clear them from the
cache).
Since we are using Infinispan for the 2lc in WildFly, I would like to
use an Infinispan simple-cache for immutable-entities, which does no
invalidation. However, just because I would like to do this, doesn't
make it right. :-) Which is why I'm asking, what the design intention
is, so I can configure the WildFly clustering configuration (for
immutable entities), to align with the intent.
From Immutable javadoc:
"
Mark an Entity or a Collection as immutable. No annotation means the
element is mutable.
An immutable entity may not be updated by the application. Updates to an
immutable entity will be ignored, but no exception is thrown.
...
"
Scott
[1] https://issues.jboss.org/browse/WFLY-5923
10 years
