I am looking for a way to peel the "extra path info" out of a request so I can pass it as a parameter to an OXF pipeline, as if it were a query parameter. I've looked at the request generator, and I can get the "path-info" element from it easily enough, but that gives me the path-info from the servlet's perspective, not from the matcher's perspective. To be more specific:

I have a URL like this:
   /orbeon/localdetail/90210

I would like all requests for "/orbeon/localdetail" to be passed to one pipeline, with "90210" (with or without leading slash) available as a parameter to pass to that pipeline's input.

If OXF is mapped to "/orbeon", then the request will contain a "path-info" element with a value of "/localdetail/90210", which is the "extra path info" from the servlet engine's perspective. What I'd like to have, then, is a facility in OXF that would perform the same function, namely, to recognize that "This pipeline was invoked by a URL beginning with '/orbeon/localdetail', and here's the extra information after the match."

I realize that this can be approximated using regular expressions in the perl5 matcher, but that's kind of a kludge, and I'd rather not have to deal with the overhead. I also realize that I could encode the information as a query parameter instead, i.e. "/orbeon/localdetail?zip=90210", but for historical reasons, I need to be able to do both.

Does anyone have any suggestions? If this isn't currently available, is it a feature worth having?

Thanks in advance for your help.

Jeff Jones
The Weather Channel Interactive


------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user

Reply via email to