CamelCXF does not work if deployed inside JBI SU
------------------------------------------------
Key: SMX4-422
URL: https://issues.apache.org/activemq/browse/SMX4-422
Project: ServiceMix 4
Issue Type: Bug
Affects Versions: 4.1.0
Reporter: Sergey Beryozkin
Fix For: 4.1.0
1. install SMX 4 snapshot
2. Unzip the project
3. Build it starting from the root, the result is a camelcxf-smxcxf-sa.zip in
camelcxfproblem/jbi/camelcxf-smxcxf/camelcxf-smxcxf-sa/target/camelcxf-smxcxf-sa.zip
This JBI SA consists of a number of SUs (see
camelcxfproblem/jbi/camelcxf-smxcxf/) but the SU of interest is
camelcxf-smxcxf-camel1-su. The route is supposed to work as follows :
* an http message is picked up from an http jbi endpoint (see
camelcxf-smxcxf-http-su) and is forwarded to a remote addess using a
camelcxf component. This request will be handled by cxfbc, cxfse and eip
SUnits and the response will be forwarded to
log:soapresponse. Camel context also declares another route. But at the
moment the first route does not work (camelcxf)
due to NoConduitInitiator...
4. So, to reproduce an issue, just drop this SA into /deploy folder and then
start camelcxfproblem//client.html and send a SOAP
message, and you'll see the exception...
Note that I've commented <import> statements in camelcxf-smxcxf-camel1-su
xbean.xml (and corresponding deps in
camelcxfproblem/jbi/camelcxf-smxcxf/camelcxf-smxcxf-camel1-su/pom.xml), just
for you to start from where I started. I've tried with
imports too but it did nnot make any difference
[ Show ยป ]
Sergey Beryozkin added a comment - 10/Nov/09 11:35 AM 1. install SMX
4.2-fuse-SNAPSHOT 2. Unzip the project 3. Build it starting from the root, the
result is a camelcxf-smxcxf-sa.zip in
camelcxfproblem/jbi/camelcxf-smxcxf/camelcxf-smxcxf-sa/target/camelcxf-smxcxf-sa.zip
This JBI SA consists of a number of SUs (see
camelcxfproblem/jbi/camelcxf-smxcxf/) but the SU of interest is
camelcxf-smxcxf-camel1-su. The route is supposed to work as follows :
* an http message is picked up from an http jbi endpoint (see
camelcxf-smxcxf-http-su) and is forwarded to a remote addess using a camelcxf
component. This request will be handled by cxfbc, cxfse and eip SUnits and the
response will be forwarded to log:soapresponse. Camel context also declares
another route. But at the moment the first route does not work (camelcxf) due
to NoConduitInitiator...
4. So, to reproduce an issue, just drop this SA into /deploy folder and then
start camelcxfproblem//client.html and send a SOAP message, and you'll see the
exception... Note that I've commented <import> statements in
camelcxf-smxcxf-camel1-su xbean.xml (and corresponding deps in
camelcxfproblem/jbi/camelcxf-smxcxf/camelcxf-smxcxf-camel1-su/pom.xml). I've
tried with imports too but it did not make any difference
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
