Hello,
Is there a way to disable CXF LoggingIntercepter both IN and OUT inside
the FUSE container. We have enabled the camel-cxf feature as we are using
REST. Though it keeps priting out the payload to the console; which we don't
want.
Any help would be appreciated.
Cheers!
Gaurav
Actually, after further experimenting, my "reconfgure" worked, but
only after the
CamelContext was started. So the implementation was to just have an initial
route consuming from a direct:, then, when an message comes in, I dynamically
create and add new routes, each headed by a unique instance of
So was (is) the root package supposed to be internal and "model" the
ideal external API?
I'm still not certain of the purpose of the "model" package
Thanks,
Chris
On Sat, May 18, 2013 at 3:33 AM, Claus Ibsen wrote:
> Hi
>
> Yeah its IMHO a bit unfortunate with the @deprecated on the
> Cam
Hi,
I am working on JSON marshalling/unmarshalling and need to exclude certain
POJO fields from marshalling.
I have referred to the following link:
http://camel.apache.org/json.html
It says that JSON View needs to be used.
And after that we need to specify the following in the java fi
Hi Christian,
the licence should be Eclipse. We are still working on the best home for Fuse
IDE - its part of the JBoss Developer Studio product - but it should have a
release, lifecycle of its own as open source project.
thanks,
Rob
On 18 May 2013, at 15:29, Christian Schneider wrote:
> Hi
Hi Rob,
thanks for the link this might be interesting for many people. The only
thing I am missing is a license statement.
I might have overlooked it but I did not find any license file in the tree.
Christian
Am 17.05.2013 20:48, schrieb Robert Davies:
Hi Mrinal - the src is here : https://g
The RouteBuilder is just java code, so I suggest to add getter/setter
to a MyCronRouteBuilder class which extends RouteBuilder. Then you can
create a new instance of that, and then use the setter to set your
options.
And in the configure method you can use the getter to get your
options, which you
Hi
Yeah its IMHO a bit unfortunate with the @deprecated on the
CamelContext. But the point was to use ModelCamelContext as this
interface is from the model package. Where as CamelContext is from the
root.
So with the ModelCamelContext you dont have root -> model in the
dependency triage.
On Fr
On Fri, May 17, 2013 at 1:03 PM, Peter Hilton wrote:
> On 17 May 2013, at 09:33, Claus Ibsen wrote:
>> You can use the move option on the Camel file consumer, and then use a
>> bean to calculate the file name. http://camel.apache.org/file2
>
> Claus, by the way, your comment let to an 'aha' momen
