asyncRequestBodyAndHeaders exists ...
sendBodyAndHeaders exists...
Why no asyncSendBodyAndHeaders?
Thanks!
There is a "SendBodyAndProperty" (singular.)
This is a "SendBodyAndHeader" (plural)
Why is there no plural version of the properties?
...
// mina component
// unmarshal it
// marshal it
I can put a bean:myBean in between and see that, yes, it is being
unmarshalled correctly. Even more complex JSON will unmarshall cor
Hi all.
Given that you can use Jackson to unmarshall to "unmarshalTypeName="
(which works for a 1:1 mapping) how does one go about "dynamically
unmarshalling" a JSON document to "N-possible classes?"
eg, full protocol work, based on a piece of the JSON itself.
I can build something using the java
In Spring, you can set the scope='prototype' on a bean to stop it from
being, effectively, a singleton.
The same may work for your context, but I am not sure.
G'luck.
-mox
On Sat, Jul 20, 2013 at 2:01 PM, SyedBhai wrote:
> Hi Guys,
> I have configured camel context in a spring file.
> Sampl
The CSS which is loaded is defined in your HTML. If you're going to use a
parameter to fetch the HTML, you're going to have to dynamically rewrite
that HTML to point to the correct CSS.
Whether you use a handler to rewrite where to get the CSS file, or whether
it shoves all the CSS into the HTML
I believe you can "synthesize" with a dynamic-router.
Get first chunk, route to processor-route. When that route completes, it
will head back to dynamic-router with the same Exchange. If that Exchange
has a property which says "this SQL connection" and a property which says
"this starting number
