Hello,
Really interesting question.
The answer is this jira issue: https://issues.apache.org/jira/browse/CAMEL-4555
and this diff:
http://mail-archives.apache.org/mod_mbox/camel-commits/201110.mbox/%3c20111022140442.94f362388...@eris.apache.org%3E
It would be really great if
1. the component wil
> https://issues.apache.org/jira/browse/CAMEL-8150
> (done).
> Btw nice catch with that tmp file :)
> Josef
> On 03/24/2015 09:19 PM, Sergey Zhemzhitsky wrote:
>> Hello,
>>
>> Really interesting question.
>> The answer is this jira issue:
&
Hi there,
> DomainName\\${user.username}
You should use single slash here.
DomainName\${user.username}
What OS are you using to run you camel route? win/*nix?
In case of Windows who started your app? What user does your application work
on behalf of?
Is this user (who started the app) domain use
Hello Joe,
1. Make sure that tomcat runs under non-domain user.
In case of domain users, you probably access your ntlm-protected service using
tomcat's user
(you could verify it easily by means of wireshark) due to credentials caching
inside jre.
2. Remote sec:Authorization from your conduit co
d jca resource
adapter
(http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/jca/) to achieve
"native" connection pooling
Regards,
Sergey Zhemzhitsky
> I have tested the fix in
> org.apache.qpid.client.AMQDestination.equals(), and
> now it works.
> I just made sure that no
If vm/seda component have multipleConsumers enabled, it creates a
thread pool to preconfigure MultiCastProcessor, and this processor has
parallelProcessing enabled and stopOnException disabled by default. So
if consuming endpoint fails to process exchange you will not know
about it in
Hello Aleksey,
Take a look at the following test
https://github.com/szhem/camel-osgi/blob/master/src/test/java/org/apache/camel/osgi/service/integration/OsgiDefaultEndpointTest.java.
testInstallUninstallBundle tests new bundle
installation/uninstallation and I've alre
Hello Michael,
To call the listeners asynchronously you can use the following uri:
osgi:multicast:myEndpoint?parallelProcessing=true. Here is some docs
aboutpredefinedparametersfor osgi:multicast producers:
https://github.com/szhem/camel-osgi#multicasting-to-multiple-osgi-bund
Hi Claus,
The component can be used right now without any additions, but I'd
like to include some integration tests which will check that:
1. Any camel processor (even not included into the camel route) can be
published into the OSGi service registry to process exchanges.
2. Multiple produce
Hi Claus,
Recently docs and integration tests of the component have been updated.
I suppose it's ready for now and all missing pieces and features can be added
later.
Regards,
Sergey
> On Wed, May 30, 2012 at 8:41 PM, Sergey Zhemzhitsky
> wrote:
>> Hi Claus,
>>
>
duce it in 2.10.1. We have done this in the past adding new
>> components to a patch release.
>>
>>
>>
>> On Sat, Jun 2, 2012 at 6:37 PM, Sergey Zhemzhitsky
>> wrote:
>>> Hi Claus,
>>>
>>> Recently docs and integration tests of the com
Hello Charles,
The component does not contain any transaction-specific or spring-specific
logic.
Handling of transactions should be done using transactional-client
(http://camel.apache.org/transactional-client.html) EIP.
Basically, if you need to call the consuming bundles in a transaction sta
Hello Christian,
Firstly I thought about some kind of indirect dependency on camel, but I
suppose that such
an indirection will complicate the component with copying of headers, bodies,
properties,
etc. from and to a camel exchange in case of duplication of camel exchange api
(lightweight analog
Hi Guillaume,
Of course if there is more convenient way to communicate between
bundles there is no need in the component. On the moment of development
of this component there were multiple ways to do that, for instance:
1. jms component which is rather heavyweight to do inter-bundle communication
;>> which can do some type of discovery (though the osgi implementation is
>>>> lacking a lot of stuff).
>>>> A simple one would at least be some kind of regular expression that
>>>> would match some endpoints. We may need something slightly more
>>>> spe
Hello,
FEFF - are the BOM(http://en.wikipedia.org/wiki/Byte_order_mark) bytes that are
used to identify bytes order for
UTF-16 encoding.
>> 1. How to set 'data_coding' manually without usign 'alphabet' parameter?
As far as I know component does not support such an option at the time.
> 2. How t
Hello Guillaume,
I suppose static method to retrieve consumers that can be filtered by a custom
expression will be quite enough.
Regards,
Sergey
> On Fri, Jun 22, 2012 at 6:33 AM, Sergey Zhemzhitsky
> wrote:
>> Hello, guys,
>>
>> I agree that if the camel-core coul
direct-vm:/parent/child")
> and for the expression, a simple xpath like:
> from("foo:bar").recipientList(directVm("/parent/*"))
> or
> /parent//*
> Just a thought though, not sure if that's really needed.
> On Sat, Jun 23, 2012 at 9:18 AM
Hi Camel Gurus,
I've faced with some performance issues of camel-kafka component during
migrating it from 2.17.0 then to 2.17.1 and then to 2.17.2.
The camel route is pretty simple and looks like this
from("file:/var/lib/app/input")
.split().simple("\n").streaming()
.to("direct:kafka
return next != null;
> }
> public byte[] next() {
> byte[] tmp = next;
> next = readNext();
> return tmp;
> }
> @Override
> public void remove() {
> }
> };
>
>
> On
20 matches
Mail list logo
