[
https://issues.jboss.org/browse/TEIID-3297?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-3297:
--------------------------------
Description:
{code}
ArrayList contentTypes = (ArrayList)this.responseContext.get("content-type");
//$NON-NLS-1$
String contentType = contentTypes != null ?
(String)contentTypes.get(0):"application/octet-stream"; //$NON-NLS-1$
{code}
Looking at
http://stackoverflow.com/questions/20392345/is-content-type-http-header-a... it
is not always required but recommended. In the DV it is more required because, based on
this it will to build the object of that type. What is missing is NPE handling there.
was:
{code}
ArrayList contentTypes =
(ArrayList)this.responseContext.get("content-type"); //$NON-NLS-1$
String contentType = contentTypes != null ?
(String)contentTypes.get(0):"application/octet-stream"; //$NON-NLS-1$
{code}
Looking at
http://stackoverflow.com/questions/20392345/is-content-type-http-header-a... it
is not always required but recommended. In the DV it is more required because, based on
this it will to build the object of that type. What is missing is NPE handling there.
Possible NPE in WSConnectionImpl
--------------------------------
Key: TEIID-3297
URL:
https://issues.jboss.org/browse/TEIID-3297
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.10
{code}
ArrayList contentTypes = (ArrayList)this.responseContext.get("content-type");
//$NON-NLS-1$
String contentType = contentTypes != null ?
(String)contentTypes.get(0):"application/octet-stream"; //$NON-NLS-1$
{code}
Looking at
http://stackoverflow.com/questions/20392345/is-content-type-http-header-a... it
is not always required but recommended. In the DV it is more required because, based on
this it will to build the object of that type. What is missing is NPE handling there.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)