[
https://issues.apache.org/jira/browse/OPENJPA-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998867#comment-12998867
]
Kevin Sutter commented on OPENJPA-1951:
---------------------------------------
Hi. Even though OpenJPA 2.1.x is built with Java 6, it *should* still run okay
with Java 5. You won't have access to the MetaModel annotation processor (code
generation), but that wouldn't be new for your environment. I am in the
process of updating this old article [1] to explain how to use OpenJPA 2.x in
WebSphere v6.1 environment (non-managed, of course) and I have not had any
problems running the samples and tests in this environment. The updated
article should be posted soon on Developer Works.
I'm not trying to justify not fixing this in OpenJPA 2.0.x, but I thought I
would let you know that I think the OpenJPA 2.1.x driver would work for you as
well.
[1]
http://www.ibm.com/developerworks/websphere/techjournal/0612_barcia/0612_barcia.html
> missing key "cant-set-value" in localizer properties
> org.apache.openjpa.jdbc.meta.strats
> ----------------------------------------------------------------------------------------
>
> Key: OPENJPA-1951
> URL: https://issues.apache.org/jira/browse/OPENJPA-1951
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.1
> Reporter: Vedran Vidović
>
> Key cant-set-value is missing in properties file
> org.apache.openjpa.jdbc.meta.strats in openjpa-jdbc-2.0.1.jar so we don't get
> descriptive message in case this exception occurs.
> To reproduce it set some field as not nullable in jpa and try to update it
> with null value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
