Re: camel-rest-starter vs camel-servlet-starter
I made it working by referencing apache/camel-spring-boot-examples
|
|
|
| | |
|
|
|
| |
apache/camel-spring-boot-examples
Apache Camel Spring Boot Examples. Contribute to
apache/camel-spring-boot-examples development by creating an ac...
|
|
|
.
Thank you,
On Tuesday, October 20, 2020, 05:21:57 PM EDT, Site Register
wrote:
Hi Camel Users,
Is camel-servlet-starter discontinued? The latest version I can find from maven
repository is 3.0.0-RC3.
I tried to use camel-rest component by using camel-servlet-starter 3.5.0.
However, I got below error from the browser when I tried to call the service
using "http://localhost:8080/hello;.
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as
a fallback.
Below is my simple route.
public void configure() throws Exception {
restConfiguration().host("localhost:8080");
from("rest:get:hello").transform().constant("Hello World");
}
Very appreciated if somebody can point me to the right direction.
Thank you
camel-rest-starter vs camel-servlet-starter
Hi Camel Users,
Is camel-servlet-starter discontinued? The latest version I can find from maven
repository is 3.0.0-RC3.
I tried to use camel-rest component by using camel-servlet-starter 3.5.0.
However, I got below error from the browser when I tried to call the service
using "http://localhost:8080/hello;.
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as
a fallback.
Below is my simple route.
public void configure() throws Exception {
restConfiguration().host("localhost:8080");
from("rest:get:hello").transform().constant("Hello World");
}
Very appreciated if somebody can point me to the right direction.
Thank you
[ANNOUNCE] Apache Camel 3.6.0 Released
The Camel PMC is pleased to announce the release of Apache Camel 3.6.0. Apache Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data. This patch release contains 151 bug fixes and improvements. The release is available for immediate download at: https://camel.apache.org/download/ For more details please take a look at the release notes at: https://camel.apache.org/releases/release-3.6.0/
RE: multiple consumers with ahc-ws component
Thanks Claus, Jira is created! https://issues.apache.org/jira/browse/CAMEL-15716 -Message d'origine- De : Claus Ibsen Envoyé : mardi 20 octobre 2020 06:43 À : users@camel.apache.org Objet : Re: multiple consumers with ahc-ws component On Mon, Oct 19, 2020 at 11:32 PM CASAUX Nicolas wrote: > > Hi Claus, > > I'm trying another component like you suggested, the new vertex-websocket > component. > I'm struggling with setting a stomp over websocket connection with the > ActiveMQ. > > Netty keeps saying this: > Caused by: > io.netty.handler.codec.http.websocketx.WebSocketHandshakeException: > Invalid subprotocol. Actual: stomp. Expected one of: null > > I can't find where I could set-up the subprotocol value where I'd like to put > "stomp", or "v12.stomp" etc... > I can see in Netty source code that there are constructors which takes this > subprotocol as a parameter, but I can't find (if it's possible) where I could > pass this value from Camel. > I looked into the vertxOptions of the component, but I couldn't find... > > Any hint on this ? > Thanks ! > Can you create a JIRA about this? And put in details where in netty you found that place to put in sub protocol. Then we can better help and find a solution for this, as it would be great if the vertx based ws component would work with AMQ. > Regards, > Nicolas > > -Message d'origine- > De : Claus Ibsen Envoyé : samedi 17 octobre > 2020 17:48 À : users@camel.apache.org Objet : Re: multiple consumers > with ahc-ws component > > Hi > > There are a few other camel websocket components you can try also. > > On Sat, Oct 17, 2020 at 1:19 AM CASAUX Nicolas > wrote: > > > > Hello ! > > > > I have a requirement to open multiple websocket connections to an ActiveMQ > > broker. > > As far as I understand, the only (?) Camel component for this is the ahc-ws > > component. > > > > I managed to use it, however I can't open more than 1 connection to the > > ActiveMQ, because I encounter a "already have a consumer" error on this > > endpoint when I try to open one more connection, which makes sense. > > I already tried to use things like "from(ahc-ws://dummy)" and the > > Exchange.HTTP_URI header, but the component seems to ignore this header and > > it fails with a "java.net.UnknownHostException: (dummy)" error. > > > > Any idea how could I achieve that ? > > > > Thanks in advance! > > > > Nicolas > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
AW: Camel .toD() adding extra CamelHttpPath to target URL?
Hi Claus.
Thanks for your answer.
Actually I tried that already while waiting for an answer - I emptied it, but
felt a bit naughty. Didn't know if that’s the proper way to do it.
Lars
-Ursprüngliche Nachricht-
Von: Claus Ibsen
Gesendet: Dienstag, 20. Oktober 2020 15:07
An: users@camel.apache.org
Betreff: Re: Camel .toD() adding extra CamelHttpPath to target URL?
Hi
If you do some from http to http proxy thingy, then it can often make better to
remove existing CamelHttp headers before calling to / toD to clear those from
interfering. There was a FAQ about this on the old website, not sure if it was
migrated to the new.
On Tue, Oct 20, 2020 at 2:50 PM Lars Schaps wrote:
>
> Hello Maillinglist
>
> I have a question/problem regarding the .toD feature to dynamically
> set the endpoint for the http(s) protocol
>
> In my example call I have
>
> .toD("${exchangeProperty.rewrite}")
>
> With rewrite set to
>
> https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/?th
> rowExceptionOnFailure=false=1
> .socketTimeout=1=true=mySSLCon
> textParameters
>
> The command
>
>.to("log:INFO?showBody=true=true");
>
> after the .toD() is showing me following output:
>
> 2020-10-20 13:23:57,143 [T:http-nio-8080-exec-3, C:test] INFO |
> Exchange[ExchangePattern: InOut, Headers: {accept=*/*,
> accept-encoding=gzip,deflate, CamelHttpCharacterEncoding=ISO-8859-1,
> CamelHttpMethod=POST, CamelHttpPath=/au/offerDate,
> CamelHttpResponseCode=301, CamelHttpResponseText=X RealURL redirect,
> CamelHttpServletRequest=org.apache.catalina.connector.RequestFacade@12dcf186,
>
> CamelHttpServletResponse=org.apache.catalina.connector.ResponseFacade@180c0467,
> CamelHttpUri=/proxy/v2/reminder/au/offerDate,
> CamelHttpUrl=http://exampledomain/proxy/v2/reminder/au/offerDate,
> CamelServletContextPath=/v2/reminder, Connection=keep-alive,
> Content-Length=0, Content-Type=text/html; charset=UTF-8, Date=Tue, 20 Oct
> 2020 11:23:57 GMT, Location=https://exampledomain/en/reminder-webservice-
>v2/reminder/offerDate/au/offerDate/, Server=nginx,
> Strict-Transport-Security=max-age=31536000, X-Content-Type-Options=nosniff,
> X-TYPO3-RealURL-Info=redirect for missing slash, X-XSS-Protection=1;
> mode=block}, BodyType:
> org.apache.camel.converter.stream.CachedOutputStream.WrappedInputStream,
> Body: [Body is instance of java.io.InputStream]]
>
> I expect the target host to receive a request
>
>
> https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/
>
> like it was set via .toD(), but instead it receives (like in
> "Location" of the log message)
>
>
> https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/au/
> offerDate/
>
> with an extra
>
>au/offerDate
>
> Which causes trouble.
>
> What am I doing wrong and how can I fix this?
>
> Camel 3.4.3
> Tomcat 8.5
> Java 8 openjdk
>
> Kind regards
> Lars
>
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
smime.p7s
Description: S/MIME cryptographic signature
Camel documentation question
Hello! As I could remember there was a section on the old camel website about using activeMQ destination options Is there a reason for not to have it now? Camel AMQ component - https://camel.apache.org/components/latest/activemq-component.html AMQ destination options - https://activemq.apache.org/destination-options Thanks!
Re: Camel .toD() adding extra CamelHttpPath to target URL?
Hi
If you do some from http to http proxy thingy, then it can often make
better to remove existing CamelHttp headers before calling to / toD to
clear those from interfering. There was a FAQ about this on the old
website, not sure if it was migrated to the new.
On Tue, Oct 20, 2020 at 2:50 PM Lars Schaps wrote:
>
> Hello Maillinglist
>
> I have a question/problem regarding the .toD feature to dynamically set the
> endpoint for the http(s) protocol
>
> In my example call I have
>
> .toD("${exchangeProperty.rewrite}")
>
> With rewrite set to
>
> https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/?throwExceptionOnFailure=false=1=1=true=mySSLContextParameters
>
> The command
>
>.to("log:INFO?showBody=true=true");
>
> after the .toD() is showing me following output:
>
> 2020-10-20 13:23:57,143 [T:http-nio-8080-exec-3, C:test] INFO |
> Exchange[ExchangePattern: InOut, Headers: {accept=*/*,
> accept-encoding=gzip,deflate, CamelHttpCharacterEncoding=ISO-8859-1,
> CamelHttpMethod=POST, CamelHttpPath=/au/offerDate,
> CamelHttpResponseCode=301, CamelHttpResponseText=X RealURL redirect,
> CamelHttpServletRequest=org.apache.catalina.connector.RequestFacade@12dcf186,
>
> CamelHttpServletResponse=org.apache.catalina.connector.ResponseFacade@180c0467,
> CamelHttpUri=/proxy/v2/reminder/au/offerDate,
> CamelHttpUrl=http://exampledomain/proxy/v2/reminder/au/offerDate,
> CamelServletContextPath=/v2/reminder, Connection=keep-alive,
> Content-Length=0, Content-Type=text/html; charset=UTF-8, Date=Tue, 20 Oct
> 2020 11:23:57 GMT, Location=https://exampledomain/en/reminder-webservice-
>v2/reminder/offerDate/au/offerDate/, Server=nginx,
> Strict-Transport-Security=max-age=31536000, X-Content-Type-Options=nosniff,
> X-TYPO3-RealURL-Info=redirect for missing slash, X-XSS-Protection=1;
> mode=block}, BodyType:
> org.apache.camel.converter.stream.CachedOutputStream.WrappedInputStream,
> Body: [Body is instance of java.io.InputStream]]
>
> I expect the target host to receive a request
>
>https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/
>
> like it was set via .toD(), but instead it receives (like in "Location" of
> the log message)
>
>
> https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/au/offerDate/
>
> with an extra
>
>au/offerDate
>
> Which causes trouble.
>
> What am I doing wrong and how can I fix this?
>
> Camel 3.4.3
> Tomcat 8.5
> Java 8 openjdk
>
> Kind regards
> Lars
>
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Camel .toD() adding extra CamelHttpPath to target URL?
Hello Maillinglist
I have a question/problem regarding the .toD feature to dynamically set the
endpoint for the http(s) protocol
In my example call I have
.toD("${exchangeProperty.rewrite}")
With rewrite set to
https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/?throwExceptionOnFailure=false=1=1=true=mySSLContextParameters
The command
.to("log:INFO?showBody=true=true");
after the .toD() is showing me following output:
2020-10-20 13:23:57,143 [T:http-nio-8080-exec-3, C:test] INFO |
Exchange[ExchangePattern: InOut, Headers: {accept=*/*,
accept-encoding=gzip,deflate, CamelHttpCharacterEncoding=ISO-8859-1,
CamelHttpMethod=POST, CamelHttpPath=/au/offerDate,
CamelHttpResponseCode=301, CamelHttpResponseText=X RealURL redirect,
CamelHttpServletRequest=org.apache.catalina.connector.RequestFacade@12dcf186,
CamelHttpServletResponse=org.apache.catalina.connector.ResponseFacade@180c0467,
CamelHttpUri=/proxy/v2/reminder/au/offerDate,
CamelHttpUrl=http://exampledomain/proxy/v2/reminder/au/offerDate,
CamelServletContextPath=/v2/reminder, Connection=keep-alive, Content-Length=0,
Content-Type=text/html; charset=UTF-8, Date=Tue, 20 Oct 2020 11:23:57 GMT,
Location=https://exampledomain/en/reminder-webservice-
v2/reminder/offerDate/au/offerDate/, Server=nginx,
Strict-Transport-Security=max-age=31536000, X-Content-Type-Options=nosniff,
X-TYPO3-RealURL-Info=redirect for missing slash, X-XSS-Protection=1;
mode=block}, BodyType:
org.apache.camel.converter.stream.CachedOutputStream.WrappedInputStream, Body:
[Body is instance of java.io.InputStream]]
I expect the target host to receive a request
https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/
like it was set via .toD(), but instead it receives (like in "Location" of the
log message)
https://exampledomain/en/reminder-webservice-v2/reminder/offerDate/au/offerDate/
with an extra
au/offerDate
Which causes trouble.
What am I doing wrong and how can I fix this?
Camel 3.4.3
Tomcat 8.5
Java 8 openjdk
Kind regards
Lars
Re: ApacheCon @Home 2020 videos have been published
Great, thanks Zoran! On Tue, Oct 20, 2020 at 8:19 AM Zoran Regvart wrote: > > Hi Cameleers, > in case you missed some of the sessions at this year's ApacheCon or > wish to revisit some of them you can now watch on demand on The Apache > Software Foundation YouTube channel: > > https://www.youtube.com/c/TheApacheFoundation/ > > We have a blog post linking to slides that we got from speakers: > > https://camel.apache.org/blog/2020/10/ApacheCon-at-Home-videos/ > > Share and enjoy! > > zoran > -- > Zoran Regvart
ApacheCon @Home 2020 videos have been published
Hi Cameleers, in case you missed some of the sessions at this year's ApacheCon or wish to revisit some of them you can now watch on demand on The Apache Software Foundation YouTube channel: https://www.youtube.com/c/TheApacheFoundation/ We have a blog post linking to slides that we got from speakers: https://camel.apache.org/blog/2020/10/ApacheCon-at-Home-videos/ Share and enjoy! zoran -- Zoran Regvart
