Hi Tim,
You’ll find an example of using REST DSL with the Servlet component and CDI
here:
https://github.com/apache/camel/tree/674b8cd2eb1f2c937121a62fc0ce8cb0df9a4c9f/examples/camel-example-cdi-rest-servlet
That uses the work done at https://github.com/astefanutti/camel-cdi that has
recently
I’m doing something like the code below
(IbmWebsphereDestinationResolver is something like the one attached to this
Jira ticket https://jira.spring.io/browse/SPR-3614)
==
@Configuration
@ComponentScan
public Class Config{
public void beforeApplicationStart(CamelContext camelContext) {
http://camel.apache.org/mailing-lists.html
> Am 27.01.2016 um 11:41 schrieb Kushagra Saxena :
>
> Hi,
>
> Please add me into the mailing list of camel.
>
> Regards,
> Kushagra
Hi Matt,
Still unable to make progress here. I have a simple SOAP 12 endpoint
defined, and this is working if I send a request.
@Endpoint
public class HeartbeatEndpoint {
@Action("http://myevent/Heartbeat";)
@ResponsePayload
p
Hi Nes,
SQL Camel Component is mapped with JdbcTemplate [1].
You could use "template.queryTimeout" URI parameter to set your timeout.
If it still doesn't work, feel free to rise an JIRA/issue
[1]
https://docs.spring.io/spring/docs/2.5.x/javadoc-api/org/springframework/jdbc/core/JdbcTemplate.ht
hello,
I have tried with the below route & filter configuration , its
works fine once , the filter is never called again after the first run .
Do i need to call the filter explicitly to start the poll again? Since in
my Filter I am getting the sequence from the Db always in the accep
Dears,
I am using the JPA component to persist some messages into a DB table on
which multiple JPA consumers will consume enrich to send them after in
aggregator.
The routes are expressed exclusively in XML (spring-camel). From the point
of view of the routes everything seems to work well.
To hel
I tried with a new approach it works atleast for basic condition . But the
problem is if there is any file left in the folder which did not match in
the Run , the route keeps on polling and the filter is called everytime .
1) Is there any way in which the route can be told to stop pooling after
I think in my case the problem was with how the package scan is working but
I'm not positive. In the Camel Core OSGi package scanner class there is a
section. If it can find it in OSGi it shrugs, throws up its hands and
resorts to brute force classloading. Instead of getting hard error Camel
was
By the way, while I realize this is in there for older JBI constructs this is
what I meant when asking if there is a way that a "strict" flag could be
added.
Perhaps that's a question I should post on the developers forum. Even if by
default the flag was false, being able to set it to true and
I got the defaultErrorHandler to collapse with these 2 adjustments:
- set messageHistory="false" on CONTEXT
- set logStackTrace="false" for onException block, like this:
The timestamp with default error handler still shows up, but much easier on
the eye.
I tried
but it makes no impac
1.Below Asynchoronus spring-ws application called from Camel.
http://camel.apache.org/schema/spring";>
http://www.example.com/fgh}Application?endpointMapping=#endpointMapping";
/>
A bit of an update. I changed the code to use control bus. The logs show that
control bus is signaling to the camel context to shut down, however when
inspecting the debug thread, the Camel JMSConsumer class is still running,
as shown below with 1 inflight and pending exchange. My processor logic w
Setting the logging level off works fine:
And also doTry/doCatch work: the exception won't go the the error handler
from the catch block.
But: it this a bug or a feature? I really don't like a behaviour that I
don't understand.
--
View this message in context:
http://camel.465427.n5.nabble
Hi,
We are using Camel-Swagger-Java v 2.16 for documenting the REST services
generated using CamelREST DSL.
We are able to integrate the swagger with the application and can get the
Swagger document laying down the full API specification.
The problem we are getting is in describing the Model in
Nice to meet you , everyone. from Japan
I want to construct servlet system with Camel.
the above is my image.
camel-servlet or camel-jetty receive HTTP Request.
Then, next Processor parse HTTP Request and forward another JSP or servlet.
But I have no idea about this way.
I tried to follow,
Thank you for your help, Gregoire.
I missed a template option.
I feel like I can implement a query timeout.
--
View this message in context:
http://camel.465427.n5.nabble.com/Does-Camel-SQL-Component-have-setQueryTimeout-tp5777088p5777126.html
Sent from the Camel - Users mailing list archive at
Hi,
I'm testing camel-rest with the folowing spring xml.
// <--- (1)
it can't work correctly with Accept header.
$ curl -H 'Accept:application/json' http://lo
You should use the rest-dsl which provides the rest functionality with
{} and get/post and so on.
The rest is not really intended to be used in regular routes, the
rest-dsl is the syntax sugar on top that uses the rest component under
the covers.
On Tue, Feb 2, 2016 at 7:47 AM, sogabe wrote:
>
Try upgrading to 2.16.2, we had some fixes in camel-swagger-java
On Tue, Feb 2, 2016 at 12:18 AM, ytatyaLij wrote:
> Hi,
>
> We are using Camel-Swagger-Java v 2.16 for documenting the REST services
> generated using CamelREST DSL.
> We are able to integrate the swagger with the application and ca
You cannot do that, you should likely use standard servlets if you
want to do servlet forwarding.
You can then from a servlet call Camel if you need to.
On Tue, Feb 2, 2016 at 7:34 AM, tko429 wrote:
> Nice to meet you , everyone. from Japan
>
> I want to construct servlet system with Camel.
>
>
Hi,
Thanks, I'll use rest-dsl.
>You should use the rest-dsl which provides the rest functionality
> with {} and get/post and so on.
>The rest is not really intended to be used in regular routes, the
> rest-dsl is the syntax sugar on top that uses the rest component under
> the covers.
--
Vi
22 matches
Mail list logo
