James.Strachan wrote:
>
>
> I've just patched trunk to lazily create the Jetty server. Also you
> could try using just the HttpComponent rather than the
> HttpJettyComponent if you prefer (which never starts Jetty) to only
> support client side HTTP
>
How do I do that? Something like context.addComponent("http",new
HttpComponent()) ?
James.Strachan wrote:
>
> From reading the source again - it looks like a GetMethod is used,
> unless the body of the Message can be converted to a valid
> RequestEntity. Does this always generate POSTs for you?
>
I read the source as well. It seems that there are multiple returns from
HttpProducer.createRequestEntity and none of them returns null...so
createMethod never returns a GetMethod(uri)? Maybe I shouldn't debug compute
mentally :confused:
James.Strachan wrote:
>
> Another option is to provide some default HTTP operation on the
> endpoint as configuration; or as a header/property on the exchange
> maybe?
>
Not sure how you would accomplish this as http:// uri shares the same syntax
as URI. E.g. how would you know that
http://myurl/myaction?myparam1=x&http_comp_param1=y , the url runs from
http://myurl/myaction?myparam1=x and the second param is intended for the
http component.
This is I guess a limitation of specifying everything on the URI ...
James.Strachan wrote:
>
> Maybe we need to separate out the http-client component from the
> servlet/server side? Another option is to use another component to do
> the polling; something like...
>
> from("timer:foo?period=5000").to("http://www.google.com";, "direct:a")
>
This would work for me, but it still points to the fact that by starting a
server when creating an endpoint, Camel is doing more than integration (EIP
stuff) and starting to host services. Is that the intention of Camel or is
the intention that Camel interfaces with endpoints (of certain component)
and produce/consume from it?
--
View this message in context:
http://www.nabble.com/Consuming-from-a-http-endpoint-tf4314211s22882.html#a12300478
Sent from the Camel - Users mailing list archive at Nabble.com.
