[
https://issues.apache.org/jira/browse/OPENJPA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-990:
---------------------------------
Attachment: OPENJPA-990_20090326.patch
Updated patch that
1) fixes the localizer.properties bug mentioned by Jeremy.
2) No changes to the exception type being created in FetchConfigurationImpl, as
openjpa-kernel code does not have access to the ArgumentException class in
openjpa-persistence and the exception is being coverted to a ArgumentException
type by the HintHandler -
107 test TRACE [main] Tests - testQueryTimeout5() - Caught expected
Exception = <openjpa-2.0.0-SNAPSHOT-r422266:758490M nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Invalid value specified for
query hint "javax.persistence.query.timeout": -2,000
> setHint should return IllegalArgumentException for invalid query/lock timeout
> values
> ------------------------------------------------------------------------------------
>
> Key: OPENJPA-990
> URL: https://issues.apache.org/jira/browse/OPENJPA-990
> Project: OpenJPA
> Issue Type: Sub-task
> Components: query
> Affects Versions: 2.0.0
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-990.patch, OPENJPA-990_20090326.patch
>
>
> JPA2 spec notes that Query.setHint() should throw a IllegalArgumentException
> if a supplied hint value is not valid for a given implementation.
> For lock/query timeout, any user supplied value < -1 is invalid and should
> throw an exception, which is not occurring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
