topic Feature request: TemplateNode Factory & ScriptNodeFactory in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/feature-request-templatenode-factory-scriptnodefactory/m-p/259148#M212278 <HTML><HEAD></HEAD><BODY><SPAN>We have developed an Alfresco module in-house that adds extra functionality. For certain reasons we have needed to add extra functionality to the ScriptNode and the TemplateNode, but in doing so we have had to over-ride the definition of these classes, since the current architecture does not take into account a module needing to extend the functionality of theses classes.</SPAN><BR /><BR /><SPAN>If these two classes were generated via a factory, then it would allow us to easily extend these classes through inheritance, rather than redefinition. Using the TemplateNode as an example, I see something like this:</SPAN><BR /><PRE class="language-none line-numbers"><CODE><BR />&lt;bean id="templateNodeFactory" <BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; class="org.alfresco.repo.template.TemplateNodeFactory"<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; p:serviceRegistry-ref="serviceRegistry" /&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><PRE class="language-none line-numbers"><CODE><BR />public class TemplateNodeFactory<BR />{<BR /><BR />&nbsp;&nbsp;&nbsp; private ServiceRegistry services;<BR />&nbsp;&nbsp;&nbsp; private TemplateImageResolver resolver;<BR />&nbsp;&nbsp;&nbsp; <BR />&nbsp;&nbsp;&nbsp; @Required<BR />&nbsp;&nbsp;&nbsp; public void setServiceRegistry( ServiceRegistry services ) <BR />&nbsp;&nbsp;&nbsp; {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.services = services;<BR />&nbsp;&nbsp;&nbsp; }<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <BR />&nbsp;&nbsp;&nbsp; public void setTemplateImageResolver( TemplateImageResolver resolver ) <BR />&nbsp;&nbsp;&nbsp; {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.resolver = resolver;<BR />&nbsp;&nbsp;&nbsp; }<BR />&nbsp;&nbsp;&nbsp; <BR />&nbsp;&nbsp;&nbsp; /**<BR />&nbsp;&nbsp;&nbsp;&nbsp; * Creates a new TemplateNode for the nodeRef<BR />&nbsp;&nbsp;&nbsp;&nbsp; * <BR />&nbsp;&nbsp;&nbsp;&nbsp; * @param nodeRef<BR />&nbsp;&nbsp;&nbsp;&nbsp; * @return<BR />&nbsp;&nbsp;&nbsp;&nbsp; */<BR />&nbsp;&nbsp;&nbsp; public TemplateNode createTemplateNode( NodeRef nodeRef )<BR />&nbsp;&nbsp;&nbsp; {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return createTemplateNode(nodeRef,this.services,this.resolver);<BR />&nbsp;&nbsp;&nbsp; }<BR />&nbsp;&nbsp;&nbsp; <BR />&nbsp;&nbsp;&nbsp; /**<BR />&nbsp;&nbsp;&nbsp;&nbsp; * Creates a new TemplateNode for the nodeRef<BR />&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; <BR />&nbsp;&nbsp;&nbsp;&nbsp; * @param nodeRef<BR />&nbsp;&nbsp;&nbsp;&nbsp; * @param services<BR />&nbsp;&nbsp;&nbsp;&nbsp; * @param resolver<BR />&nbsp;&nbsp;&nbsp;&nbsp; * @return<BR />&nbsp;&nbsp;&nbsp;&nbsp; */<BR />&nbsp;&nbsp;&nbsp; protected TemplateNode createTemplateNode( <BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NodeRef nodeRef, <BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ServiceRegistry services,<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TemplateImageResolver resolver )<BR />&nbsp;&nbsp;&nbsp; {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return new CoreTemplateNode(nodeRef, services, resolver);<BR />&nbsp;&nbsp;&nbsp; }<BR />&nbsp;&nbsp;&nbsp; <BR />}<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>The factory class could then be extended to return the appropriate implementation. There are probably other ways of going about this, but this would certainly be helpful.</SPAN><BR /><BR /><SPAN>Edit: The same factory implementation could be reused, simply using reflection and specifying the class to be instantiated as a property:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&nbsp;&nbsp;&nbsp; /* templateNodeClass node would be specified as a bean property, p:templateNodeClass="package.MyTemplateNode" */<BR />&nbsp;&nbsp;&nbsp; protected TemplateNode createTemplateNode( NodeRef nodeRef, ServiceRegistry services, TemplateImageResolver resolver )<BR />&nbsp;&nbsp;&nbsp; {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; try {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Constructor&lt;TemplateNode&gt; constructor = templateNodeClass.getConstructor(NodeRef.class,ServiceRegistry.class,TemplateImageResolver.class);<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return constructor.newInstance(nodeRef,services,resolver);<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } catch (Exception ex) {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; throw new RuntimeException(ex);<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<BR />&nbsp;&nbsp;&nbsp; }<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE></BODY></HTML> Fri, 29 Apr 2011 19:59:58 GMT ajmas 2011-04-29T19:59:58Z Feature request: TemplateNode Factory & ScriptNodeFactory https://connect.hyland.com/t5/alfresco-archive/feature-request-templatenode-factory-scriptnodefactory/m-p/259148#M212278 We have developed an Alfresco module in-house that adds extra functionality. For certain reasons we have needed to add extra functionality to the ScriptNode and the TemplateNode, but in doing so we have had to over-ride the definition of these classes, since the current architecture does not take in Fri, 29 Apr 2011 19:59:58 GMT https://connect.hyland.com/t5/alfresco-archive/feature-request-templatenode-factory-scriptnodefactory/m-p/259148#M212278 ajmas 2011-04-29T19:59:58Z Re: Feature request: TemplateNode Factory & ScriptNodeFactory https://connect.hyland.com/t5/alfresco-archive/feature-request-templatenode-factory-scriptnodefactory/m-p/259149#M212279 <HTML><HEAD></HEAD><BODY><SPAN>This is probably better shared as a feature request in Jira.</SPAN><BR /><BR /><SPAN>Jeff</SPAN></BODY></HTML> Wed, 15 Feb 2012 21:10:16 GMT https://connect.hyland.com/t5/alfresco-archive/feature-request-templatenode-factory-scriptnodefactory/m-p/259149#M212279 jpotts 2012-02-15T21:10:16Z