Hi, We read the http://wiki.magnolia-cms.com/display/WIKI/How+to+install+Magnolia+on+Jboss but that may be outdated. It says: "Copy/Move exploded WAR with jboss-web.xml to your Jboss deploy directory (JBOSS_HOME/server/default/deploy), making sure that the directory name ends with '.war'.". Perhaps that entry should be changed or elaborated so it explains what you must do to run as war. After I wrote the question we configured our war to have the repository data outside of the deployment dir (that could be explained also in the above article perhaps).
On the war-issue: the problem I have is that our marketing department are demanding a very very agile and fast time to market for new functionlaity. They today have a situation where the full war contains 200+ subprojects and historically an upgrade required full regression testing of all functionality which lead to releases only being done 4 times a year. A key issue is to get away from this and get a more modular and agile development/release cycle. Being able to deploy only project specific jars/modules like I explained could have given us some options. But I agree its not ideal and that is why I asked about portlets and OSGI as that could solve the issue more elegant. Regards Mattias Bogeblad ________________________________________ Från: [email protected] [[email protected]] för =?ANSI_X3.4-1968?Q?Magnolia_Forums_=28on_behalf_of_Gr=3Fgory_Joseph=29?= [[email protected]] Skickat: den 9 maj 2011 18:52 Till: Magnolia Dev List Ämne: [magnolia-dev] Re: Magnolia and Portlets etc Hey Mattias, I'll deliberately leave parts of your questions out, hoping someone else picks them up. [quote] 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. [/quote] What ? Where does that come from ? If someone from the company recommended that to you, I'll have to publicly whip their ass ;-) Seriously though, there is no need to deploy exploded wars, provided you understand the [url=http://documentation.magnolia-cms.com/cookbook/using-a-single-war-file-with-multiple-configurations.html]configuration mechanism[/url] for that. [quote] 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? [/quote]I don't really get your question. Yes, if you update a module (be it yours, or a third party used by your installation), you'll have to rebuild the war file for deployment. I'm not sure you're implying that could be a problem, but if you do, I don't understand ;) Provided the creation of the .war (exploded or not)is part of your project - and it should be!! - then .. what's the big deal ? Of course, if you have been building war files "manually" for your projects instead of relying on a build tool to do it for you along with your modules/content/what have you, then it's a pain in the ass. If that's the case, hopefully, the link above will give you incentive to stop doing that. Essentially, updating a Magnolia-based project should be as smooth as updating a .war file (and/or the context configuration to point to a new version of that file) and kick the appserver to pick it up. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=7c6a3ba6-1ccb-4fac-8a9d-b3f9022cc80b ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
