Re: Using camel-jetty options in recipient List

[pratham <pr...@gmail.com>]

Hi Claus ,

According to what you said , there are 2 tables :

"options"  - this can be configured in the uri 
"component options" - for jetty endpoint

i did not get what you meant by "enableJmx is on the component only" .
Infact enableJmx option appears in both the tables.

Now , 'chunked' appears in the options table . That means this can be
configured in the endpoint uri. It works when specified in <from> tag as
shown below:

/<route trace="true" id="SimpleProxy">
			<from
uri="jetty:http://0.0.0.0:8299/test2?matchOnUriPrefix=true&amp;chunked=false"
/>
			<to uri="http://0.gravatar.com/avatar?bridgeEndpoint=true" />
</route>/

My understanding is jetty will start a process to listening on port 8299
(this being a consumer(server) endpoint). So when we set 'chunked' to false
and access http://0.0.0.0:8299 in browser , the response headers contain
'content length' header. and on setting chunked to true the response header
will content 'transfer encoding' header instead of content length. This
behavior is clear to me.

However if i have a snippet like below:
/
    <recipientList>
        <simple>jetty:http://localhost:10001/callback?chunked=false</simple>
    </recipientList>/

or :
<to uri="jetty:http://localhost:10001/callback?chunked=false"/>

Is the use of 'chunked' or 'enableJmx' in the uri's above incorrect ?. Both
are listed under options table which can be configured in the endpoint uri.

Thanks




--
View this message in context: http://camel.465427.n5.nabble.com/Using-camel-jetty-options-in-recipient-List-tp5773399p5774627.html
Sent from the Camel - Users mailing list archive at Nabble.com.