-
1. Re: Exploded deployments
kcbabo Sep 14, 2011 9:27 PM (in response to objectiser)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
kcbabo Sep 14, 2011 9:28 PM (in response to kcbabo)And by "we require" I mean that it's a requirement stated in the documentation.
-
3. Re: Exploded deployments
objectiser Sep 15, 2011 4:36 AM (in response to kcbabo)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
objectiser Sep 26, 2011 12:35 PM (in response to objectiser)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