Confused about modules versus extensions and config files

[mxc]

Hi all,

I am a little confused about share customisations. Are extensions and modules the same thing? Aren't amps just supposed to be modules? Also as far as customisation go I see some references to a *-extension.xml config file  (see blog-extension.xml)

http://blogs.alfresco.com/wp/developer/2013/09/04/customizing-the-share-header-menu-part-1/


and most to a *-modules.xml file. (extension-modules.xml)

http://docs.alfresco.com/4.2/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Ftasks%2Fdev-extensions...


and some imply any file with .xml (see blog-demo.xml)

http://blogs.alfresco.com/wp/developer/2011/07/22/how-to-add-content-to-an-alfresco-share-page/

Which one is correct? Do all of them work? When would I use the one approach over another

[mitpatoliya]

You First need to understand the Surf platform as (blog-demo.xml)file is part of new page creation in surf.

Extension Modules are advance way through which you can hook in your code to extension points given by alfresco. So, these *-modules.xml files are related to those extension module.You can also name it as blog-extension.xml so both of those files serve same purpose.

So, In Nutshell Extension modules are one way to extend alfresco share. Consider Extension as Super set and Extension Module as one of the way to achieve that. I could not think of  any more logical analogy for this as of now

[mxc]

Thanks for the answer. I also found this stack overflow answer helpful

http://stackoverflow.com/questions/12569495/what-is-the-file-structure-of-the-share-webscript-extens...