Hi Claus,
Now I get it :). In any non trivial case it's useless and could be
confusing/error prone I agree.
I think it is there mostly for convenience for developers, so if we
take it out the inconvenience would be that they'd have to specify the
endpoint (uri) explicitly, which from my point of view is good.
A strong +1 from me on this, but I'd like another opinion too.
Cheers
Hadrian
On Nov 12, 2008, at 1:56 AM, Claus Ibsen wrote:
Hi
Yes I did not make my point clear.
It's the fact that CamelContext requires a default endpoint URI to be
configured. Then you can use ProducerTemplate.sendBody("Hello World")
and then it will send this body the default endpoint URI. Normally you
have to provide the URI as well such as:
ProducerTemplate.sendBody("direct:in", Hello World");
The class DefaultEndpoint should of course be there as the base
class ;)
/Claus
On Tue, Nov 11, 2008 at 10:40 PM, Hadrian Zbarcea
<[EMAIL PROTECTED]> wrote:
Claus,
DefaultEndpoint is the base class for all Endpoints and provides a
default
implementation of the Endpoint methods.
Am I misunderstanding your question?
Hadrian
On Nov 11, 2008, at 2:22 PM, Claus Ibsen wrote:
Hi
I am wondering if this "default" endpoint is used by anyone? I am
wondering what the purpose really is and what it solves. Is it
possible to consider to remove this?
Would remove many methods for ProducerTemplate so less for end users
to get confused by.
--
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
--
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
