ity header of the CXF message
> in CxfHeaderFilterStrategy.
> You can configure your own HeaderFilterStrategy by extends the
> CxfHeaderFilterStrategy.
>
>
> On 6/14/11 10:37 AM, ext2 wrote:
> >
> > Hi:
> >
> > Following is a simple sayHello Webservice
ity header of the CXF message
> in CxfHeaderFilterStrategy.
> You can configure your own HeaderFilterStrategy by extends the
> CxfHeaderFilterStrategy.
>
>
> On 6/14/11 10:37 AM, ext2 wrote:
> >
> > Hi:
> >
> > Following is a simple sayHello Webservice
Hi:
Following is a simple sayHello Webservice implemented by camel.
The webservice's request is configured to decrypt by server
certificate and response is configured to encrypt by client certificate.
If I use a bean as following, every thing is ok
s
nothing to do with camel;
Thanks
> -original -
> Sender: ext2 [mailto:x...@tongtech.com]
> Date: 2011/6/8 11:09
> Receiver: users@camel.apache.org
> Subject: Re: A problem of XSLT
>
> Hi, Jiang:
> I just got the answer from apache xalan mail-list. You can check it;
MSource
>If your xpath expressions starts with '/' e.g. '/Records/Record' then you
need >a document If you are
>transforming a "sub" element you cannot start with '/' e.g. '/Record' but
must >use 'Record'
>Best regards
Hi:
Recently I am using camel xslt to do xml transform;
If the xslt processor's input is a xml string, the transform result is
correct;
But if the xslt processor's input is a org.w3c.xml.Node which is build from
the exactly same xml string; then thing's will be very strange:
If I using the lat
ations, then a
content
> >> based router in front of this should do niely.
> >>
> >> On Fri, May 20, 2011 at 8:18 AM, Taariq Levack
wrote:
> >>
> >>> Have you looked at the Validation component?
> >>> http://ca
Using camel's in:header() xpath function, we can deal with xml stored in
message header very easy; for example:
in:header('bookstore')/child::book[price<100]
The setHeader could retrieve all cheaper books(price less than 100) from a
bookstore xml (which already
I am using cxf component to proxy one webservce to another.
The route's logical is very simple: receiving the soap-xml, transform the
soap xml element(if the wsdls of two webservice are not exactly same), then
send the transformed xml to another webservice;
But unfortunately in camel, this is n
? I try
to check the source code of camel, but still know nothing about this;
On Fri, Apr 1, 2011 at 9:20 AM, ext2 wrote:
>
>
> Hi:
> With spring, caml processors may depend on many beans. Could c
Hi:
With spring, caml processors may depend on many beans. Could camel
will ensure the camelcontext will be destroy before all the dependencies
while spring context is destroy?
Hi, Camel:
I have raised a JIRA for the question;
Hi, Camel:
I have raised a issue to show it more clearly using source code
https://issues.apache.org/jira/browse/CAMEL-3438
major changes exists in the JAXBDataFormatter .getContext() method
===
Hi，Camel：
Camel's JAXBDataFormatter using Thread.contextClassLoader() to
create JAXBContext;
It's suspiciously, I think it's bug;
Spring DM (from 1.2.0)'s extender will using a separate Thread to
loading spring configures; In this thread, the thread's context ClassLoader
wi
Hi,TheWinch:
I am using JAXB in osgi too, it seems I haven't encounter such a
problem; But I really want know what's exactly problem you have.
And could you help me to send you project to my private mail, if you
don't mind?
If you cannot sent , could you help me to tell som
Hi, sharma_arun_se:
Where do you deploy the JAXBContextResolver class?
Deploy it in the same bundle of camel route?
In the generated jaxb object's bundle?
Or in a separate bundle?
Thanks a lot
-origin -
Sender: sharma_arun_se [mailto:arun.kaun...@gmail.com]
Date: 2010/12/17 14:05
Rece
Gi service
registry, it doesn't support the filter.
I think this feature is easy to add and please don't hesitate to
contribute your patch.
On 12/16/10 7:25 PM, ext2 wrote:
> Camel Osgi registry doesn't support filter for services;
>
> You'd better write your own proc
Camel Osgi registry doesn't support filter for services;
You'd better write your own processor to locate osgi services; it's not so
sophisticated , just do some reflecting works;
But if you do wish to use camel bean's features, the only way I know is
change the source code of CamelOsgiRegistry t
Yes, camel 's OSGIServiceRegistry doesn't support filter yet;
If your services use same interface, I think recipient list pattern cannot
be used, directly;
Maybe you can write a custom processor to invoke osgi services by your self;
But if you really like the bean feature supported by camel, you
Hi, Christian Müller:
Thanks you. I know how to split csv now.
First, please forgive my long e-mail , but this question is confusing me
for a long time. I think I should express it clearly at this chance.
I still feel confused about whether we should do "batch" operation in the
route or
7;s OGNL a try (on CxfPayload object)
to avoid writing Java code.
On 12/14/2010 10:40 AM, ext2 wrote:
>> Camel message header is used by transport header and other Camel
>> "internal" header.
> Is it the design principles of camel? Only transport header and Internal
> head
Sorry, forget to say, in osgi registry, the name of service(bean) is the
osgi service's class name; that's to say to using "to" endpoint to invoke a
osgi service is not like to invoke a spring bean. It should use the class as
name , not the id like spring registry does;
By the way, if you osgi se
Trying recipient-list pattern(dynamic to create to endpoint to invoke beans
in registry), it will look registry of osgi first(Clause has already said )
-original -
Sender: klausb [mailto:klaus.baumec...@hp.com]
Date: 2010/12/14 23:31
Sender: users@camel.apache.org
Subject: Re: How to setu
ers@camel.apache.org
Subject: Re: Questions of how to simplify using Camel as mediator for
WebService
On 12/14/2010 08:51 AM, ext2 wrote:
> Hi:
>
> The cxf component (payload model)will wrapped the soap message in a
> CXFPayLoad or a CXFMessage. Both are not advantage for camel&#
Hi:
The cxf component (payload model)will wrapped the soap message in a
CXFPayLoad or a CXFMessage. Both are not advantage for camel's script
language to access headers and body xml。
I cannot use a simple expression etc: simple language or xpath
language to access the soap header
The real problem is: if split expression cannot do streaming operation, the
memory cost cannot be avoid;
Here the xpath is example which cannot do streaming. Csv will be another
example. It means we cannot process a very large csv file (is it?I am not
sure, but it seems so)
So how about supporting
Backup it in a message header before entering split, then you can use it.
But if memory cost is a critical problem for you, you'd better to redesign
your
from endpoint's implementation, which should not loading all objects in
memory at once, but return a iterator which will sequential load the ob
Hi:
Camel support user to define custom InterceptStrategy;
But the exchanged processed by the custom interceptor's cannot be
logged by Camel's Tracer.
This is because camel always wrap tracer before wrapping the custom
interceptors;
Maybe camel should wrap tracer a
12/8 16:06
Receiver: users@camel.apache.org
Subject: Re: How about to support dynamic configurations in camel?
On 12/8/10 2:31 PM, ext2 wrote:
> Hi:
> Changing the configuration dynamically at runtime to adjust the
> behavior of application is a use-full feature for many applica
Hi:
Changing the configuration dynamically at runtime to adjust the
behavior of application is a use-full feature for many application.
Camel support some dynamic mechanism now, etc: dynamic-routing
pattern; but I still encounter some limits while using camel. For example:
1)how cou
ptor is wrapped twice for each
processor.
On Fri, Dec 3, 2010 at 4:17 PM, ext2 wrote:
> Thanks a lot.
> It's really a good news to support dynamic support at runtime;
>
> Actually, many management requirement need a runtime-dynamic-deciding
> features beside Instrument;
>
gic deciding to do this would then be easier to implement.
>
>
> On Dec 3, 2010, at 7:15 AM, ext2 wrote:
>
>> Sorry, I forget to attach my tracing result;
>>
>> I am sure , it's wrapped twice;
>> Because the Instrument Processor will trace t
n call the disableJMX()
method to do it.
On 11/30/10 9:18 PM, ext2 wrote:
>
> Hi:
> Camel's InstrumentationStrategy will works by default. Does anyone
> knows how to configured to remove it?
> Because I wont to implement mine InstrumentationStrategy instead;
>
> Thanks
plain
text]
- bean: Recording duration: 11 millis for exchange: Exchange[Message: plain
text]
- bean: Recording duration: 48 millis for exchange: Exchange[Message: plain
text]
- route: Recording duration: 160 millis for exchange: Exchange[Message:
plain text]
-Original -
Sender: ext2
ry. It ensures a
better use of resources and scales much better with higher message volume.
I hope this helps,
Hadrian
On Dec 1, 2010, at 9:53 PM, ext2 wrote:
> Hi:
> Each camel processor will be wrapped with Instrument Interceptor
> twice. So for each process , the Instrume
Hi:
Each camel processor will be wrapped with Instrument Interceptor
twice. So for each process , the Instrument interceptor will be executed
twice.
It seems no use but waste performance;
Why? Or a bug?
Thanks for any suggestion.
Hi:
Camel's InstrumentationStrategy will works by default. Does anyone
knows how to configured to remove it?
Because I wont to implement mine InstrumentationStrategy instead;
Thanks any suggestion;
Hi:
Camel's InstrumentationStrategy will works by default. Could I
configured to remove it?
Because I wont to implement mine InstrumentationStrategy instead;
Thanks any suggestion;
Claus Ibsen [mailto:claus.ib...@gmail.com]
Time: 2010年11月26日 16:53
Receiver: users@camel.apache.org
Subject: Re: Some questions of camel's jta transaction support
Hi
Camel in Action chapter 9 really covers transaction and compensations
really well.
On Fri, Nov 26, 2010 at 6:06 AM, ex
camel.apache.org
Subject: Re: Some questions of camel's jta transaction support
Hi
Camel in Action chapter 9 really covers transaction and compensations
really well.
On Fri, Nov 26, 2010 at 6:06 AM, ext2 wrote:
> 1: Could the from-endpoint decide how to do the post-action according to
&g
1: Could the from-endpoint decide how to do the post-action according to
following route's transaction result(rollback/commit)?
Fo example :
from().transacted().multicast().db1().db2();
from() will receive a external message. Db1, db2 will insert the
message to different databa
Hi:
Here is a simple route, I think it's result should be 6, but the result is
2;
from("direct:start2").multicast(new SumAggregateBean())
.pipeline().transform(BeanLanguage.bean(IncreaseOne.class)).bean(new
IncreaseTwo()).end()
.pipeline().transform(BeanLanguage.bean(IncreaseOne.c
Hi:
The mail tell 3 things:
1) pipeline processor, along with other build-in processor of camel(which
doesn't care MEP) will cause a confusing things;
2) some source code of camel concerned of this confusing.
3) how to understand the confusing things? it concerns of MEP , which has been
discuss
Thanks a lot
I have raise the issue as:
https://issues.apache.org/activemq/browse/CAMEL-3266,
On Fri, Oct 22, 2010 at 11:27 AM, Claus Ibsen wrote:
> On Fri, Oct 22, 2010 at 11:15 AM, ext2 wrote:
>> Hi, Clau
Hi, Clause:
It seems the Ordered interface of interceptor strategy doesn't works;
Could camel support such a feature?
==
On Fri, Oct 22, 2010 Claus Ibsen [mailto:claus.ib...@gmail.com] wrote
> On Fri, Oct 22, 2010 at 9:19
{A{B{Processor}}.
On Fri, Oct 22, 2010 Claus Ibsen [mailto:claus.ib...@gmail.com] wrote:
Re: Could camel support configurable interceptor strategy in spring?
On Fri, Oct 22, 2010 at 7:39 AM, ext2 wrote:
> Thanks a lot. I see;
>
> Cam
level interceptor)
There is an InterceptFrom DSL[1] that can meet you requirement.
[1]http://camel.apache.org/intercept.html#Intercept-InterceptFrom
On 10/22/10 12:01 PM, ext2 wrote:
>
>
> Hi:
> Camel support interceptors for processor, but recently I encounter a
> requirement,
n the afterPropertiesSet() method of
AbstractCamelContextFactoryBean[1].
[1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-core-xml/sr
c/main/java/org/apache/camel/core/xml/AbstractCamelContextFactoryBean.java
On 10/22/10 12:15 PM, ext2 wrote:
> Hi:
> Camel's Context sup
Hi:
Camel's Context support a low level
API(CamelContext.addInterceptStrategy), which we could use it to add our
custom interceptor-strategy in Java DSL program;
But while using Spring DSL, it seems there is no such a
configuration we can use to configure the custom interceptor-str
Hi:
Camel support interceptors for processor, but recently I encounter a
requirement, it ask for a custom instrumentation strategy of from endpoint;
for example , we need the statistics of how much times the message is
successfully processed in a given time, and how much message is faile
Thanks Willem Jiang
I agree to your comments. Camel's InOnly & InOut pattern does have their means,
and it's not just for optimize;
Because we understand MEP as such, I think the low level Processor should
always handle the MEP correctly, they should judge the MEP, and return the
result by In
ink current Camel can do the job 2.
But you can easily write a customer ShutdownStrategy which extends the
default one and configure it into Camel.
On 10/13/10 8:59 PM, ext2 wrote:
>
> Hi:
> I have post the question. But it seems I doesn't illustrate the
> usage clearly and c
not worth.
==
Hadrian Zbarcea wrote:
>Then there's something wrong with the aggregator, I'd say.
>The result of processing is always: out if present, otherwise in. Makes
sense?
>I hope this helps,
>Hadrian
>On Oct 14, 2010, at 12:43 AM, ext2 wrote:
> I still feel it
ld-you-getin-or-getout.html
On Oct 13, 2010, at 11:51 PM, ext2 wrote:
> The Transformer Processor always set Out Message as result and doesn't
> care what MEP being;(At least until version camel 2.4.0, it being so,
2.5.0
> I haven't checked)
>
> It seems doesn't confirm to the rules of camel's MEP, why?
>
>
The Transformer Processor always set Out Message as result and doesn't
care what MEP being;(At least until version camel 2.4.0, it being so, 2.5.0
I haven't checked)
It seems doesn't confirm to the rules of camel's MEP, why?
Hi:
I have post the question. But it seems I doesn't illustrate the
usage clearly and cause some confuse things. So I re-write the use case,
and repost the subject again. I am regret for it :(.
While the manager decide to stop the applications. They often
encounter such s
Hi:
It seems the camel's graceful shutdownis just like the requirement "robust
stop application": give a waiting time, force stop, and do it's best
ability to avoid lost message;
But the camel cannot support "try to stop" interface; isn't it?
>Hi
>Can you elaborate on the robust shutdown?
>My experience is if you can't do the grace for shutdown with a certain
>time, the on flight exchanges maybe have no other change to be processed.
>Do you mean Camel should store these on flight exchanges into a
>persistence storage, if the wait ti
Can I configure sync or asynchronous for individual processor in spring?
If so , I could separate the CPU-cost actions and IO-Cost actions in
different thread more clearly;
Hi:
Camel support graceful shutdown feature. When the camelContext is
stopped, camel will try to stop application gracefully until the time
expired;
Some-times the system manager may required to try to stop the
application , and if the application cannot be stopped in time, the s
/tests/camel-itest-osgi
On 10/9/10 7:57 PM, ext2 wrote:
> Sorry, the mail list will disable attachment, check the patch :
> https://issues.apache.org/activemq/browse/CAMEL-3213
> ===
> Hi:
> To debug the camel test case i
Sorry, the mail list will disable attachment, check the patch :
https://issues.apache.org/activemq/browse/CAMEL-3213
===
Hi:
To debug the camel test case in osgi framework with eclipse ide,
using PAX-EXAM is difficult than spring-osgi-test
Hi:
To debug the camel test case in osgi framework with eclipse ide,
using PAX-EXAM is difficult than spring-osgi-test.But the spring-osgi will
loading some exhausted and expired bundles by default. Some bundles are
expired and hardly to find in the maven repository;
The attachmen
Hi:
Only transactional resources(Database, JMS etc) could support
transaction. While other resources( File etc) couldn't support transaction.
Doest the camel support a feature to support a custom transaction
process? The feature allow we write custom commit/rollback process for an
e
try-catch, the catch will not works;
Claus Ibsen wrote:
>I told you that in Spring XML does not work as expected in
>2.2 or older. You need 2.3 for that.
On Sat, Apr 24, 2010 at 2:52 AM, ext2 wrote:
> Maybe I hasn't illustrated my usage clearly.
> My usage is two separa
ng XML does not work as expected in
>2.2 or older. You need 2.3 for that.
On Sat, Apr 24, 2010 at 2:52 AM, ext2 wrote:
> Maybe I hasn't illustrated my usage clearly.
> My usage is two separate nested global transaction(jta), not just a single
> transaction.
> If only a si
ests for transactions and
>there would also be one for this use case.
On Fri, Apr 23, 2010 at 1:02 PM, ext2 wrote:
>
> Hi:
>
> Sorry to raise the question again.
>
> Recently , I check the EJB specification and do some test with ejb's
> container managed transaction
Hi:
Sorry to raise the question again.
Recently , I check the EJB specification and do some test with ejb's
container managed transaction-policy , also the spring-transaction
template(they both are same)
After checking and testing EJB, I think the camel's current transaction is
deficiency;
Fo
nd it can do the same thing as
>doTry... doCatch does.
[1]http://camel.apache.org/exception-clause.html
Willem
ext2 wrote:
> Thanks Claus Ibsen:
>
> If we just consider this example, move policy before doTry could resolve
it; but If we consider another situation:
>
always ask for transacted-error-handler, and they
will sometimes conflict with other error-handle mechanism(etc: try-catch);
Willem wrote;
>>ext2 wrote:
> Thanks Willem:
>
> I got it; and using this feature I could define custom transaction range
in
> a single route(need not sepa
Thanks Claus Ibsen:
If we just consider this example, move policy before doTry could resolve it;
but If we consider another situation:
..some other operation ..
>
>
>
>
>
>
> java.lang.Exception
>
>
>
> As for normal unders
Hi:
The camel's transaction required the transacted-error-handler, but try-catch
required no-error-handler. They will conflict; following is a sample that
the try-catch cannot works while using transaction. but I am not sure if
this is bug or just a camel's limit?
For example, the following rout
curity is based on this camel policy feature.
how to configure such policy using spring? Or just dsl?
Willem
ext2 wrote:
> Hi:
> Camel policy is very useful to define some custom wrapper features;
> But in camel 2.2 , it seems the policy only apply on the whole route; And
it
&g
Willem wrote:
>>No, you can apply the police per processor.
>>The new added camel-spring-security is based on this camel policy feature.
how to configure such policy using spring? Or just dsl?
Willem
ext2 wrote:
> Hi:
> Camel policy is very useful to define some custo
Hi:
Camel policy is very useful to define some custom wrapper features;
But in camel 2.2 , it seems the policy only apply on the whole route; And it
cannot define a policy on a special processor, is this true?
And does camel 2.x support some mechanism to support define custom
polic
Hi:
Camel 's transaction-policy is applied for all processors in the
route; but how to use this features to implement a customized transaction
section in camel? Etc: if I could assign a transaction-policy to a single
pipe-line processor(not the whole route), I could define custom transact
Hi :
In camel 1.6x, I must use the to control transaction; but
when camel 2.2x , a new element is introduced. Is the
is just a simplified for or it provide some new
features?
Thanks for any suggestion
Hi:
Previously , I have ask some question about splitter, and the
stream-based splitter pattern can resolve such situations:
Enumerate data from large external data source, and process each
data continuously until all data from external-data source is readed;
But resolve
Sorry, I forget to say, this is running on camel 2.2;
I have checked the camel's document and source-code; the camel-document say
" try-catch will disable the error-handler"; but while I checking the
source-code of camel , it only disable error-handlers of node (which is
conjunction with doTry pa
Follow route use a default-error-handler for the route, and also defined a
custom exception handle logic using try-catch-pattern.
But if the "myProcessRaiseError" raised exception the catch-clause cannot be
invoked; Why? Is it camel's bug?
$
In camel , try-catch means , if exception occurs , catch-clause will be
execute.
And how does camel define : What is message(catch-clause received) 's
content?
Is the content exactly equals to the processed content where exception just
occurs?
For pipe line , catch-clause will received a mess
Hi:
camel-osgi component give another a spring osgi
namespace."http://camel.apache.org/schema/osgi";.
But if I use the normal
spring-namespace(http://camel.apache.org/schema/spring), it seems works well
too in osgi environment.
So what's the real different for the osgi name
Hi Andrew:
I have run to the same problem as you. To resolve this , beside using
streaming option. You maybe care about following things too:
Because in your situation, iterator will return millions result , but
thread pool only has limited threads.
1) You must configured a executor, not use
Hi:
The camle's enrich pattern could be used to enrich the original
message by a producer's result message.
And does the pattern support to enrich the original message by a
"customed route result"?
For example, it maybe looks liked as :
is is
camel's wonderful flexibility;
Thanks a lot;
-origin-
Sender: Claus Ibsen [mailto:claus.ib...@gmail.com]
Date: 2010-1-16 20:05
Receiver: users@camel.apache.org
Subject: Re: A bug of InOut pattern?
On Sat, Jan 16, 2010 at 8:26 AM, ext2 wrote:
> This is a bad news for me.
>
oid process(Exchange me)
> {
> Integer result= me.getIn().getBody() + 1;
> if (me.getPattern().isOutCapable()) {
> me.getOut().setBody(result);
> } else {
> me.getIn().setBody(result);
> }
>
he out message
>to next processor exchange's in message, otherwise it will copy the in
>message to next processor exchange's in message.
>Willem
ext2 wrote:
> Hi:
> The camel 2.1's pipeline patter's MEP is InOnly default. But the result of
> following route
he out message
>to next processor exchange's in message, otherwise it will copy the in
>message to next processor exchange's in message.
>Willem
ext2 wrote:
> Hi:
> The camel 2.1's pipeline patter's MEP is InOnly default. But the result of
> following route
Hi:
The camel 2.1's pipeline patter's MEP is InOnly default. But the result of
following route is different, if I using inOnly() processor in route vs
using default;
I tried it using a simple sample: send a message to a direct endpoint, which
body is number=1, a route receive the message and incr
While learning camel's pattern, it seems the in only patter is very hard to
understand;
Following is a test-case from the camel's unit test( with a little change).
inProcess bean just increase the input message body(as Integer) and set back
to input message. outProcess bean just increase the inpu
Hi:
Camel has provide management feature. But how I could extend it?
I have noticed the camel provide managed object(etc:
ManagedProcessor), will be very useful to extend the management feature.
But if I write a custom ManagedProcessor , could I inject it in
camelContext(tell cam
Sorry, in my previous mail , I call the strategy as "release Strategy". The
name is wrong, it should changed as "exit strategy". The "exit strategy"
provide a mechanism to do some cleanup things when a pattern exist;
Ext2 wrote:
Hi:
I haven't c
;
> Could you create a ticket and attach a small sample / unit test etc.
> what you are doing?
>
>
> On Mon, Jan 11, 2010 at 7:26 AM, ext2 wrote:
>> Hi:
>>By checking the camel's document, I just find a property tell the
>> index of message, but cann
>>Use .convertBodyTo(String.class) after the from. This will store the HTTP
data
>>as a String which can be safely duplicated when you do a multicast.
Is the problem is really caused by duplicating message?
If it does, does the multi-cast support a strategy for end-user who can
control how to dup
Hi:
By checking the camel's document, I just find a property tell the
index of message, but cannot find a property to indicate the end of
splitting.
But some-times, it will be very use-full for stream-based splitter.
For example:
When I using stream-based splitter to proce
Oh, I am stupid;
The camel's document said clearly, the bean return iterator, and using
stream model could resolve my problem;
---
Does the split-pattern support the bean-express to return a Enumeration
instead of List?
--
Does the split-pattern support the bean-express to return a Enumeration
instead of List?
Hi
I always to do work , it seems "the split pattern" could resolve,
but will encounter memory overload problem. To illustr
Hi
I always to do work , it seems "the split pattern" could resolve,
but will encounter memory overload problem. To illustrate the problem, lets'
take a example:
Often , we need to query records from a database , but the records
matched the condition are too much , and cannot loa
97 matches
Mail list logo
