You can use xquery expression to get the desired element.
On May 30, 2017 12:08 AM, "anjanaintergration" <2340pa...@gmail.com> wrote:
>
> Hi ,
>
> We have a SOAP service that sends huge data 4 gb. We need to route this
> response to another SOAP service. However there is an element in SOAP:BODY
>
In the past I generated java-classes based on a wsdl containing DataHandlers.
If you are able to generate a java-class like this you could render the
soap-message to a java-object without a large memory consumption.
You need to enable MTOM on the endpoint.
Maybe this can help you.
--
View this
Hi ,
We have a SOAP service that sends huge data 4 gb. We need to route this
response to another SOAP service. However there is an element in SOAP:BODY
which we need to extract and set as SOAP header in outgoing service.
I understand converting to JAXB is not optimal since huge data converting
Hello,
I am using org.apache.camel.spring.javaconfig.CamelConfiguration to
bootstrap my application. Generally it works fine, but if I am using
restConfiguration() then it gives me some issues:
I've tried with Camel 2.17 and 2.19 with Jetty9 endpoint.
If I have two route builders, I can use th
Ok,
quick fix for that was to use HashLoginService instead of custom class
implementing LoginService. As HashLoginService extends AbstractLifeCycle it
is not being sanitized on stop of security handler (when second service is
added).
adie
--
View this message in context:
http://camel.465427.n
Yes its extended by default
https://github.com/apache/camel/blob/camel-2.17.x/camel-core/src/main/java/org/apache/camel/management/DefaultManagementAgent.java#L82
On Mon, May 29, 2017 at 5:18 PM, Martin Lichtin
wrote:
> Upgrading from 2.16.x to 2.17.7 I see many
> Runtime endpoint registry is in
Upgrading from 2.16.x to 2.17.7 I see many
Runtime endpoint registry is in extended mode gathering usage statistics of all
incoming and outgoing endpoints (cache limit: 1000)
messages.I'm not setting the statisticslevel, and the default level should not
be extended?
You need to store the state of this offset outside a Camel exchange
property. Instead create a bean to hold that state, and then call that
bean from the camel route to get the new offset, which you can then
increment for the next call.
On Mon, May 29, 2017 at 3:34 PM, tor86 wrote:
> I have a prob
Hi,
I totally aggree on furchess post and I guess issue
https://issues.apache.org/jira/browse/CAMEL-9241 is related to this topic.
Having the regex literal as delimiter on the grouped result seems broken.
Actually we replace the "regex literal" after the tokenize took place but it
seems like bad
I have a problem with dynamically altering properties of a given route. I
have a timer which calls an endpoint. This endpoint fetches xx amount of
rows from a DB and uses the offset=$property.testproperty to know where to
begin fetching data from DB. If offset is 100 it starts at row 100 and moves
Hi
I got the task to build an Event-Dispatching application and decided to use
camel as base framework.
Among others, I have the following requirements:
1) Some routes are hardcoded in the software, but the user can configure
some aspects of the route via a web gui (e.g. the condition for a
switc
11 matches
Mail list logo