Re: Empty stream for gzipped response

2023-01-18 Thread Claus Ibsen
On Tue, Jan 17, 2023 at 3:16 PM Dmitri T  wrote:

> Sure.
> The Server is jetty from camel-jetty.
> Message body is:
> org.apache.camel.converter.stream.InputStreamCache for
> exchange.getIn().getBody() (empty)
> org.apache.camel.converter.stream.ByteArrayInputStreamCache for
> message.getBody() (not empty)
>
>
Thanks for reporting this. You are welcome to create a JIRA so we can work
on a fix.
I think we need to check for StreamCache in that part of the code.



> вт, 17 янв. 2023 г. в 16:59, Claus Ibsen :
> >
>




> > Hi
> >
> > Thanks for reporting. Can you tell a bit more about what HTTP server you
> > are using? And what class type the message body is at that moment in
> > doWriteGZIPResponse?
> > If the body is not an instance of InputStream then what type is that body
> > of yours?
> >
> >
> > On Tue, Jan 17, 2023 at 1:03 PM Dmitri T  wrote:
> >
> > > Hello.
> > > After upgrading from Camel 3.7.x to the recent version, gzipped
> > > response (Content-Encoding: gzip) from a route comes empty. I have
> > > found an issue CAMEL-13092 (fixed in Camel 3.10) which caused that in
> > >
> > >
> camel-http-common/src/main/java/org/apache/camel/http/common/DefaultHttpBinding.java
> > > (line 602 doWriteGZIPResponse method): Object body =
> > > exchange.getIn().getBody();
> > > I debugged and found. that stream was not empty, if that line was
> > > replaced by Object body = message.getBody(InputStream.class);, like it
> > > was done for plain non-gzipped response in doWriteDirectResponse
> > > method.
> > > I have tested this change with ServletStreamingGzipChunkedTest
> > > successfully.
> > > Is this an issue and could be fixed in the next Camel release?
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Best regards,
> Dmitri
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2


Camel 3.X / camel-infinispan feature

2023-01-18 Thread Ephemeris Lappis
Hello.

If I'm not wrong, the feature camel-infinispan is not found in the
feature repository of version 3.20.1.

Is it another deprecated component of 3.X ?

Thanks.

Regards.


Re: Camel 3.X / camel-infinispan feature

2023-01-18 Thread Andrea Cosentino
Hello,

The Karaf feature has been removed in 3.3.0

https://github.com/apache/camel-karaf/commit/57e67fc48fbd4e197d4715b8cfcee791d3394ea2

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, January 18, 2023 at 01:40:41 PM GMT+1, Ephemeris Lappis 
 wrote: 





Hello.

If I'm not wrong, the feature camel-infinispan is not found in the
feature repository of version 3.20.1.

Is it another deprecated component of 3.X ?

Thanks.

Regards.


Re: Camel 3.X / camel-infinispan feature

2023-01-18 Thread Ephemeris Lappis
Hello.

Bad news :( ! Thanks anyway for your answer...

What do you suggest to restore Infinispan core features ? We don't
really need the camel component but we have OSGi services that need
these features.

Thanks again.

Regards.

Le mer. 18 janv. 2023 à 13:46, Andrea Cosentino
 a écrit :
>
> Hello,
>
> The Karaf feature has been removed in 3.3.0
>
> https://github.com/apache/camel-karaf/commit/57e67fc48fbd4e197d4715b8cfcee791d3394ea2
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Wednesday, January 18, 2023 at 01:40:41 PM GMT+1, Ephemeris Lappis 
>  wrote:
>
>
>
>
>
> Hello.
>
> If I'm not wrong, the feature camel-infinispan is not found in the
> feature repository of version 3.20.1.
>
> Is it another deprecated component of 3.X ?
>
> Thanks.
>
> Regards.


Re: Camel 3.X / camel-infinispan feature

2023-01-18 Thread Andrea Cosentino
I would probably create a feature with what I need from Infinispan and use that.

Also it depends from what version you're going to use (of Infinispan). From a 
particular version they choose to drop OSGi support, so you might need to wrap 
their JARs.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, January 18, 2023 at 02:11:07 PM GMT+1, Ephemeris Lappis 
 wrote: 





Hello.

Bad news :( ! Thanks anyway for your answer...

What do you suggest to restore Infinispan core features ? We don't
really need the camel component but we have OSGi services that need
these features.

Thanks again.

Regards.

Le mer. 18 janv. 2023 à 13:46, Andrea Cosentino
 a écrit :
>
> Hello,
>
> The Karaf feature has been removed in 3.3.0
>
> https://github.com/apache/camel-karaf/commit/57e67fc48fbd4e197d4715b8cfcee791d3394ea2
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Wednesday, January 18, 2023 at 01:40:41 PM GMT+1, Ephemeris Lappis 
>  wrote:
>
>
>
>
>
> Hello.
>
> If I'm not wrong, the feature camel-infinispan is not found in the
> feature repository of version 3.20.1.
>
> Is it another deprecated component of 3.X ?
>
> Thanks.
>
> Regards.