[ORM] EhCache 3 and JCache
by Emmanuel Bernard
Hello guys,
(I meant to send that almost a month ago, apologies Louis).
I’ve met Louis Jacomet from Ehcache at Devoxx France and we discussed how to restart the progress around JCache and EhCache 3 integration.
Louis is willing to step up to make these a reality but will need a bit of help to ramp up knowledge wise. Let me list the key subjects.
== JCache
I think Sanne has the info somewhere in his brain, what is the status of the current code? Any detail on what was missing? It would be nice to drive this one home.
== Ehcache 3
Ehcache 3 has been out recently and it would be nice to get an integration. The API is very different.
There are a few options:
1. make the JCache support extensible to build upon it and use Ehcache specific features when necessary or useful. Ehcache 3 is a JCache implementation.
2. create an new module dedicated to Ehcache 3 and go for it from scratch basically
3. change the Ehcache module and move it from v2 to v3
1. might be the conceptual nicest but it’s unclear how doable that is
2. vs 3. is about migration path for users and whether we consider it a “breaking change” in a 5.x series
== Doc and pointers
As I said, Louis know Ehcache well but needs some input to step into the magic world of second level caching in Hibernate ORM. Things like where is the code, how to test it, is there a doc or an example of a well written one etc.
Can someone give him a hand?
Emmanuel
8 years, 5 months
5.1 branch backporting
by Vlad Mihalcea
Hi,
I have backported some fixed to 5.1, and I'm not sure if that was the right
thing to do.
I know that for 5.0 we should ask Gail if to backport anything
Now that we moved to 5.2, should we also ask Gail when to backport
something to 5.1 too?
Vlad
8 years, 7 months
Code style question
by Vlad Mihalcea
Hi,
I'm currently using the IDEA code style from the GitHUb repo:
https://github.com/hibernate/hibernate-ide-codestyles
However, not all classes use the same styling, so which one is correct in
regards to Annotations parameters?
1. OnExpectedFailure
@Retention( RetentionPolicy.RUNTIME )
@Target( ElementType.METHOD )
public @interface OnExpectedFailure {
}
2. TestForIssue
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.METHOD, ElementType.TYPE })
public @interface TestForIssue {
/**
* The key of a JIRA issue tested.
* @return The jira issue key
*/
String jiraKey();
}
Thanks,
Vlad
8 years, 7 months
Is SQM going to remain a separate component?
by Gunnar Morling
Steve, all,
During the No-ORM meeting this week, Andrea gave us a great overview on the
current status of the SQM work (thanks again, Andrea!).
This looks awesome and we look forward to make use of it in Hibernate OGM.
One thing I'm wondering is how closely tied to Hibernate ORM 6 this will
be. Is the plan to move all the SQM bits into the hibernate-orm repo
eventually? Or will SQM remain a separate component, and only the
implementation of the type system will live in ORM?
The reason for asking is that I'm trying to gauge how feasible it'd be to
use SQM in a Hibernate OGM based on ORM 5.x. That'd be much simpler (or
even only actually doable without essentially copying code), if SQM would
remain separate, and we'd "only" have to copy/backport the type system
implementation.
Any thoughts?
Thanks,
--Gunnar
8 years, 7 months
Pushing 5.2 to next week (6/1)
by Steve Ebersole
5.2 had been slated to be released today (5/25). However based on the
"Ehcache 3 and JCache" discussion on this mailing list I have decided to
push releasing 5.2 to next week (6/1) to give time for this JCache to
finalize a bit. There is also a hibernate-osgi issue whose proposed fix
would be better to investigate a bit more.
8 years, 7 months
