You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/06/23 15:41:35 UTC
[jira] Moved: (SMXCOMP-574) CXF-BC and CXF-SE should allow separate
configuration for non-default busCfg at component level.
[ https://issues.apache.org/activemq/browse/SMXCOMP-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang moved SM-1872 to SMXCOMP-574:
------------------------------------------
Component/s: (was: servicemix-cxf-bc)
(was: servicemix-cxf-se)
servicemix-cxf-se
servicemix-cxf-bc
Fix Version/s: (was: 3.2.4)
(was: 3.3.1)
servicemix-cxf-se-2009.02
servicemix-cxf-bc-2009.02
3.2.4
Affects Version/s: (was: 3.2.3)
(was: 3.3)
3.2.3
Key: SMXCOMP-574 (was: SM-1872)
Project: ServiceMix Components (was: ServiceMix)
> CXF-BC and CXF-SE should allow separate configuration for non-default busCfg at component level.
> ------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-574
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-574
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-cxf-bc, servicemix-cxf-se
> Affects Versions: 3.2.3
> Reporter: Ulhas Bhole
> Assignee: Ulhas Bhole
> Fix For: 3.2.4, servicemix-cxf-bc-2009.02, servicemix-cxf-se-2009.02
>
>
> Currently CXF-BC and CXF-SE doesn't have a mechanism to configure bus configuration at component level (apart from default cxf mechanism of cxf.xml on classpath which causes problem for CXF-SE as it doesn't have access to all schema).
> This is an enhancement as there is no way to do this currently.
> I am planning to add this feature via configuration which can be set into normal component.properties file which can provide a relative path to busCfg for each (CXF-BC and CXF-SE) which can be used while installing component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.