camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-5679) functionality to process SOAP messages inside a camel processor
Date Tue, 02 Oct 2012 22:49:07 GMT


Raul Kripalani resolved CAMEL-5679.

    Resolution: Won't Fix
      Assignee: Raul Kripalani

Users can handle SOAP messages inside a processor in whatever way they wish.

This is the related thread:
My idea was to create a setter DSL not constrained to the body (setBody), headers (setHeader)
or properties (setProperty). Instead, the destination of the "setting" or assignment would
be determined by an expression.

Opening another ticket with a new title and description.
> functionality to process SOAP messages inside a camel processor
> ---------------------------------------------------------------
>                 Key: CAMEL-5679
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf, camel-soap
>    Affects Versions: 2.10.1
>         Environment: Generic to all environments
>            Reporter: sura monday
>            Assignee: Raul Kripalani
>            Priority: Minor
>              Labels: feature
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> currently it is not possible to use camel xpath or xquery to extract soap elements into
a hashmap (or some variables inside a processor in the camel route). camel xpath and xquery
support only setting headers using soap elements and to be used as filter conditions

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message