Back to bug 1023994
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Gary Hu | 2013-10-28 14:28:03 UTC | Priority | unspecified | high |
| Target Release | --- | EAP 6.3.0 | ||
| Brett Meyer | 2013-10-28 14:39:05 UTC | Priority | high | low |
| Status | NEW | ASSIGNED | ||
| Version | TBD EAP 6 | 6.1.0 | ||
| Severity | high | low | ||
| Brett Meyer | 2013-10-28 16:52:22 UTC | Status | ASSIGNED | POST |
| Doc Text | HHH-8643 https://hibernate.atlassian.net/browse/HHH-8643 In a JPA Query, setting a TemporalType.DATE or TemporalType.TIMESTAMP parameter should be able to use a Calendar *or* a Date value. Hibernate EntityManager attempts to validate the parameter type and its given value. The interchangeability was broken, throwing an IllegalArgumentException. |
|||
| Brett Meyer | 2013-10-30 14:20:15 UTC | Blocks | 1024864 | |
| Brett Meyer | 2014-02-10 16:20:15 UTC | Blocks | 1063408 | |
| Brett Meyer | 2014-03-05 19:40:32 UTC | Target Milestone | --- | DR2 |
| Kabir Khan | 2014-04-04 15:28:35 UTC | Status | POST | ON_QA |
| CC | kkhan | |||
| Jan Martiska | 2014-04-16 10:11:37 UTC | Status | ON_QA | VERIFIED |
| CC | jmartisk | |||
| Scott Mumford | 2014-04-28 02:45:40 UTC | CC | smumford | |
| Doc Text | HHH-8643 https://hibernate.atlassian.net/browse/HHH-8643 In a JPA Query, setting a TemporalType.DATE or TemporalType.TIMESTAMP parameter should be able to use a Calendar *or* a Date value. Hibernate EntityManager attempts to validate the parameter type and its given value. The interchangeability was broken, throwing an IllegalArgumentException. | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a <literal>TemooralType.DATE</literal> or <literal>TemporalType.TIMESTAMP</literal> parameter in a JPA query. The parameter is intended to be able to use a Calendar or a Date value, however this interchangeability did not operate as expected in an earlier version of EAP. The issue has now been corrected and the exception no longer presents when using <literal>TemporalType</literal> parameters in queries. | ||
| Scott Mumford | 2014-05-13 00:14:54 UTC | CC | sgilda | |
| Doc Text | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a <literal>TemooralType.DATE</literal> or <literal>TemporalType.TIMESTAMP</literal> parameter in a JPA query. | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a `TemooralType.DATE` or `TemporalType.TIMESTAMP` parameter in a JPA query. The parameter is intended to be | ||
| Doc Text | The parameter is intended to be able to use a Calendar or a Date value | able to use a Calendar or a Date value, however this interchangeability did not operate as expected in an earlier version of EAP. The issue has now been corrected and the exception no longer presents when using `TemporalType` parameters in queries. | ||
| Doc Text | , however this interchangeability did not operate as expected in an earlier version of EAP. The issue has now been corrected and the exception no longer presents when using <literal>TemporalType</literal> parameters in queries. | |||
| Doc Text | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a `TemooralType.DATE` or `TemporalType.TIMESTAMP` parameter in a JPA query. The parameter is intended to be able to use a Calendar or a Date value, however this interchangeability did not operate as expected in an earlier version of EAP. The issue has now been corrected and the exception no longer presents when using `TemporalType` parameters in queries. | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a `TemooralType.DATE` or `TemporalType.TIMESTAMP` parameter in a JPA query. The parameter is intended to be able to use a Calendar or a Date value, however this interchangeability did not operate as expected. The issue has now been corrected and the exception no longer presents when using `TemporalType` parameters in queries. | ||
| Scott Mumford | 2014-06-30 02:35:35 UTC | Doc Text | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an IllegalArgumentException to be thrown when setting a `TemooralType.DATE` or `TemporalType.TIMESTAMP` parameter in a JPA query. The parameter is intended to be able to use a Calendar or a Date value, however this interchangeability did not operate as expected. The issue has now been corrected and the exception no longer presents when using `TemporalType` parameters in queries. | This release of JBoss EAP 6 contains a fix to a bug in the Hibernate component that caused an `IllegalArgumentException` to be thrown when setting a `TemooralType.DATE` or `TemporalType.TIMESTAMP` parameter in a JPA query. The parameter is intended to be able to use a Calendar or a Date value, however this interchangeability did not operate as expected. The issue has now been corrected and the exception no longer presents when using `TemporalType` parameters in queries. |
| Pavel Slavicek | 2014-08-06 14:38:43 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-08-06 10:38:43 UTC | |||
| John Skeoch | 2015-09-01 04:00:34 UTC | CC | theute |
Back to bug 1023994