facebook

Re-deployment of EAR to server

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #351582 Reply

    eugenejsn
    Participant

    ME Pro 2014 on Linux.

    I set up the IDE to do hot deployment after a change is made. For the server (Jave) side changes, the re-deployment are triggered as soon as the change is made.

    Now for the front end (javascript) changes, everytime I make a change (on the javascript), the redeployment is triggered, I have to wait till the process is complete and restart my web app.

    Is this normal? I believe the front end (javascript changes) should not trigger the re-deployment of the EAR to the server. If I am right, then how to make sure the hot deployment is triggered only if it is necessary, but not always and for any kind of change is made?

    (I used to use the IBM’s RAD IDE version 8. There, the hot redeployment is trigger only if the java class change is made. The changes on JSP and javasctipts do not trigger the redeployment process).

    Thanks

    Eugene

    #351601 Reply

    support-swapna
    Moderator

    Eugene,

    Sorry that you are seeing this issue. I could not replicate the issue at my end. The JS changes do not trigger a redeployment in a hot sync environment.

    Can you please give us some more information ?

    1. Are you deploying the project in exploded or packaged mode? For the hot deployment to work, the project must be deployed in ‘Exploded mode’ and the server must be started in Debug mode (right click on the server in the servers view and select ‘Debug Server’).

    2. When you enable hot deployment, the hot sync happens seamlessly behind. There is no trigger for redeployment as such. Please switch to a new workspace, configure the server for hot deployment by starting it in debug mode and check if the issue persists.

    3. Can you please check on an external browser instead of the MyEclipse Browser to see the issue persists ? Sometimes it might also be caching issue. Please clear the cache of your browser and retry.

    4. If you are still seeing issues, please prepare a sample project which exhibits the issue and send it over to us to help replicate the issue at our end. Also share the exact version details of the server you are working with.

    #351607 Reply

    eugenejsn
    Participant

    1. Are you deploying the project in exploded or packaged mode?

    –Exploded mode.

    For the hot deployment to work, the project must be deployed in ‘Exploded mode’ and the server must be started in Debug mode (right click on the server in the servers view and select ‘Debug Server’).

    –Yes. I did just that.

    3. Can you please check on an external browser instead of the MyEclipse Browser to see the issue persists ? Sometimes it might also be caching issue. Please clear the cache of your browser and retry.

    –I used the external browser.

    Regardless where I make the change in my project, the re-dployment will be triggered, at the end, it will display:

    10:52:04,024 INFO [org.springframework.web.servlet.DispatcherServlet] (MSC service thread 1-12) FrameworkServlet ‘dispatcher’: initialization completed in 409 ms
    10:52:04,025 INFO [org.jboss.web] (MSC service thread 1-12) JBAS018210: Registering web context:
    10:52:04,122 INFO [org.jboss.as.server] (DeploymentScanner-threads – 1) JBAS018559: Deployed “MyWebEAR.ear”

    Please duplicate the issue using the following settings:

    1. ME Pro 2014 (I also tested on ME Blue 2014 same thing happened)
    2. 64 bit SUSE Linux OS (other Linux may be OK)
    3. JBoss AS 7.1.1 optional arguments: –server-config=standalone-ha.xml (I also tested iton the default standalone.xml. The same thing happened)
    4. Create a web project with EAR project.

    Whatever a change is made, may it be in a java class or javascript, as soon as the change is saved, the auto-redeployment will be triggered. You can observe it on the console, the re-deployment process is going on simultaneously. At the end, it will display something like:

    Deployed “MyWebEAR.ear”

    If I uncheck the Project –> Build Automatically. The re-deployment will not be triggered. BUT the changes made will not be picked up when testing the project.

    I still suspect that this is the MyEclipse IDE issue, for the following reasons:

    1. I worked on the exact same web application using the IBM’s RAD IDE version 8. There, restarting the application server is not needed unless the change is made on a java class . The changes on JSP and javasctipts do not need to restart or redeploy the EAR file.

    2. Now I test the same web application using MyEclipse Pro (or Blue alike), the previously mentioned issue occurred.

    3. You mentioned you could not duplicate the issue. I would assume when you did the testing, you might use a very simple web application so the auto-redeployment of the EAR file is quite fast so fast that it is undetectable. I am different that I used the business strength application which needs longer redeployment time, hence I can feel the time lag during the auto-redeployment process.

    If still not solvable, I would recommend to forward this issue to your development team, hopefully they can figure it out or fix it.

    I have used IBM’s RAD IDE for 8 years and recently switched to MyEclipse. My feeling is that the IBM RAD IDE is very solid and detailed tool, as the contrast, the MyEclipse IDE is somewhat coming short, here or there, a little bit here or a little bit there. Like a car you drive it, you can feel it.

    It is just those details.

    Thanks

    Eugene

    #351615 Reply

    Eugene,

    Sorry that you are facing issues with MyEclipse.

    We still couldn’t replicate the issue at our end on Linux machine. Can you please clarify if the ‘use auto-deploy mode’ is selected/checked under Window > Preferences > MyEclipse > Servers > JBoss > JBoss 7.x ? If yes, please make sure that the ‘use auto-deploy mode’ option is unchecked. (After unchecking the option please make sure you restart the JBoss server ).

    If the ‘use auto-deploy mode’ option is checked or if the flag ‘auto-deploy-exploded’ in the standalone.xml file is set to true, a change in any file in an exploded deployment triggers redeploy. Please take a look at this link for more information.

    Can you please try using MyEclipse 2015 CI and see if the issue persists there, as there were some improvements done in this area. You can download MyEclipse 2015 CI from here and install it alongside your existing MyEclipse 2014 installation.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Re-deployment of EAR to server

You must be logged in to post in the forum log in