Lucene moving to Java7
by Sanne Grinovero
The next minor release of Apache Lucene v. 4.8 will require Java7.
The Lucene team has highlighted many good reasons for that, including
some excellent improvements in sorting performance and reliability of
IO operations: nice things we'd like to take advantage of.
Objections against baseling Hibernate Search 5 to *require* Java7 too?
We hardly have a choice, so objections better be good ;-)
-- Sanne
10 years, 9 months
Delivery Failure
by Postmaster
---------------------------------------------------------------------------------
The message you sent to amigosenmarcha.org/informacion was rejected because it would exceed the quota for the mailbox.
The subject of the message follows:
Subject: Vacancy - apply online
---------------------------------------------------------------------------------
10 years, 9 months
Fix for the Eclipse formatter
by Guillaume Smet
Hi,
Here is a fix for the Eclipse formatter posted on the community site.
Currently, it changes:
x.<String, Element>foo();
to
x.<String, Element> foo();
which doesn't respect the checkstyle rules.
Thought it might be useful to report it as it's quite painful to have
a build broken because of that.
Thanks!
--
Guillaume
10 years, 9 months
Attribute paths and '.' versus '#' as separator
by Steve Ebersole
This is a bit of a potentially insidious one. Not the best way to start
off a discussion, I know :)
The premise is this... Until now Hibernate has represented attribute roles
using dots. For an attribute named 'department' on the com.acme.Employee
entity, the role would be "com.acme.Employee.department". In terms of
embeddables, say Employee had an 'address' embedded with its own attributes
like 'city'. Then, the full role for 'city' would be
"com.acme.Employee.address.city".
As you can start to see the dots here are completely indistinguishable in
terms of those which define the package/class and those which identify the
attribute "path".
So one of the things I started playing with in 5 is to replace the
separators used in attribute paths to use '#', such that
"com.acme.Employee.address.city" would instead be
"com.acme.Employee#address#city". This makes the role fully parseable
which is actually useful in quite a few situations. And it REALLY helps in
things I have just started working on like storing metadata for composites
(embeddeds/embeddables) on the SessionFactory, which is the first step in
support for some cool new features around embeddables like discriminated
inheritance support.
However, there is a minor drawback. Like all attributes, collections have
a role. Unfortunately the use of '.' in their role Strings leaks into the
SPI in terms of locating the CollectionPersisters.
So the question is whether to continue with this path of replacing the use
of '.' with '#' for attribute path separators. The drawback is
unfortunate. The benefit is very nice, but I can't really say it is
required atm.
Votes? Thoughts?
10 years, 9 months
Tests asserting warnings get logged
by Steve Ebersole
I again have in mind adding some test assertions that a particular logging
(WARN) message gets triggered. We have already one such test in place,
which is one of the places where our usage of byteman comes in.
Given the problems using byteman is causing in CI and the fact that our
reliance on it is pretty light at the moment, I wanted to reach out for
some other ideas/proposals for ways to handle this testing requirement. I
will also reach out to David and James to see if this is something JBoss
Logging itself could help us tackle; maybe there is some feature there
already that would help. Any other ideas/proposals?
10 years, 9 months
Build failure executing :hibernate-core:runAnnotationProcessors
by Gail Badner
After pulling, I am getting a failure executing :hibernate-core:runAnnotationProcessors.
I tried building with --debug and it looks like the hibernate-core/target/generated-src/apt/main is deleted without being re-generated. When hibernate-core is compiled, there are failures because package org.hibernate.hql.internal.antlr does not exist.
Anyone have ideas why this is happening?
Thanks,
Gail
10 years, 9 months
Re: [hibernate-dev] Welcome to the "hibernate-dev" mailing list (Digest mode)
by 秋雪 佛
hello,i am chinese ,so my english is not good ,sorry! i use hibernate orm + jdts.13 connection sqlserver 2008 , and there are a class of User .
class User
{
....
private Blob pictureImg;
......
}
when i save user ,i got a problem " net.sourceforge.jtds.jdbc.JtdsPreparedStatement.setBinaryStream(JtdsPreparedStatement.java:1234) ", i know jtds do not implement the method " setBinaryStream" .
but i use hibernate 3 ,it's work well, why? has hibernate-release-4.3.4.Final this " bug" ,i hope your reply,thank you
10 years, 9 months
"derived identifier" mapping
by Steve Ebersole
What's the rational for supporting the following?
@Entity
class Product {
...
}
@Entity
class Order {
...
}
@Entity
@IdClass(...)
class OrderLine {
@Id
private Order order;
@Id
private Product product;
}
Specifically, the declaration of the OrderLine primary key. Why would
these not have to be `@Id @ManyToOne`?
10 years, 9 months
Metamodel, Jandex and "XML mixins"
by Steve Ebersole
I was looking into some failures on master in regards to XML overrides for
JPA annotations in relation to our friend Access/AccessType. Which got me
to thinking...
How does the "mixin" code handle defining the target for the
AnnotationInstances it creates?
Seems to me this code would have really no idea whether to choose the field
or the getter as the target. Which is potentially problematic as we are
validating the "placement" of these annotations.
Strong? Hardy?
Maybe we need to look at adding a virtual notion of the attribute as the
target in the virtual AnnotationInstance?
10 years, 9 months
Bytecode enhancement
by Guillaume Smet
Hi,
I took a look at the bytecode enhancement Maven plugin and I also have
this issue https://hibernate.atlassian.net/browse/HHH-8833 .
As far as I can tell the Maven plugin (and I suppose the Gradle plugin
too) doesn't provide any information about the classpath so it's
impossible to use the bytecode enhancement plugin in real life
applications because you obviously have dependencies to other classes.
Is this something supported or something very experimental? I found
some old posts of Emmanuel discouraging the use of bytecode
enhancement so I'm not sure it's a good idea to invest our time in it?
Basically, we have a lot of nullable @OneToOne properties and as far
as I understood it, it's supposed to help this case a lot.
Maybe using something like
http://www.mograblog.com/2010/01/setting-classloader-in-maven-plugin.html
might be a good idea for the Maven plugin?
Anyway feedback welcome before we invest time in it.
Thanks.
--
Guillaume
10 years, 9 months
