On Apr 5, 2012, at 10:17 AM, Carlo de Wolf wrote:
On 04/04/2012 05:01 PM, Max Rydahl Andersen wrote:
> And all this override would be via management API's, not doable with any
deployment-scanner operations?
>
> i.e. can I do something like:
>
> cd overridestuff
> cp * to
> /data/contents/xyz.war/
>
>
> now xyz.war has an "incomplete" override of xyz.war
> which will be "overlayed" on to deployment named xyz.war (independent on
wether it comes from deployment scanner or management api)
>
> or is it all just via management api's that would need to be executed on every
restart/change to the data/contents folder ?
>
> /max
>
How about?
standalone/deployments/xyz.war.part01/
standalone/deployments/xyz.war.part02/
standalone/deployments/xyz.war.part03/
touch standalone/deployments/xyz.war.dodeploy
I like that but I thought these were ment to be put in a separate location than
/deployments ? (if not then +1)
/max