topic Re: Any ideia of modularizing alfresco core? Spring OSGI maybe? in Alfresco Archive

Any ideia of modularizing alfresco core? Spring OSGI maybe?

jbernab — Thu, 18 Oct 2007 01:52:25 GMT

Hi,I have been studying Alfresco, and itÃ‚Â´s internal structure and how plugable it is today, and itÃ‚Â´s very very powerful and I like it very much.But I have one objection to the current structure, today is rather monolitic in the way that I cannot see clearly bundles contributing functionalities

Re: Any ideia of modularizing alfresco core? Spring OSGI maybe?

alexander — Tue, 13 May 2008 17:10:33 GMT

I would agree with Juan.

Alfresco modules are far from ideal and allow quite little (or none) runtime management. It just modifies WAR file that has to be re-deployed (at least for me).

If OSGi is a too big change may be worth looking at Impala - http://code.google.com/p/impala/

Thanks
Alexander

Re: Any ideia of modularizing alfresco core? Spring OSGI maybe?

dbachem — Tue, 03 Jun 2008 16:53:57 GMT

I'm wondering that there is only one single thought about modularization and OSGi to be found in this forum. From an architectural point of view there should be a real interest to use OSGi for state-of-the-art component-based development. Beside this, you should be aware frustrating (potential) users getting down into the "config hell" (http://www.jroller.com/robwilliams/entry/alfresco_and_spring_a_canto). Just do it like SpringSource, Apache Cocoon (Cocoon Blocks) and many other did, bundle your framework!

:arrow: Read here: http://wiki.bjhargrave.com/local--files/start/TS-5122.pdf

So one important thing is to have a look which subcomponents are yet available as OSGi bundles. There are some interesting movements:

SpringSource dm Server: probably the best target platform for Alfresco

http://lucene.apache.org/tika/: Tika is a subproject of Apache Lucene packaged in 3 components - core, parsers und app - which are shipped as OSGi bundles.

and maybe most of your jars should be available in SpringSource bundle repository

In my opinion you should start a separate migration project, maybe together with Optaros or - this would be interesting - with help of SpringSource company.