Hi Ashwin,
Well i added the start as follows:
public void configure() throws Exception {
getContext().start();
getContext().addInterceptStrategy(new MyFromEndpointInterceptor());
from("jbi:service:http://oxp/oXpInternalService";)
.process(new OXpServicesAu
Hi Liav,
Have you add the code in the configure() method. The reason for this issue
can be one of two things
- The Camel listener has not been setup. This means the code is called
before context.start()
- The dependencies cannot be resolved (i.e the jar containing
org/apache/camel/spi/Inter
nojonojo wrote:
>
> I'm possibly interested in working with camel-restlet (2.0, since it
> doesn't exist before then). First off, is there any documentation besides
> that on http://camel.apache.org/restlet.html the restlet component page ?
>
> I'm having two problems. The first is conceptua
Hi,
Can you send me your test case, and which version of camel are you using?
It's looks like a cxfEndpoint configuration issue.
Willem
S. Ali Tokmen wrote:
> Hello again
>
> I now have a very annoying exception:
>
>java.lang.NullPointerException
> at
>
> org.apache.cxf.wsdl11
Yea, agreed with lacking documentation on this component. (I guess
contribution is always welcomed :-))
On the NoSuchMethodError, javadoc says, "Normally, this error is
caught by the compiler; this error can only occur at run time if the
definition of a class has incompatibly changed." So, are
I'm possibly interested in working with camel-restlet (2.0, since it doesn't
exist before then). First off, is there any documentation besides that on
http://camel.apache.org/restlet.html the restlet component page ?
I'm having two problems. The first is conceptual - the page that I linked
abo
Hello again
I now have a very annoying exception:
java.lang.NullPointerException
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:81)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromWSDL(ReflectionServiceFactoryBea
Hi,
I was able to get an acceptable solution working, so I won't try anymore until
we eventually have to upgrade. Since we are using Camel 1.4.0, I suspect there
are multiple issues at hand. Just to recapitulate:
FooProcessor sets the body of the out message of the incoming exchange. In the
in
Hi
Ah how does the code in your interceptor looks like. It could be its
constructor failing.
You can try with a empty implementation or try using the Tracer
getContext().addInterceptStrategy(new Tracer());
Tracer is shipped with Camel and it should work
On Tue, Jan 20, 2009 at 4:43 PM, Liav E
2009/1/20 Matvey :
>
> I still have several questions about Spring/JMS/Camel/POJO mapping.
>
> Question 1
> for example I have Spring config file:
>
>
>
> http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:camel="http://active
Hi Ashwin,
My processor works great - if i remove the
getContext().addInterceptStrategy(new MyFromEndpointInterceptor()); line
everything is smooth.
Can you think of a reason why i get this exception?
framework.beans.factory.BeanCreationException: Error creating bean with name
'camelContext': I
I still have several questions about Spring/JMS/Camel/POJO mapping.
Question 1
for example I have Spring config file:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="http://activemq.apache.org/camel/schema/spring";
Please try the last verion of Camel 1.5.1-snapshot or Camel 2.0-snapshot.
I just fixed some bus related issue in camel-cxf component.
Willem
S. Ali Tokmen wrote:
> Hello, Willem
>
> The cxf:bus approach would be exactly what I need, but when I enable it
> I have the impression Camel-CXF ignores
Hello, Willem
The cxf:bus approach would be exactly what I need, but when I enable it
I have the impression Camel-CXF ignores all of it. Did you try out
anything similar?
Thanks
S. Ali Tokmen
savas-ali.tok...@bull.net
Office: +33 4 76 29 76 19
GSM:+33 66 43 00 555
Bull, Architect of an
Just one more note, please take a look at CXF example[1][2], when you
run mvn install in the camel-example-cxf, you will see the generated
PingMeFault in the targe/generated/src/main/java directory.
[1] http://svn.apache.org/viewvc/camel/trunk/examples/camel-example-cxf
[2] http://camel.apache.org
Hi Lars,
Can you show me the detail code of FooProcessor() ?
If you take a look at the PipeLine(which chains these endpoints and
processor together), you will find the codes about copying exchanges
between these endpoints and processors.
// now lets set the input of the next exchange to the
Hi guys,
I've got the following scenario. I want to receive a HTTP Message, put the
received message into a queue, wait for response and give the response back
as HTTP response.
My spring.xml looks like that:
http://activemq.apache.org/camel/schema/spring";>
Hi
You can set the interceptors into cxf bus[1], then all the CXF endpoints
create by CAMEL will use them.
[1]http://cwiki.apache.org/CXF20DOC/bus-configuration.html
Willem
S. Ali Tokmen wrote:
> Hello, Pawel
>
> Thank you for this quick response. I now have another issue: I would
> actually be
Hi Liav,
Have you checked the packages in the camel context block of the
camel-context.xml in the resources directory to see if the Camel processor
have been correctly defined.
Cheers,
Ashwin...
Liav Ezer wrote:
>
> Hi,
>
> I use servicemix-fuse 3.3.1.3 with Camel 1.4.
> In my Camel Builde
Hi Matvey,
The approach of throwing an exception and returning the message to the queue
in order to process another message that can be processed quicker is not a
good solution. It is prrocessing expense incurred for no real value.
I would rather create 2 queues or 1 virtual queue/topic in activ
Congratulations to Camel
The next step will be to write a book : "Camel in action"
Regards,
Charles
SOA Architect
Hadrian Zbarcea wrote:
>
> Hi,
>
> Most of you probably know already that the Apache Board voted at the
> last meeting (Dec 17th, 2008) on a resolution that makes Camel a top
Hello, Pawel
Thank you for this quick response. I now have another issue: I would
actually be interested in defining these properties globally, i.e. for
all CXF endpoints created by CAMEL. This way, people programming the
routes would only use CXF URLs and not create the CXF beans by hand.
T
22 matches
Mail list logo