Hi All,
I like to get a clarification regarding OAth ui feature and
databridge.datareceiver features in our platform.
1. In OAth UI feature
<includedFeatures>
<includedFeatureDef>org.wso2.carbon:org.wso2.carbon.jaxws.webapp.mgt.server.feature:4.0.2</includedFeatureDef>
<includedFeatureDef>org.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.2</includedFeatureDef>
</includedFeatures>
Why does the ui feature need server features like above?
And why have these external features included instead of being imported?
Generally we use includedFeatureDef in an aggregate feature to include it's
sub features and we use ImportFeatureDef to import external features.
2. In databridge.datareceiver feautre
Same question with including external features instead of defining them as
import-features.
<includedFeatureDef>org.wso2.carbon:org.wso2.carbon.jaxws.webapp.mgt.server.feature:${carbon.platform.patch.version.402}</includedFeatureDef>
<includedFeatureDef>org.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:${carbon.platform.patch.version.402}</includedFeatureDef>
Is there a particular reason we have included above features instead of
importing them?
Thanks,
Dileepa
--
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware
Mobile : +94777-857616
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
