va:68)
at
org.apache.camel.component.cxf.CxfSpringEndpoint.(CxfSpringEndpoint.java:61)
at
org.apache.camel.component.cxf.CxfComponent.createEndpoint(CxfComponent.java:64)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:75)
at
org.apache.camel.impl.DefaultCame
Just one comment, if you are using Camel 2.8.x or trunk, you can do it
without any issue. If you are using the version which is below the
2.8.x, you can't do it that way.
On 12/17/11 12:43 AM, Claus Ibsen wrote:
Hi
the is a namespace handler, that will
create a CxfEndpoint and register it in
27.n5.nabble.com/How-to-set-endpoint-id-in-Java-dsl-tp5080518p5080825.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
the is a namespace handler, that will
create a CxfEndpoint and register it in the Registry with that given
id.
In pure Java code for an unit test, you would need to enlist the CXF
endpoint manually.
For example you can use the SimpleRegistry with the
DefaultCamelContext, which is just a Map.
prints:
endpoint1
endpoint2
But again, this's really not nice.
Babak
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-set-endpoint-id-in-Java-dsl-tp5080518p5080679.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have a xml-file with the camel-context, and an endpoint configured
like this:
http://impl.gateway.pumax.company.com/"/>
>From my routebuilder I can use this endpoint:
.to("cxf:bean:CommonServiceEndpoint?dataFormat=PAYLOAD")
But for my test classes I don't want to use the camel-contex
Yes its for debugging purposes.. and exactly like oisin mentioned.
using idorCreate() in the interceptor while initialization of routes is a
good option and this makes us to use the same procedure to generate ids for
visualization nodes too for synchronization. Thanks all.
---
Siva Naresh.
ois
On Wed, Jul 8, 2009 at 10:10 AM, James Strachan wrote:
> I think its for debugging purposes maybe?
Yep - used for synchronization between the Camel route and a visual
representation
of the route that might live somewhere else, for example, in an Eclipse debugger
view.
--oh
2009/7/8 Claus Ibsen :
> Hi
>
> Why do you need the .id in the Java DSL? Are you going to add some
> editor that can edit Java DSL route also?
> Shouldnt we leave that up to the Eclipse Java editor?
I think its for debugging purposes maybe?
But as we've said in this thread, rather than calling ge
Hi
Why do you need the .id in the Java DSL? Are you going to add some
editor that can edit Java DSL route also?
Shouldnt we leave that up to the Eclipse Java editor?
On Wed, Jul 8, 2009 at 7:47 AM, Claus Ibsen wrote:
> On Wed, Jul 8, 2009 at 7:28 AM, siva naresh wrote:
>>
>> from("direct:start"
On Wed, Jul 8, 2009 at 7:28 AM, siva naresh wrote:
>
> from("direct:start").id("A")
> .to("log:foo").id("B")
> .to("mock:result").id("C");
>
> shows a compile error : Method to(String) is undefined for the type
> OperationalIdentifiedType .
> I am not sure how
from("direct:start").id("A")
.to("log:foo").id("B")
.to("mock:result").id("C");
shows a compile error : Method to(String) is undefined for the type
OperationalIdentifiedType .
I am not sure how you were able to run it.
Claus Ibsen-2 wrote:
>
> On Tue, J
2009/7/7 siva naresh :
>
> someNode.getId() is called during debug interceptor call and it should be
> returning whatever was set for that node during initialization of
> camelcontext.
We can just change that to use someNode.idOrCreate() which will only
associate a new ID if there was not one expl
On Tue, Jul 7, 2009 at 4:53 PM, Claus Ibsen wrote:
> On Tue, Jul 7, 2009 at 4:47 PM, siva naresh wrote:
>>
>> someNode.getId() is called during debug interceptor call and it should be
>> returning whatever was set for that node during initialization of
>> camelcontext.
>>
> Hi
>
> Let me add an uni
On Tue, Jul 7, 2009 at 4:47 PM, siva naresh wrote:
>
> someNode.getId() is called during debug interceptor call and it should be
> returning whatever was set for that node during initialization of
> camelcontext.
>
Hi
Let me add an unit test in the Java DSL that sets some custom ids.
And see if I
someNode.getId() is called during debug interceptor call and it should be
returning whatever was set for that node during initialization of
camelcontext.
Siva Naresh.
James.Strachan wrote:
>
> 2009/7/7 siva naresh :
>>
>> The ids are important to identify the endpoint to a front end too
2009/7/7 siva naresh :
>
> The ids are important to identify the endpoint to a front end tooling system.
>
> Using the camel naming system. we get null ids for all the endpoints in the
> multicast case for example.
An even easier fix then, replace the code which does
someNode.getId()
with
some
2009/7/7 Oisin Hurley :
from("file://C:/Debug/from").id("File_0").to("file://C:/test").id("File_1");
>
> This is a pretty cumbersome usage and it kind of clutters up the Java
> for the route - but having ids on the various bits of the pipeline is really
> very useful if you are debugging, or i
>>> from("file://C:/Debug/from").id("File_0").to("file://C:/test").id("File_1");
This is a pretty cumbersome usage and it kind of clutters up the Java
for the route - but having ids on the various bits of the pipeline is really
very useful if you are debugging, or if you are visualizing the overal
The ids are important to identify the endpoint to a front end tooling system.
Using the camel naming system. we get null ids for all the endpoints in the
multicast case for example
from("file://C:/Debug/from").multicast().to("file://C:/from","file://C:/from1","file://C:/from2");
Same is the c
2009/7/7 siva naresh :
>
> Hi all,
>
> I am trying to set ids on every endpoint in the following way.
> But this seems to set ids on the entire route and not on the endpoint.
BTW you had me confused a bit there. At first read I thought you
wanted to do the XML equivalent of
i.e. really to
I tried using both 1.5 and 1.6. The result is the same.
Claus Ibsen-2 wrote:
>
> On Tue, Jul 7, 2009 at 12:58 PM, siva naresh wrote:
>>
>> Hi all,
>>
>> I am trying to set ids on every endpoint in the following way.
>> But this seems to set ids on the entire route and not on the endpoint.
On Tue, Jul 7, 2009 at 12:58 PM, siva naresh wrote:
>
> Hi all,
>
> I am trying to set ids on every endpoint in the following way.
> But this seems to set ids on the entire route and not on the endpoint.
>
> from("file://C:/Debug/from").id("File_0").to("file://C:/test").id("File_1");
>
> How
Hi all,
I am trying to set ids on every endpoint in the following way.
But this seems to set ids on the entire route and not on the endpoint.
from("file://C:/Debug/from").id("File_0").to("file://C:/test").id("File_1");
How do I set ids on every point in Java dsl?
The same is achieved in
24 matches
Mail list logo
