wcm-bootstrap-context.xml should not be in extension directory
As a neat-freak sysadmin, I like to keep my configuration strictly separate from vendor supplied defaults. I do this by:
1. Configuring Alfresco by editing files in the Alfresco/tomcat/shared/classes/alfresco/extension/ directory, using the existing files as examples and guides.
2. Deleting everything I didn't touch. I consider this safe, as each file also exists in Alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/ where the real default values are stored.
All except wcm-bootstrap-context.xml; I cannot find any corresponding default for this file.
If it is vendor supplied, I expect it to be included in the war instead of polluting my client-side configuration directory. I only expect samples and examples to be there. The convention is to label such files as .sample, though there are a couple of files named example* or custom*. wcm-bootstrap-context.xml violates this convention.
[This issue has been reassigned to email@example.com as part of the Alfresco cloud migration project. The reporter of this issue was resplin]
The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.
[This comment has been reassigned to firstname.lastname@example.org as part of the Alfresco cloud migration project. The author of this comment was wtaylor] This issue has been re-triaged and determined as “Won’t Fix” and Closed.
Many factors were considered in this decision, among which is the need to correctly prioritise the work of the Engineering team and be clear with those issues that are not going to be resolved.
[This comment has been reassigned to email@example.com as part of the Alfresco cloud migration project. The author of this comment was srigby] Review for inclusion in 3.3E or for future
[This comment has been reassigned to firstname.lastname@example.org as part of the Alfresco cloud migration project. The author of this comment was mrogers] I agree with the direction of this issue. However its a bigger issue than just the spring config file. The WCM bootstrap is an oddity since it augments the WAR file rather than just being part of the existing alfresco.war. So, for example, as well as the wcm bootstrap spring configuration file it also adds a whole new tomcat instance for the VS and adds new scripts to the bin directory.
In 3.2 the WCM samples were removed from the WCM bootstrap to be their own download package. I think we need to continue with this idea. And as and when the VS is removed the wcm bootstrap will become smaller again. And we can think about how we repackage the wcm-bootstrap-bootstrap.xml
With 3.2 we begun to implement the idea of a "Web Delivery Runtime" but never bottomed out the detail. It's also becoming clear that we need to think through how the Web Authoring environment is packaged.