Thanks for quick reply. After reading the SEDA component source and reading
the article (http://www.eecs.harvard.edu/~mdw/papers/seda-sosp01.pdf)
thoroughly, gave me some understanding about Staging concept. Nice work
Camel team, it is quiet easy to understand Seda code in Camel..
--
View this
I found out that JAXRS Client only sends 1 parameter. So i will just have to
configure my service class to only accept 1 parameter instead of two. Ill
just wrap it in a transfer object.
Anyway, maybe as a enhancement to camel-cxf jaxrs, hopefully we can also use
and support different rest client
Hi Jejo
Please feel free to log a JIRA for it, doesn't the HttpClient work good
for you ?
Willem
jejmaster wrote:
I found out that JAXRS Client only sends 1 parameter. So i will just have to
configure my service class to only accept 1 parameter instead of two. Ill
just wrap it in a transfer
Hi Jejo,
I just checked the code of CxfRsProducer, the parameter is taken from
the inMessageBody with Object[].class.
Maybe something is wrong with this part of code.
Can you attach a small test case into the JIRA? It will help us to find
a way to resolve this issue quickly.
Willem
jejmast
Hi Willem,
Its working enough in 2.3-SNAPSHOT. but we decided to use 2.2 as of the
moment until 2.3 gets released.
Do you recommend on the httpclient rather than the proxyClient?
Jejo
willem.jiang wrote:
>
> Hi Jejo
>
> Please feel free to log a JIRA for it, doesn't the HttpClient work g
It's hard to create the Proxy without specify the ResourceClass.
HttpClient API is more friendly, as you don't need to specify the
ResourceClass when creating the client.
Willem
jejmaster wrote:
Hi Willem,
Its working enough in 2.3-SNAPSHOT. but we decided to use 2.2 as of the
moment until 2
Hi,
That worked, thank you!
On 8 April 2010 11:44, Claus Ibsen wrote:
> Hi
>
> Okay I have had a look. You need to enable eagerCheckCompletion() to
> test for the header in the INCOMING message.
> Then it should work. Otherwise it will check for the header in the
> AGGREGATED exchange and since
this looks like a good idea but external server vendor doesn't support this.
would there be any problems like loosing messages with iofilter approach
previously suggested or should I copy and customize Mina producer component
and change the messageReceiver method to send message to another endpoin
Thanks for the quick replies!
Willem--
This is a rather trivial test case - in my "real" routes I definitely
require the tags. It does appear that using transacted IS
setting up a new TransactionErrorHandler; it's just not grabbing the global
onException handlers as I expected...
Claus--
Cam
that's a good idea. but external server vendor doesn't support this. would
there be any problems like loosing messages with iofilter approach
previously suggested or should I copy and customize Mina producer component
and change the messageReceiver method to send message to another endpoint
when i
Yea, I tried that based on thread I saw yesterday. I still get the same
error. I'm wondering if it has something to do with the way the camel web
console works. Do I need to put anything in the beans file
(applicationContext.xml)? Here is my web.xml:
http://www.w3.org/2001/XMLSchema-instanc
Thanks Clause - in this case that wasn't it - line wrapping made it less
obvious but you can see the second ? was in a
commented out section /* */ I had switched to object serialization to
try and track the problem which ultimately helped.
by switching to object serialization it started complaini
I see. That's great. So you mean the serviceClass parameter is optional when
configuring cxf? How do you expose the service without specifying the
serviceClass ? Isn't it required configuring at least the cxf:rsServer?
http://localhost:8080/services/rest";
serviceClass="com.project.service.impl
Hi
I have created an unit test on Camel trunk based on your route. And it
works for me.
http://svn.apache.org/viewvc?rev=932470&view=rev
On Fri, Apr 9, 2010 at 4:15 PM, dnn wrote:
>
> Thanks for the quick replies!
>
> Willem--
>
> This is a rather trivial test case - in my "real" routes I defi
Hi
I also think there was an issue in a Camel release with setting a
errorHandlerRef on . So set it on instead to see
if it works then.
It should be fixed in 2.3-SNAPSHOT. or maybe in 2.2 also (cant remember)
On Fri, Apr 9, 2010 at 5:51 PM, Claus Ibsen wrote:
> Hi
>
> I have created an unit te
Works for me too using trunk. It looks like an automated build pulls the
trunk at midnight and deploys it to 2.3-SNAPSHOT in maven, so I should be
able to start using it from mvn tomorrow. When is 2.3.0 slated for release?
Thanks for all the hard work. You guys make a great product!
Claus Ib
I'm trying to post documents to couchdb using restlet but the restlet
component is hard coded to url encode the post data. This makes the JSON
text i'm posting invalid. Do I need to use some other component or is there
a way around this?
--
View this message in context:
http://old.nabble.com/R
All,
After having worked my way through this I thought I might post the results
and ask if there's anything I left out, or if there are easier or better
ways to do this.
We need our application, using a camel client, to connect to a remote
ActiveMQ/FUSE message broker using https transport. Bef
All,
This is a follow on to my previous note POJO Example with http transport.
After getting HTTP working, I did the following to get HTTPS working:
Per various posts and pages for ActiveMQ, after adding the https
transportConnector (described in my previous note), I set up key and trust
stores
19 matches
Mail list logo
