Sergey,
Thanks for this looking into this.
Regards D.
On Wed, Jun 27, 2012 at 6:28 PM, Sergey Beryozkin-3 [via Camel] <
ml-node+s465427n5715175...@n5.nabble.com> wrote:
> Hi
> On 15/06/12 09:33, desysemia wrote:
> > Both,
> >
> > Thanks for your input.
> >
> > With regards to checking that my
Hi
On 15/06/12 09:33, desysemia wrote:
Both,
Thanks for your input.
With regards to checking that my camel-cxfrs consumer is correct. All
other components of the URL are matched and passed through correctly, e.g.
PathSegments and QueryParameters. What could be configured incorrectly an
still
Both,
Thanks for your input.
With regards to checking that my camel-cxfrs consumer is correct. All
other components of the URL are matched and passed through correctly, e.g.
PathSegments and QueryParameters. What could be configured incorrectly an
still allow this to happen?
D.
On Fri, Jun 15
Hi,
As Sergey just said, the metrix parameters are got from the request URI
which means it has nothing to do with the server address that your
camel-cxfrs consumer is using.
Even you define the server address with the values option, if the
client request doesn't has these values you will not g
Hi
On 14/06/12 16:59, desysemia wrote:
This is my first time posting here, so a big hello from me!
Let me start off by stating I'm quite new to Camel and CXF so the issue I'm
seeing might well just be my own doing.
I'm currently running FuseESB/ServiceMix 3.6/4.4.1 including Camel version
2.8.0
