[
https://issues.apache.org/activemq/browse/SM-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39770
]
Chris DiLeo commented on SM-228:
--------------------------------
If I understand this issue properly I think I have run into the same problem.
The goal I am trying to achieve is to have a single HTTP Binding component act
as a "gateway" for subsequent dispatching/routing based on message properties.
One way to achieve this is to have the binding component take parameters from
the incoming URL and make those part of the in message properties when it gets
constructed. Attached is a patch for 2 files which I think reaches the goal.
1. HttpComponent: added a boolean flag to allow the user to decide if this
behavior is wanted for a particular flow. For backwards compatibility, it
defaults to false.
2. ConsumerComponent: added a block of code that, if the flag for storing
parameters in properties is set, will spin through a query string, if present,
and populate the in message properties.
> Get back http parameters as inMessage.properties in a POST request.
> -------------------------------------------------------------------
>
> Key: SM-228
> URL: https://issues.apache.org/activemq/browse/SM-228
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-components
> Affects Versions: 2.0.1, 2.0.2, 3.0-M1
> Environment: All
> Reporter: Angel Gomez
> Priority: Minor
> Attachments: HttpMarshaler.java, parameter_patch.patch
>
>
> To have the parameters of an Http Post Request available in inMessage.
> This behavior was present in version 1.0 and changed in a latter version (
> 2.0.2 + ) from a change in HttpMarshaller.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
