Hello, I'm wondering what Magnolia has decided when it comes to Portlets (JSR-168 etc). Will you work towards supporting this technology? We would like the combination of swift development in magnolia modules and Portlets for advanced apps. Mostly because we have so much of those and dependency issues between parts is a big problem for us. With portlets the dependency issues disappear as each portlet is it's own webapp with it's own classloader.
Also - our server group who handles the Magnolia deployment wants us to only deliver war-files to them and not exploded war-files which seems to be what Magnolia recommends. If you have an exploded war you can upgrade / add modules by just adding a module-jar in WEB-INF/lib but that option is removed if we must run a war-file and instead we must create such a file for each small change to any module. Is there any way to have both. That is - add our modules to another path that the war-file (I cannot think of any standard webapp-way but I thought I'd ask)? Perhaps you have some secret / cool plugin classloader who can be configured to look outside the war? Regards Mattias Bogeblad ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
