Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6869A922B for ; Thu, 14 Jun 2012 16:00:14 +0000 (UTC) Received: (qmail 23685 invoked by uid 500); 14 Jun 2012 16:00:13 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 23659 invoked by uid 500); 14 Jun 2012 16:00:13 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 23651 invoked by uid 99); 14 Jun 2012 16:00:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2012 16:00:13 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of sysemia.darren.everley@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2012 16:00:07 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SfCSY-0001MX-QO for users@camel.apache.org; Thu, 14 Jun 2012 08:59:46 -0700 Date: Thu, 14 Jun 2012 08:59:46 -0700 (PDT) From: desysemia To: users@camel.apache.org Message-ID: <1339689586806-5714486.post@n5.nabble.com> Subject: CXFRS URL Matrix Parameters seemingly stripped away MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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.