[
https://issues.jboss.org/browse/TEIID-2660?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on TEIID-2660:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug
1006961|https://bugzilla.redhat.com/show_bug.cgi?id=1006961] from VERIFIED to CLOSED
OData procedure issues
----------------------
Key: TEIID-2660
URL:
https://issues.jboss.org/browse/TEIID-2660
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.4.1, 8.5
Calling a procedure through Teiid's odata interface has several issues. First is
that joda time values are passed directly - which the runtime will not be able to convert
to analogous Teiid time types. Ultimately this appears as a classcastexception, which is
due to logic in the joda time AbstractPartial.compareTo method (which may be reported with
an erroneous message and seems odd in general, but is their way of saying the comparison
is invalid).
Another is that the logic assumes that the url will be called with the positional
ordering of the parameters preserved. We should use named parameters instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira