You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2009/11/10 12:41:52 UTC
[jira] Created: (SMX4-422) CamelCXF does not work if deployed
inside JBI SU
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.
[jira] Commented: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55373#action_55373 ]
Willem Jiang commented on SMX4-422:
-----------------------------------
Hi Sergey,
After digging the code for a while I guess your issue is caused by the CXF BusFactory created a wrong version of BusFactory.
When I added this system property into the SMX/etc/system.properties , the error went way.
{code}
org.apache.cxf.bus.factory=org.apache.cxf.bus.spring.SpringBusFactory
{code}
Willem
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip
>
>
> 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.
[jira] Resolved: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMX4-422.
-------------------------------
Resolution: Fixed
apply patch on behalf of Willem with thanks
http://svn.apache.org/viewvc?rev=882087&view=rev
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip, SMX4-422.patch
>
>
> 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.
[jira] Commented: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56077#action_56077 ]
Freeman Fang commented on SMX4-422:
-----------------------------------
revert the patch as it's not the real fix, take a look at camel-2216
http://svn.apache.org/viewvc?rev=883964&view=rev
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip, SMX4-422.patch
>
>
> 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.
[jira] Updated: (SMX4-422) CamelCXF does not work if deployed
inside JBI SU
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated SMX4-422:
----------------------------------
Attachment: camelcxfProblem.zip
> 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
>
> Attachments: camelcxfProblem.zip
>
>
> 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.
[jira] Commented: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55292#action_55292 ]
Willem Jiang commented on SMX4-422:
-----------------------------------
I can reproduce this error on windows box, but in mac OSX, the client can invoke the service without any error.
> CamelCXF Producer 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
>
> Attachments: camelcxfProblem.zip
>
>
> 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.
[jira] Updated: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated SMX4-422:
----------------------------------
Summary: CamelCXF Producer does not work if deployed inside JBI SU (was: CamelCXF does not work if deployed inside JBI SU)
> CamelCXF Producer 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
>
> Attachments: camelcxfProblem.zip
>
>
> 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.
[jira] Updated: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated SMX4-422:
------------------------------
Attachment: SMX4-422.patch
Please apply this patch on the features module.
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip, SMX4-422.patch
>
>
> 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.
[jira] Assigned: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned SMX4-422:
---------------------------------
Assignee: Willem Jiang
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip
>
>
> 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.
[jira] Commented: (SMX4-422) CamelCXF Producer does not work if
deployed inside JBI SU
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55374#action_55374 ]
Willem Jiang commented on SMX4-422:
-----------------------------------
Since we can use the cxf jars in the SMX 4 from camel-cxf component, and camel-osgi will help the camel-core to load the camel-cxf bundle , so please don't wrap cxf and camel-cxf jars into the camel-su.
> CamelCXF Producer 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
> Assignee: Willem Jiang
> Fix For: 4.1.0
>
> Attachments: camelcxfProblem.zip
>
>
> 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.