Am Donnerstag, 24. August 2006 12:03 schrieb Ben Brock: > Thanks for the reply, Chris. > > >Have your developer(s) pack the xml in with the module so that when the > >module is rev'd you get the new config bootstrapped automatically. > > As an example, do you mean that the dialog xml and paragraph xml would > be checked in with the associated template jsp?
Well, yes. Of course these could be checked in together without making a module too. One could export the xml, and check it into a source code repository. But then they would be just loose files lying about, and you would have to use some sort of potentially error prone home grown technique for getting them installed. > When checked out, how > does these configs get imported/moved? Where do they go on the file > system? Right, that is exactly the problem. You have these development artifacts which need to be put on a server. This is why I sugged you have your developers make a module, because of the ease with which your config data plus templates can be deployed if you have a module. When you have new templates and other associated data, they could arrive in your hands as a simple jar file. Just drop this module jar file into your Magnolia deployment. Restart Magnolia and your new module version is detected and bootstrapped. This can include webserver resources, java script, and other java classes as well. > > >"Magnolia Packager".. I think you can buy it separately. > > Do you know where? We're not using the EE yet. Have a look at: http://www.hirning.de/public/company.html I've checked it out a little, and found it to have all the advantages of creating a module, except you don't have to be a developer to use it. It is nice a way to get the artifacts from a development effort bundled together in a way that makes them easy to archive, upload to a remote server, and deploy. A very nice solution that doesn't require the work of creating a module. Has a nice user interface, doesn't require any special dev skills, ideal tool for a system administrator to use. Chris ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
