And as per the discussion with Sameera and Manu, this is the recommended approach for any product that wants to embed ES functionality. On Sep 1, 2015 4:49 PM, "Shabir Mohamed" <[email protected]> wrote:
> Hi, > > *As per the offline conversation:* > > Given that our intention is make use of the Enterprise-Store for Products > using CDMF, I have added a new (wrapper) feature into the CDMF pack and > have defined it to be importing the ES features via the > *<importFeatureDef>* tags. Note that this enforces the installation of > the ES-feature at the product level and does NOT pack any of the features > into CDMF. > > The purpose is to explicitely make it evident for someone using the CDMF > pack that it is ported with ES-features for Device-Type listing. > > Regards > > ------------------------------------- > *Shabir Mohamed* > *Software Engineer* > WSO2 Inc.; http://wso2.com > Email: [email protected] <[email protected]> > Mobile: +94 77 3516019 | +94 71 6583393 > > On Tue, Sep 1, 2015 at 10:26 AM, Shabir Mohamed <[email protected]> wrote: > >> Hi ES Team, >> >> I am trying to integrate ES features into the CDMF pack. >> >> I am going about doing this by creating a new feature inside the CDMF >> pack and importing the *<featureArtifactDef> s *found in the >> "Product-ES" profile-gen into the new CDMF feature as *<importFeatureDef> >> s. * >> >> Is this procedure right and will it give me a CDMF feature that wraps >> ES-Features. If so, what are the minimum set of ES-specific >> *<featureArtifactDef>s *found in Product-ES that I need to import. >> >> Thanks >> ------------------------------------- >> *Shabir Mohamed* >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> Email: [email protected] <[email protected]> >> Mobile: +94 77 3516019 | +94 71 6583393 >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
