HI sergey, We are upgrading CXF version 2.7.7 to 3.1.8 and facing the below
issue.
AUDIT:2017-08-15 11:31:11.047:localhost-startStop-1:"Caused by
javax.ws.rs.ProcessingException: java.lang.IllegalStateException: Entity is
not available
at
We are also using some other jar , which is using javax.rs.ws 2.0-m10 . But
cxf 3.1.8 is not compatible with
javax.rs.ws 2.0-m10. what could be the solution?
--
View this message in context:
I am migrating my cxf version from 2.7.7 tp 3.1.8. Earlier i used javax rs ws
2.0-m10 version , but with cxf that version is not working and uodated to
2.0.1 . Later on i am facing this issue.
Caused by java.lang.ClassNotFoundException:
javax.ws.rs.client.ClientException
at
lt given of the few
> well-known side-effects.
>
> Given you have already tried to debug - it is better to set a breakpoint
> inside org.apache.cxf.jaxrs.impl.ResponseImpl - there you will see why
> InputStream is not available in your case
>
> Cheers, Sergey
>
> On 15/08/
16, 2017 at 2:29 PM, Sergey Beryozkin [via CXF] <
> ml+s547215n5782761...@n5.nabble.com> wrote:
>
>> So where is readEntity is called from ?
>> On 16/08/17 22:26, sbalustar wrote:
>>
>> > In CXF 3.1.8
>> >
>> > There is a call in readEntity m
Response () method
>> there is method call readBody (), in that method readEntity method is
>> called. After that there is another method call JAXRSUtils.fromRespons
>> which is calling getEntity method
>>
>>
>>
>> On Wed, Aug 16, 2017 at 2:29 PM, Sergey
se where response is read
> implicitly was not taken care of
>
> So if you'd do to continue doing the auto-closing just follow
>
> webCliemt.get().readEntity(Book.class) pattern
>
> in meantime I'll have a look at this property working in a
>
> webCliemt.get(Book.class)
&
Sergey Beryozkin [via CXF] <
> ml+s547215n578275...@n5.nabble.com> wrote:
>
>> Hi, that will need to be measured for a concrete flow.
>> I'm still not sure why you are seeing the failure with the auto close
>> being on - it only takes effect after the entity has
+s547215n578275...@n5.nabble.com> wrote:
> Hi, that will need to be measured for a concrete flow.
> I'm still not sure why you are seeing the failure with the auto close
> being on - it only takes effect after the entity has been consumed...
>
> Sergey
> On 16/08/
Beryozkin [via CXF] <
ml+s547215n5782761...@n5.nabble.com> wrote:
> So where is readEntity is called from ?
> On 16/08/17 22:26, sbalustar wrote:
>
> > In CXF 3.1.8
> >
> > There is a call in readEntity menthod autoClose(), but in cxf 2.7.7
> there
> > is no su
,
> Entity is not available Exception is throwing.
>
>
> On Thu, Aug 17, 2017 at 12:15 AM, Jose María Zaragoza [via CXF] <
> ml+s547215n5782769...@n5.nabble.com> wrote:
>
>> 2017-08-16 23:18 GMT+02:00 sbalustar <[hidden email]
>> <http:///user/SendEmail.j
calling
getEntity which is checking the entity is closed or not. If it is closed ,
Entity is not available Exception is throwing.
On Thu, Aug 17, 2017 at 12:15 AM, Jose María Zaragoza [via CXF] <
ml+s547215n5782769...@n5.nabble.com> wrote:
> 2017-08-16 23:18 GMT+02:00 sbalustar <[
12 matches
Mail list logo
