Skip to main content

Posts

Showing posts from July, 2016

Overriding default look and feel of GREG - 5.3.0

Following list explains what are the best approach for different use cases. 1 ) - You created a new asset type, and you need to change the look and feel of the details page in the listing page just for that new asset type. To create a new asset type you need to login to the carbon console (username:admin, password:admin) https:// :9443/carbon/ Navigate to Extensions > Configure > Artifacts Click "Add new Artifact" link at the bottom of the page. By default in the "Generic Artifact" area "application" asset type is loaded. Note the shortName="applications" in the root node. "applications" is the name of the asset type. Browse in to /repository/deployment/server/jaggeryapps/store/extensions/assets Create a folder with name "applications"    Now we can override the files in /repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults   Since we are overriding the details page we need to...

Understanding GREG extension hierarchy

GREG is developed on to of Enterprise Store. So the GREG is married to the ES Extension model. By default ES ships few extensions. Following are the list of extensions shipped with ES. Following is the list of additional extensions available with GREG. Following listing have GREG extensions in the left and ES extensions shipped by default on the right hand side GREG - Store & ES - Store (A) - App Extensions GREG ES greg-apis   greg-diff   greg-diff-api   greg_impact   greg_store  greg-store-defaults   greg_swagger   soap-viewer 9.   social-reviews 10. store-apis 11. store-common  (B) - Asset Extensions GREG ES endpoint   policy   restservice   schema   soapservice   swagger   wadl   wsdl 9.   default 10. gadget 11. site GREG - Publisher & ES - Publisher (C) - ...