cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iris ding <irisdin...@gmail.com>
Subject Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider
Date Tue, 01 Jul 2014 02:30:10 GMT
Johan,

Can I know the reason for your point?

Actually, the key reason for the issue 2 is not for available() usage. Let
me give an example for this issue:

If you deploy your application to Tomcat, the incomming InputStream might be
a tomcat class which implements ServletInputStream.

If you deploy your application to WebSphere, the incoming InputStream might
be a websphere specific class which implements ServletInputStream.

In other case, the incomming InputStream might be some other class which
implements InputStream directly. 

In such case if we do not do conversion and return the original incomming
InputStream, Users will loose control of it. He might need to use specific
API to operate the different stream.

Iris Ding 



--
View this message in context: http://cxf.547215.n5.nabble.com/two-issues-in-org-apache-cxf-jaxrs-provider-DataSourceProvider-tp5745783p5745788.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Mime
View raw message