4 Replies Latest reply on Sep 26, 2011 12:35 PM by Gary Brown

    Exploded deployments

    Gary Brown Master

      Hi

       

      Would it be possible to enable a component to indicate whether it required an exploded deployment, and for the AS6/7 integrations to use that info to determine whether it should explode the deployment before activating the component? (Also making the exploded path available to the component).

       

      The problem I have is that ODE expects everything to be expanded in the file system, and to change it to use the virtual filesystem approach would be a significant change.

       

      In general it probably would not be a good idea for the switchyard components to use AS6/7 specific stuff anyway, to make it more portable.

       

      Alternatively I could explode the jar into a tmp area, bypassing the virtual filesystem, just to enable ODE to load the relevant artifacts and compile the bpel process?

       

      Regards

      Gary

        • 1. Re: Exploded deployments
          Keith Babo Master

          Hey Gary,


          Is this as an alternative to the approach where we simply require an exploded deployment if a given component is used?

           

          cheers,

          keith

          • 2. Re: Exploded deployments
            Keith Babo Master

            And by "we require" I mean that it's a requirement stated in the documentation.

            • 3. Re: Exploded deployments
              Gary Brown Master

              Hi Keith

               

              Yes the last para was intended to provide an alternative solution that would not require any change to switchyard, in case you preferred not to provide such a mechanism.

               

              However when I implemented this alternative mechanism (as a temporary workaround for now to make progress) I found that I needed to use AS7 specific knowledge to locate the deployment jar.

               

              The variable 'jboss.server.deploy.dir' unfortunately points to $as7/standalone/data/content, which always appears to be empty, instead of the expected $as7/standalone/deployments folder.

               

              So although I could provide a configurable mechanism to support different containers, if this may become a common requirement then it might be better supported in switchyard.

               

              Regards

              Gary

              • 4. Re: Exploded deployments
                Gary Brown Master

                Hi Keith

                 

                Just to let you know, this is no longer a requirement for the bpel component, as for other reasons I need to control the unpacking of the switchyard app containing the bpel processes.

                 

                Regards

                Gary