-
1. Re: Enabling manual deployment
zhurlik Sep 16, 2019 3:00 PM (in response to gbrown1)Hi,
What happens when you set auto-deploy-zipped = true
Thanks,
Vlad
-
2. Re: Enabling manual deployment
gbrown1 Sep 16, 2019 3:06 PM (in response to zhurlik)Isn't that the default? If so, that also does not resolve the problem.
-
3. Re: Enabling manual deployment
zhurlik Sep 16, 2019 3:45 PM (in response to gbrown1)Are you dropping a zip file?
-
4. Re: Enabling manual deployment
gbrown1 Sep 16, 2019 3:49 PM (in response to zhurlik)No, as I mentioned in my original post it is an exploded EAR (a folder).
-
5. Re: Enabling manual deployment
zhurlik Sep 16, 2019 3:57 PM (in response to gbrown1)I guess you need to use ear file instead of a folder, based on Admin Guide - JBoss AS 7.0 - Project Documentation Editor
auto-deploy-exploded BOOLEAN Controls whether exploded deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content. -
6. Re: Enabling manual deployment
gbrown1 Sep 16, 2019 4:00 PM (in response to zhurlik)I have auto-deploy-exploded set to false, and I have a .dodeploy marker file. Based on the documentation you posted (and I have already read), I would expect this configuration to work.
-
7. Re: Enabling manual deployment
zhurlik Sep 16, 2019 4:16 PM (in response to gbrown1)Hmm... I remember that once I had issues with deployment and it was related with .war and .dodeploy files and last modified dates, could you check them via ls -l
-
8. Re: Enabling manual deployment
jaikiran Sep 19, 2019 12:21 AM (in response to gbrown1)When you say manual deployment, do you mean you want to have the application deployed, through the standalone/deployments folder, once when teh server boots up? Or do you mean you want to use management APIs to trigger the deployment even when server is up and running.
FWIW, setting scan-enabled to false (like in the config you pasted) altogether disables looking for deployments in the directory configured for the scanner and that's what you are seeing in your tests.
-
9. Re: Enabling manual deployment
gbrown1 Sep 19, 2019 7:43 AM (in response to jaikiran)Yes. I am basically looking for a way to hard-code the applications I want deployed, vs. having the deployment scanner try to figure it out dynamically.
-
10. Re: Enabling manual deployment
ctomc Sep 19, 2019 7:55 AM (in response to gbrown1)look at deploying your application via cli and "deploy" command.
just be careful with parameters it takes to deploy exploded archive.
-
11. Re: Enabling manual deployment
gbrown1 Sep 19, 2019 8:06 AM (in response to ctomc)OK. I was hoping I might be able to do it declaratively, in standalone.xml or something similar. Thanks for your help.
-
12. Re: Enabling manual deployment
ctomc Sep 19, 2019 3:24 PM (in response to gbrown1)the deploy command will result in some extra configuration being written to standalone.xml.
take notice the part with <deployment> tag(s)
Once you get hang of what are all the options and what result in xml is, you can do it declarative.