Hi Claus,
Unfortunately, this issue reproduces with the last 2.2-SNAPSHOTS artifacts
from the apache.snapshots repo...
I managed to workaround it the way I previously explained :
- routing the multicast bean to a "direct:webservices" channel,
- wiring "direct:webservices" and
"direct:webservices-
On Fri, Feb 5, 2010 at 10:08 AM, Olivier Billard
wrote:
>
> Hi Claus,
>
> Unfortunately, this issue reproduces with the last 2.2-SNAPSHOTS artifacts
> from the apache.snapshots repo...
> I managed to workaround it the way I previously explained :
> - routing the multicast bean to a "direct:webserv
Many thanks for your answer, Claus!
I indeed use an ActiveMQ queue as the dead letter channel endpoint.
But my question was more on the beginning of the Camel pipeline: if a crash
happens between my two Beans (multicast and content-based router), connected
via the direct: channels, I suspect them
On Fri, Feb 5, 2010 at 11:32 AM, Olivier Billard
wrote:
>
> Many thanks for your answer, Claus!
>
> I indeed use an ActiveMQ queue as the dead letter channel endpoint.
> But my question was more on the beginning of the Camel pipeline: if a crash
> happens between my two Beans (multicast and conten
Hi,
Suppose I have camel context containing cxf endpoints which is to be used
within WAR on tomcat.
In web.xml I have CXFServlet configured plus ContextLoaderListener which
will read the camel context.
Within camel context I have camel cxf endpoint
and other stuff so I'd like to test the whole
Hi,
You can take a look at the camel-example-reportinstance[1]
It shows a way for how to write the unit test for you case.
Basically , it just uses the jetty tranpsort instead of the servlet one
to do the unit test.
[1]https://svn.apache.org/repos/asf/camel/trunk/examples/camel-example-reporti
so you mean I just need to use other url in endpoint configuration e.g.
through properties so that it can be replaced in the context?
and the code you refer to is just this? :
// We should use the related path to publish the service, when using
the ServletTransport
String cxfEndp
Yes.
If you are using cxfEndpoint tag within Spring Configuration, you just
need to set the cxfEndpoint's address with a properties variable.
Willem
Lukasz Lichota wrote:
so you mean I just need to use other url in endpoint configuration e.g.
through properties so that it can be replaced in t
