- This topic has 5 replies, 3 voices, and was last updated 9 years, 7 months ago by Brian Fernandes.
-
AuthorPosts
-
Tony HerstellParticipantWildfly
MyEclipse->add/remove->add…->Wildfly (always use)->Ok…
Does NOT deploy (but shows as deployed) ERROR ERRORclick on Servers and the deployment and select menu->Publish
NOW it deploys.
So you can now start the server… and see your project.
Tony HerstellParticipantServers->Project->Remove
does not remove…then doing clean (redploy) does clean it away…
All very strange…
support-pradeepMemberbalanceofpower,
This is an expected behaviour. If you deploy the project when the server is offline, project resources are added to deployment location only when the server is started or when you press Publish.
Similarly, if you remove the project (Server > Project > Remove) when the server is offline, you need to perform Server > Clean (redeploy) to remove the project resources from the deployment location. If you remove the project (Server > Project > Remove) when the server is running, it will directly remove the project resources from the deployment location, without any need for performing Server > Clean(redeploy).
Hope this helps.
Tony HerstellParticipantPradeep,
I read your reply at 3am as I could not sleep; and then after digesting your reply I was so shocked I could not go back to sleep.
Is this serious? (this is British understatement for the person who designed this needs psychiatric help).
If I understood you right, you are saying that, after years of deployment actually deploying to the deployment area of the server you are now saying it’s going to change to be like magic and you have to start your server to see what projects magically appear… this is simply insane.
Lets do some work…. you go into the menu option and do “deploy to server” and select your server and then, err.. it doesn’t and later auto-magically it’s supposed to magically turn up when you start the server (It doesn’t do this anyhow and certainly does not add the .dodeploy file as needed by wildfly).
A lot of time you deploy your project and then go into the deployment area (yes there is a shortcut to go into this area once you deploy your project) and examine your deployed files to see what was deployed as part of debugging.
Now; imagine a busy office; you export your project to the server and then get interrupted; you turn back to you IDE and can’t remember where you were up to…. what do you do? you have to run the server to find out which, err. hold on… what was I up to…
Come on guys; this is madness! if you deploy; you deploy!
support-pradeepMemberbalanceofpower,
I have escalated your concern to our dev team, they will get back to you soon.
Brian FernandesModeratorTony,
The deploy behavior change was something we inherited from the webtools server framework. We discussed this change and ultimately decided to stick with the new behavior – I believe it was needed for a variety of technical reasons to support the framework as well as to cleanly support some of the new features the framework provides.
Now, as was discussed earlier in the thread, the Publish action will go ahead and push your changes to the server (so you don’t need to actually start the sever). To address your concerns about not knowing what you’ve done, the Status field should give you an idea – it will be blank (when not actually pushed to the server even once) or Synchronized or Republish for instance.
What wizard do you normally use to deploy? Do you use the Add Remove Project Deployments action (project’s context menu) or the deploy toolbar button or perhaps Run As > MyEclipse server application (though this one will automatically publish as well). Would the option (in the appropriate place) to automatically publish your actions meet your needs?
(It doesn’t do this anyhow and certainly does not add the .dodeploy file as needed by wildfly).
I’ll ask the team to look into this separately.
-
AuthorPosts