- This topic has 1 reply, 2 voices, and was last updated 7 years, 11 months ago by
.
-
Posts
-
From user:
In our experience, MyEclipse 2016 does not deploy Java code changes to the local WAS server unless you switch the project to “Classic” deployment mode and do an explicit Project > Clean. It does however auto-deploy JSF xhtml changes without doing a Clean. It would be good if hot deployment of Java code worked without having to do an explicit Clean. It also doesn’t catch build errors after synchronization (pulling down the latest code) until you do a Clean. In short, our team of 5-6 developers have gotten used to cleaning their workspaces constantly: after synchronizing and before deployments. We rarely had to Clean with MEB10.
In addition, it would be good to have clear documentation from Genuitec on how these server options differ from one another and when they should be used:
• Publish
• Republish
• Clean (redeploygjt3,
Sorry that you are seeing problems. Clean is certainly not required for the hot deployment to work.
Can you please clarify if the Project > ‘Build Automatically’ is turned on? For hot deployment to work, the ‘Build Automatically’ must be turned on, in addition to setting the WAS deployment mode to ‘Classic’.
Please also check if the server’s Publishing setting is set to ‘Automatically publish when resources change’. Double click on the WAS server in the Servers view to open the Overview page in the editor. Expand the Publishing section. Attached is the screenshot for your reference.
The default mode is ‘In-workspace’. This mode deploys EAR files from the Workspace location rather than being copied to the WebSphere profile location. It is the fastest mode and synchronization of resources and code is handled by WebSphere directly.
About the server options :
1. The Publish option in the server tab will deploy the application to your server instance by copying the project resources such as xml configuration files , web resource (html ,css, js etc) , and the compiled .class files you get from the “project > Build” to the correct location for the server to find and use them.
2. Republish status is displayed in the Servers view if applications are out of sync.Either you should restart the server or manually select ‘Publish’ on the server to sync the changes.
3. Clean(redeploy) : Publishing syncs only project changes to the application server. If you want fresh deployments, you can select Clean (redeploy) from the menu. This removes all deployed applications, and redeploys the projects in their entirety. Clean is generally used to remove any old code or an invalid state of code running on the server before doing a full republish.
If you are still seeing issues, then please share with us the MyEclipse Version and Build Id details from Help > About MyEclipse section along with the exact version of WAS. Also share with us more details about the project (Web/EAR) for further investigation. Please also share with us what exact code changes in the Java classes that are not being picked up for hot deployment.
Apologies for inconvenience caused. Please let us know how it works for you.
–Swapna
MyEclipse Support
