He he, Gunnar welcome to Steve's suggestiveness :-)
Anyways, there is no reason not to compile with JDK 6. Maybe even worth
checking the build and making sure the right target level is used. I am looking
into it ...
--hardy
On 25 Feb 2013, at 19:26, Gunnar Morling wrote:
> > I never said 'no
I believe something like the work I had in mind for
https://github.com/hibernate/hibernate-orm/wiki/Proposal---Loader-redesign
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
Sure, its been discussed before. In numerous forms.
However, I am not sure exactly how a generic @Encrypt solution is
supposed to work. Not sure exactly what you are thinking here, so hard
to say.
On 02/25/2013 12:15 PM, Brett Meyer wrote:
> Have encryption capabilities in ORM ever been consi
> I never said 'no' I don't think :)
:-)
2013/2/25 Steve Ebersole
> I never said 'no' I don't think :)
>
>
>
> On Mon 25 Feb 2013 12:17:38 PM CST, Gunnar Morling wrote:
>
>> > 1) JPA 2.1 is part of EE 7 which requires SE 7
>>
>> But couldn't JPA 2.1 be used in 1.6 SE environments? I guess ther
I never said 'no' I don't think :)
On Mon 25 Feb 2013 12:17:38 PM CST, Gunnar Morling wrote:
> > 1) JPA 2.1 is part of EE 7 which requires SE 7
>
> But couldn't JPA 2.1 be used in 1.6 SE environments? I guess there'd
> be users doing this. Also if 1.6 is reaching its EOL there are lots of
> peopl
> 1) JPA 2.1 is part of EE 7 which requires SE 7
But couldn't JPA 2.1 be used in 1.6 SE environments? I guess there'd be
users doing this. Also if 1.6 is reaching its EOL there are lots of people
still using it. In BV the situation is similar, it is part of the EE 7 API,
but the BV spec (and thus
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.
Brett Meyer
Red Hat So
Was not really a conscious decision, but keep in mind that:
1) JPA 2.1 is part of EE 7 which requires SE 7
2) Oracle Java SE 6 is past any support.
And see the discussion that took place on this list over a year ago
about O/RM and the Java 6 javac bug
On 02/25/2013 04:07 AM, Hardy Ferentschik wr
Hi,
I'm working at the integration between OGM and Neo4j.
Neo4j is fully transactional and it requires to open a transaction
before the execution of any operation on the DB.
To integrate this mechanism with OGM I've created the class
Neo4jJtaPlatform.java[1] that extends AbstractJtaPlatform and it
Hi,
when trying to use
org.hibernate.javax.persistence
hibernate-jpa-2.1-api
1.0.0.Draft-10
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 do
10 matches
Mail list logo
