[teiid-issues] [JBoss JIRA] (TEIID-4867) Loosen up OData4 URL validation or parsing

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398789#comment-13398789 ] 

Ramesh Reddy commented on TEIID-4867:
-------------------------------------

[~dsteigne] and [~jolee] upgrade the Olingo library version to "4.2.0-teiid-8" for the fix for JDV 6.3

> Loosen up OData4 URL validation or parsing
> ------------------------------------------
>
>                 Key: TEIID-4867
>                 URL: https://issues.jboss.org/browse/TEIID-4867
>             Project: Teiid
>          Issue Type: Bug
>          Components: OData
>    Affects Versions: 8.12.8.6_3
>         Environment: JDV 6.3.2
> Windows 7
>            Reporter: Steve Tran
>            Assignee: Steven Hawkins
>
> I'm accessing my JDV table via OData4 through Salesforce's UI builder.  The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind.  That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
> The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is.  The thing is when I tested it via the OData2 interface, it accepted it just fine.  I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug.  Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)