You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by desysemia <sy...@gmail.com> on 2012/06/14 17:59:46 UTC
CXFRS URL Matrix Parameters seemingly stripped away
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.
The short version:
is that the PathSegment.getMatrixParameters method returns an empty
collection if the resource is accessed through the URL made available
through the rsServer endpoint, but as expected when accessed through the
rsClient endpoint. But therefore as I understand it not therefore using the
Camel route at all.
So to me somewhere along the line Camel/CXF is stripping of the matrix
parameters, thoughts?
The long version:
So here goes with the scenario;
I have a Camel route defined using the rsServer and rsClient endpoints, and
I have a resource class implemented and used by both endpoints with a single
JAXRS annotated method as such;
@GET
@Path ( "object/{context}/{version}" )
public String getObject ( @PathParam ( "context" ) PathSegment context,
@PathParam ( "version" ) float version );
This is invoked through the rsServer endpoint URL like so;
http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
Then calling the getMatrixParameters method on the 'context' parameter
returns an empty collection.
However if this is invoked through the rsClient endpoint URL like so;
http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
Then calling the getMatrixParameters method on the 'context' parameter
returns a collection containing the two key/value pairs as described.
Hopefully someone out there can point me in the right direction here?
Thanks in advance.
D.
--
View this message in context: http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: CXFRS URL Matrix Parameters seemingly stripped away
Posted by desysemia <sy...@gmail.com>.
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+s465427n5715175h63@n5.nabble.com> wrote:
> 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 allow this to happen?
> >
> Please watch
> https://issues.apache.org/jira/browse/CAMEL-5405
>
> Cheers, Sergey
>
> >
> > D.
> > On Fri, Jun 15, 2012 at 3:07 AM, Willem.Jiang [via Camel]<
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=5715175&i=0>>
> wrote:
> >
> >> 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 get it.
> >> Please check if the request to the camel-cxfrs consumer is right.
> >>
> >> On Fri Jun 15 00:19:15 2012, Sergey Beryozkin wrote:
> >>
> >>> 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.
> >>>>
> >>>> The short version:
> >>>>
> >>>> is that the PathSegment.getMatrixParameters method returns an empty
> >>>> collection if the resource is accessed through the URL made available
> >>>> through the rsServer endpoint, but as expected when accessed through
> >> the
> >>>> rsClient endpoint. But therefore as I understand it not therefore
> >>>> using the
> >>>> Camel route at all.
> >>>>
> >>>> So to me somewhere along the line Camel/CXF is stripping of the
> matrix
> >>>> parameters, thoughts?
> >>>>
> >>>
> >>> In CXF alone, HTTPServletRequest.getRequestURI() is used in CXF
> >>> AbstractHTTPDestination to capture the relative path including the
> >>> matrix parameters if any, for the subsequent match to succeed.
> >>>
> >>> I've confirmed locally that matrix parameters are correctly captured
> >>> with the nearly identical test resource method signature.
> >>>
> >>> Perhaps in your case CXF Message.REQUEST_URI property is set by CXF
> >>> Camel differently which may be causing the loss of the parameters
> >>>
> >>> Cheers, Sergey
> >>>
> >>>> The long version:
> >>>>
> >>>> So here goes with the scenario;
> >>>>
> >>>> I have a Camel route defined using the rsServer and rsClient
> >>>> endpoints, and
> >>>> I have a resource class implemented and used by both endpoints with a
> >>>> single
> >>>> JAXRS annotated method as such;
> >>>>
> >>>> @GET
> >>>> @Path ( "object/{context}/{version}" )
> >>>> public String getObject ( @PathParam ( "context" ) PathSegment
> context,
> >>>> @PathParam ( "version" ) float version );
> >>>>
> >>>> This is invoked through the rsServer endpoint URL like so;
> >>>>
> >>>> http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
> >>>>
> >>>> Then calling the getMatrixParameters method on the 'context'
> parameter
> >>>> returns an empty collection.
> >>>>
> >>>> However if this is invoked through the rsClient endpoint URL like so;
> >>>>
> >>>> http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
> >>>>
> >>>> Then calling the getMatrixParameters method on the 'context'
> parameter
> >>>> returns a collection containing the two key/value pairs as described.
> >>>>
> >>>> Hopefully someone out there can point me in the right direction here?
> >>>>
> >>>> Thanks in advance.
> >>>>
> >>>> D.
> >>>>
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>>
> >>
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
> >>>>
> >>>> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Willem
> >> ----------------------------------
> >> FuseSource
> >> Web: http://www.fusesource.com
> >> Blog: http://willemjiang.blogspot.com (English)
> >> http://jnn.javaeye.com (Chinese)
> >> Twitter: willemjiang
> >> Weibo: willemjiang
> >>
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714517.html
> >> To unsubscribe from CXFRS URL Matrix Parameters seemingly stripped
> away, click
> >> here<
>
> >> .
> >> NAML<
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714531.html
>
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
> Blog: http://sberyozkin.blogspot.com
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5715175.html
> To unsubscribe from CXFRS URL Matrix Parameters seemingly stripped away, click
> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714486&code=c3lzZW1pYS5kYXJyZW4uZXZlcmxleUBnbWFpbC5jb218NTcxNDQ4NnwtMTEzMjY3NjUyOA==>
> .
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5715409.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: CXFRS URL Matrix Parameters seemingly stripped away
Posted by Sergey Beryozkin <sb...@gmail.com>.
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 allow this to happen?
>
Please watch
https://issues.apache.org/jira/browse/CAMEL-5405
Cheers, Sergey
>
> D.
> On Fri, Jun 15, 2012 at 3:07 AM, Willem.Jiang [via Camel]<
> ml-node+s465427n5714517h65@n5.nabble.com> wrote:
>
>> 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 get it.
>> Please check if the request to the camel-cxfrs consumer is right.
>>
>> On Fri Jun 15 00:19:15 2012, Sergey Beryozkin wrote:
>>
>>> 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.
>>>>
>>>> The short version:
>>>>
>>>> is that the PathSegment.getMatrixParameters method returns an empty
>>>> collection if the resource is accessed through the URL made available
>>>> through the rsServer endpoint, but as expected when accessed through
>> the
>>>> rsClient endpoint. But therefore as I understand it not therefore
>>>> using the
>>>> Camel route at all.
>>>>
>>>> So to me somewhere along the line Camel/CXF is stripping of the matrix
>>>> parameters, thoughts?
>>>>
>>>
>>> In CXF alone, HTTPServletRequest.getRequestURI() is used in CXF
>>> AbstractHTTPDestination to capture the relative path including the
>>> matrix parameters if any, for the subsequent match to succeed.
>>>
>>> I've confirmed locally that matrix parameters are correctly captured
>>> with the nearly identical test resource method signature.
>>>
>>> Perhaps in your case CXF Message.REQUEST_URI property is set by CXF
>>> Camel differently which may be causing the loss of the parameters
>>>
>>> Cheers, Sergey
>>>
>>>> The long version:
>>>>
>>>> So here goes with the scenario;
>>>>
>>>> I have a Camel route defined using the rsServer and rsClient
>>>> endpoints, and
>>>> I have a resource class implemented and used by both endpoints with a
>>>> single
>>>> JAXRS annotated method as such;
>>>>
>>>> @GET
>>>> @Path ( "object/{context}/{version}" )
>>>> public String getObject ( @PathParam ( "context" ) PathSegment context,
>>>> @PathParam ( "version" ) float version );
>>>>
>>>> This is invoked through the rsServer endpoint URL like so;
>>>>
>>>> http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
>>>>
>>>> Then calling the getMatrixParameters method on the 'context' parameter
>>>> returns an empty collection.
>>>>
>>>> However if this is invoked through the rsClient endpoint URL like so;
>>>>
>>>> http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
>>>>
>>>> Then calling the getMatrixParameters method on the 'context' parameter
>>>> returns a collection containing the two key/value pairs as described.
>>>>
>>>> Hopefully someone out there can point me in the right direction here?
>>>>
>>>> Thanks in advance.
>>>>
>>>> D.
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
>>>>
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Willem
>> ----------------------------------
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.javaeye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: willemjiang
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714517.html
>> To unsubscribe from CXFRS URL Matrix Parameters seemingly stripped away, click
>> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714486&code=c3lzZW1pYS5kYXJyZW4uZXZlcmxleUBnbWFpbC5jb218NTcxNDQ4NnwtMTEzMjY3NjUyOA==>
>> .
>> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714531.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Re: CXFRS URL Matrix Parameters seemingly stripped away
Posted by desysemia <sy...@gmail.com>.
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, 2012 at 3:07 AM, Willem.Jiang [via Camel] <
ml-node+s465427n5714517h65@n5.nabble.com> wrote:
> 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 get it.
> Please check if the request to the camel-cxfrs consumer is right.
>
> On Fri Jun 15 00:19:15 2012, Sergey Beryozkin wrote:
>
> > 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.
> >>
> >> The short version:
> >>
> >> is that the PathSegment.getMatrixParameters method returns an empty
> >> collection if the resource is accessed through the URL made available
> >> through the rsServer endpoint, but as expected when accessed through
> the
> >> rsClient endpoint. But therefore as I understand it not therefore
> >> using the
> >> Camel route at all.
> >>
> >> So to me somewhere along the line Camel/CXF is stripping of the matrix
> >> parameters, thoughts?
> >>
> >
> > In CXF alone, HTTPServletRequest.getRequestURI() is used in CXF
> > AbstractHTTPDestination to capture the relative path including the
> > matrix parameters if any, for the subsequent match to succeed.
> >
> > I've confirmed locally that matrix parameters are correctly captured
> > with the nearly identical test resource method signature.
> >
> > Perhaps in your case CXF Message.REQUEST_URI property is set by CXF
> > Camel differently which may be causing the loss of the parameters
> >
> > Cheers, Sergey
> >
> >> The long version:
> >>
> >> So here goes with the scenario;
> >>
> >> I have a Camel route defined using the rsServer and rsClient
> >> endpoints, and
> >> I have a resource class implemented and used by both endpoints with a
> >> single
> >> JAXRS annotated method as such;
> >>
> >> @GET
> >> @Path ( "object/{context}/{version}" )
> >> public String getObject ( @PathParam ( "context" ) PathSegment context,
> >> @PathParam ( "version" ) float version );
> >>
> >> This is invoked through the rsServer endpoint URL like so;
> >>
> >> http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
> >>
> >> Then calling the getMatrixParameters method on the 'context' parameter
> >> returns an empty collection.
> >>
> >> However if this is invoked through the rsClient endpoint URL like so;
> >>
> >> http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
> >>
> >> Then calling the getMatrixParameters method on the 'context' parameter
> >> returns a collection containing the two key/value pairs as described.
> >>
> >> Hopefully someone out there can point me in the right direction here?
> >>
> >> Thanks in advance.
> >>
> >> D.
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
> >>
> >> Sent from the Camel - Users mailing list archive at Nabble.com.
> >
> >
>
>
>
> --
> Willem
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714517.html
> To unsubscribe from CXFRS URL Matrix Parameters seemingly stripped away, click
> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714486&code=c3lzZW1pYS5kYXJyZW4uZXZlcmxleUBnbWFpbC5jb218NTcxNDQ4NnwtMTEzMjY3NjUyOA==>
> .
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486p5714531.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: CXFRS URL Matrix Parameters seemingly stripped away
Posted by Willem Jiang <wi...@gmail.com>.
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 get it.
Please check if the request to the camel-cxfrs consumer is right.
On Fri Jun 15 00:19:15 2012, Sergey Beryozkin wrote:
> 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.
>>
>> The short version:
>>
>> is that the PathSegment.getMatrixParameters method returns an empty
>> collection if the resource is accessed through the URL made available
>> through the rsServer endpoint, but as expected when accessed through the
>> rsClient endpoint. But therefore as I understand it not therefore
>> using the
>> Camel route at all.
>>
>> So to me somewhere along the line Camel/CXF is stripping of the matrix
>> parameters, thoughts?
>>
>
> In CXF alone, HTTPServletRequest.getRequestURI() is used in CXF
> AbstractHTTPDestination to capture the relative path including the
> matrix parameters if any, for the subsequent match to succeed.
>
> I've confirmed locally that matrix parameters are correctly captured
> with the nearly identical test resource method signature.
>
> Perhaps in your case CXF Message.REQUEST_URI property is set by CXF
> Camel differently which may be causing the loss of the parameters
>
> Cheers, Sergey
>
>> The long version:
>>
>> So here goes with the scenario;
>>
>> I have a Camel route defined using the rsServer and rsClient
>> endpoints, and
>> I have a resource class implemented and used by both endpoints with a
>> single
>> JAXRS annotated method as such;
>>
>> @GET
>> @Path ( "object/{context}/{version}" )
>> public String getObject ( @PathParam ( "context" ) PathSegment context,
>> @PathParam ( "version" ) float version );
>>
>> This is invoked through the rsServer endpoint URL like so;
>>
>> http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
>>
>> Then calling the getMatrixParameters method on the 'context' parameter
>> returns an empty collection.
>>
>> However if this is invoked through the rsClient endpoint URL like so;
>>
>> http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
>>
>> Then calling the getMatrixParameters method on the 'context' parameter
>> returns a collection containing the two key/value pairs as described.
>>
>> Hopefully someone out there can point me in the right direction here?
>>
>> Thanks in advance.
>>
>> D.
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
>>
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: CXFRS URL Matrix Parameters seemingly stripped away
Posted by Sergey Beryozkin <sb...@gmail.com>.
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.
>
> The short version:
>
> is that the PathSegment.getMatrixParameters method returns an empty
> collection if the resource is accessed through the URL made available
> through the rsServer endpoint, but as expected when accessed through the
> rsClient endpoint. But therefore as I understand it not therefore using the
> Camel route at all.
>
> So to me somewhere along the line Camel/CXF is stripping of the matrix
> parameters, thoughts?
>
In CXF alone, HTTPServletRequest.getRequestURI() is used in CXF
AbstractHTTPDestination to capture the relative path including the
matrix parameters if any, for the subsequent match to succeed.
I've confirmed locally that matrix parameters are correctly captured
with the nearly identical test resource method signature.
Perhaps in your case CXF Message.REQUEST_URI property is set by CXF
Camel differently which may be causing the loss of the parameters
Cheers, Sergey
> The long version:
>
> So here goes with the scenario;
>
> I have a Camel route defined using the rsServer and rsClient endpoints, and
> I have a resource class implemented and used by both endpoints with a single
> JAXRS annotated method as such;
>
> @GET
> @Path ( "object/{context}/{version}" )
> public String getObject ( @PathParam ( "context" ) PathSegment context,
> @PathParam ( "version" ) float version );
>
> This is invoked through the rsServer endpoint URL like so;
>
> http://localhost:9000/test/object/id;key1=value1;key2=value2/1.0
>
> Then calling the getMatrixParameters method on the 'context' parameter
> returns an empty collection.
>
> However if this is invoked through the rsClient endpoint URL like so;
>
> http://localhost:9001/test/object/id;key1=value1;key2=value2/1.0
>
> Then calling the getMatrixParameters method on the 'context' parameter
> returns a collection containing the two key/value pairs as described.
>
> Hopefully someone out there can point me in the right direction here?
>
> Thanks in advance.
>
> D.
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/CXFRS-URL-Matrix-Parameters-seemingly-stripped-away-tp5714486.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com