Looks like Hibernate-core 4.1.10.Final is missing from some repositories
and Hibernate-ehcache.4.1.0.Final from *all* repositories. Same goes for
hibernate-entitymanager. Shouldn't these versions be in sync?
Oops, did reply instead of reply-all
On 03/04/2013 07:23 AM, Steve Ebersole wrote:
> Personal preference I guess, but while developing major features I
> find it easier to keep track of my ongoing work that way
> On Mar 4, 2013 7:02 AM, "Emmanuel Bernard" <emmanuel(a)hibernate.org
> <mailto:firstname.lastname@example.org>> wrote:
> nice, I'll have a look. If I can squeeze a bit of OGM friendliness to
> the redesign, that would be a nice bonus.
> By the way, any reason to create a dedicated repo instead of a branch?
> I mistakenly imported your repo in my orm repo ;)
> On Mon 2013-02-25 13:19, Steve Ebersole wrote:
> > I believe something like the work I had in mind for
> > is the best option for implementing JPA 2.1 "entity graph"
> support into
> > Hibernate. To that end I have been working on that proposal to
> see how
> > quickly that could come about.
> > Essentially the phase we need to tie in "entity graph" support is a
> > redefinition of the current JoinWalkers. The approach I took,
> at a high
> > level, is that of the visitor pattern.
> > The work currently lives at
> > https://github.com/sebersole/hibernate-loader-redesign I'd
> > any extras eyes.
> > Longer term I'd like the stuff that lives in the
> > org.hibernate.loader.walking package to be part of the run time
> > (persister) metadata, but for the moment I just use wrapping and
> > delegation.
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org <mailto:email@example.com>
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
Have encryption capabilities in ORM ever been considered? There are a few 3rd party libraries, like Jasypt, providing UserTypes to handle encryption behind the scenes. Even basic support for an @Encrypt annotation, hashing, and configurable salt values would be helpful.
Red Hat Software Engineer, Hibernate
I believe something like the work I had in mind for
is the best option for implementing JPA 2.1 "entity graph" support into
Hibernate. To that end I have been working on that proposal to see how
quickly that could come about.
Essentially the phase we need to tie in "entity graph" support is a
redefinition of the current JoinWalkers. The approach I took, at a high
level, is that of the visitor pattern.
The work currently lives at
https://github.com/sebersole/hibernate-loader-redesign I'd appreciate
any extras eyes.
Longer term I'd like the stuff that lives in the
org.hibernate.loader.walking package to be part of the run time
(persister) metadata, but for the moment I just use wrapping and
when trying to use
in Hibernate Validator I get an UnsupportedClassVersionError.
Seems the API is compiled with JDK 7, which causes problems in the HV build.
Is the use of Java 7 intentional for the JPA API? I don't think it is required, right?
I noticed that org.hibernate.test.annotations.onetoone.OneToOneTest and OptionalOneToOnePKJCTest uses this mapping:
Son.father specifies a join-table ("father_son"), but has no <secondary-table>. There is no @SecondaryTable defined in Son (this is a unidirectional association).
I thought that @SecondaryTable was required when an association uses a join table. Currently, that's how it works in the new metamodel.
Should it be optional?