Hi Pulasthi Let's add this feature to the pack and test inside G-Reg. We might identify some more blockers, if there is any.
On Thu, Jun 19, 2014 at 12:54 PM, Sameera Medagammaddegedara < [email protected]> wrote: > Hi, > > This mail thread will track the vital changes that are expected from the > ES for the next GREG release.The following list indicates the issues based > on priority: > > 1. https://wso2.org/jira/browse/STORE-441. Create an ES feature that > will designate apps with an es prefix > 2. https://wso2.org/jira/browse/STORE-430, Can't use RXT without > provider > 3. https://wso2.org/jira/browse/STORE-428, SQL based social > implementation > 4. https://wso2.org/jira/browse/STORE-440, Add support for > documentation tab > 5. https://wso2.org/jira/browse/STORE-442, Asset extension files will > need to be stored on a per tenant basis > 6. https://wso2.org/jira/browse/STORE-443, Allow each asset type to > define its own artifact manager > > > *STORE-441* > > - We have created a new store feature : org.wso2.es.feature > - This can be accessed from > https://github.com/wso2/enterprise-store/tree/greg-changes-store-feature > - This needs to be tested > > > *STORE-430* > > - When testing this with the service.rxt that uses the namespace > attribute in the storage path we noticed that the namespace value was been > set to null. > - This is a result of the way the GenericArtifact instance is created > prior to been added > - When adding through the carbon console the artifact is constructed > with a QName element that explicitly recieves the name and namespace > - However, the ES uses an overloaded version of the newGenericArtifact > method that does not set the namespace > - In the add method the namespace is not taken from the attribute list > but rather by calling a getNamespaceURI method.This namespace is then > written back to the attribute list > - Since the ES implementation does not set a namespace value the > namespace attribute ends up been null > - Thus, when saving services using the ES they do not follow the > storage path > - *Solution:* > - Allow each asset type to override the artifact manager > - This is already supported in the Store > > *STORE-442* > > - We already store the publisher and store config files based on the > tenant > - This will need to be extended to support extension configuration > files > - We will also need to think about how we can store template and > script files of asset types > > Thank You, > Sameera > -- > Sameera Medagammaddegedara > Software Engineer > > Contact: > Email: [email protected] > Mobile: + 94 077 255 3005 > -- Thanks /subash *Subash Chaturanga* Senior Software Engineer & Lead WSO2 Governance Registry Platform TG; WSO2 Inc. http://wso2.com Contact: email: [email protected] blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
