Hi Senaka, I'm looking in to this now. Will update this thread once completed.
Regards, SanjayaV. On Fri, Oct 26, 2012 at 9:45 AM, Senaka Fernando <[email protected]> wrote: > Hi Samisa, > > Yes, it does (and there can be several other features that have similar > issues). There are several reasons to why this fails. The human tasks > feature requires: > > 1. A database (H2 by default) > 2. A human task configuration file (has default values). > 3. A new datasource that needs to be added to datasources.properties. > > Now, though we have gone ahead with the feature management stuff, we > haven't found proper answers to some of these questions such as: > > 1. How to pack a DB inside a feature or create it as a part of the > installation procedure. > 2. How to modify an existing configuration file by adding some entries to > it. > > Simply because 90% of our features will work with a "feature installs some > jars and copies some files" model, it does not mean that all features will > work that way. This is why we are having issues with the HT feature. Its > nothing G-Reg specific - if you try to install BPS features to ESB for > instance, you'll be running into the same issues. So, IMO, unless we can > find answers to questions like the above and propose best practices for > feature-authors to follow, the feature management story is broken. > > Thanks, > Senaka. > > On Fri, Oct 26, 2012 at 7:04 AM, Samisa Abeysinghe <[email protected]>wrote: > >> >> >> On Thu, Oct 25, 2012 at 8:06 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi Samisa, >>> >>> Human Tasks are used for Management Console notifications right now. We >>> will be using it more in the upcoming releases: for approvals (before state >>> transitions in a lifecycle) and for managing deadline for remaining in a >>> lifecycle state etc. Also, we just have the BE and don't have any FE stuff >>> of human tasks. >>> >> >> It is this feature that is casing the G-Reg feature set to fails when >> installed on another server. >> >> >>> >>> Thanks, >>> Senaka. >>> >>> On Thu, Oct 25, 2012 at 1:14 PM, Samisa Abeysinghe <[email protected]>wrote: >>> >>>> >>>> Thanks, >>>> Samisa... >>>> >>>> Samisa Abeysinghe >>>> VP Engineering >>>> WSO2 Inc. >>>> http://wso2.com >>>> http://wso2.org >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Senaka Fernando* >>> Member - Integration Technologies Management Committee; >>> Technical Lead; WSO2 Inc.; http://wso2.com* >>> Member; Apache Software Foundation; http://apache.org >>> >>> E-mail: senaka AT wso2.com >>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>> Linked-In: http://linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> > > > -- > *Senaka Fernando* > Member - Integration Technologies Management Committee; > Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > -- Sanjaya Vithanagama WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 342 2881
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
