Dashlets flexibility

[simon]

Alfresco,

The new dashlets are great and we are trying to include these in our project but I have a few questions concerning the flexibility of these components.

I need a JSP page on the file system and I have to change the web-client configuration file for every dashlet which means I have to restart Alfresco to make sure they are picked up. This isn't very nice in a production environment. This also means I have to replicate these changes in every environment (dev, qa and production) making it more error prone.

Is there any workaround for these issues or are there any plans to integrate the JSP's in the Alfresco repository?

Thanks!

[enalon]

All you need is a second, clusterized instance of Alfresco and some JavaScript in the dashboard templates.

[simon]

Thanks enalon but I don't see how you will solve this with JavaScript, can you explain this?

Do you cluster Alfresco? Does it work as expected? Was it hard to setup?                                       How does it work when you upgrade one of your nodes, do you bring down every instance and upgrade all in one?

We didn't look into clustering yet but isn't it a little overkill for my "dashlet flexibility" problem?

[alexander]

It might be a solution to use JSPs that execute Freemarker templates from Data Dictionary folder.

I think default ones are running from file system, but it should be possible to pull templates from repository too. It may require new beans, not sure.