8 Replies Latest reply on May 25, 2005 9:01 PM by Alexander Wallace

    Installer friendly SARDeployer

    Scott Stark Master

      So I'm back to prototyping an installer based on the IzPack tool (http://developer.berlios.de/projects/izpack/) and it seems sufficiently capable of handling the type of installs we need. This main issue I'm seeing with trying to achieve a true cananonical installer with every service being an optional element with dependencies (which IzPack supports), is that we need to manifest the dependencies in the service descriptors in order for things to startup correctly. Right now we have a lot of implicit dependencies that just happen to be satisfied due to placement of services in the correct order in the conf/jboss-service.xml and correct naming of deployer/sar/*-service.xml in the deploy directory.

      For the first iteration I'm just breaking up the services into their independent jars, conf files, deployment descriptors to allow for a minimal installation that supports the selected services by layering these into the dist structure. I could create an object model that reflects the service dependencies and does write out the dependencies, but this is a lot more work for the initial prototype.

      Instead, I'm thinking that if the SARDeployer just accepted a dependency graph in terms of the service names, that could be used instead in a less intrusive fashion. I don't see any reason why this should not work, and it might have some benefit to users as well.