facebook

Spring configuration changes not deployed

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #326458 Reply

    Hi,

    For the past few weeks I am facing this trouble. I have made changes to the configuration file in my spring project. The changes are saved to disk. But when I deploy it to tomcat. The older version of the xml file gets deployed. Another issue I have been facing since Myeclipse 8 is the changes in javascript code(code in standalone js file) does not get hot deployed.

    Please direct me to a solution as soon as possible ?

    #326474 Reply

    support-swapna
    Moderator

    venakatasreekanth,

    Sorry that you are seeing this issue.

    Can you give us some more details ?

    1. Can you please copy paste the Installation Details from MyEclipse > Installation Summary > Installation Details ?

    2. Which version of Tomcat are you working with ? Do you see the same issue with Sandbox Tomcat too?

    3. Can you check if the server is started in Debug mode and the project is deployed in Exploded mode ?

    4. Do you see the same issue for all xml files or specific to Spring configuration file ?

    5. Can you please switch to a new workspace, create a sample web project and check if you see the same issue ?

    #326490 Reply

    Installation summary:

    *** Date:
    Wednesday, May 30, 2012 10:50:28 AM CDT

    *** System properties:
    OS=WindowsVista
    OS version=6.1.0
    OS arch=amd64
    Profile arch=x86_64
    Window system=win32
    Java version=1.6.0_13
    Workspace=file:/C:/NPO/RB-1.8/
    VM Args=-Xmx1024m
    -XX:MaxPermSize=512m
    -XX:ReservedCodeCacheSize=512m
    -Dosgi.nls.warnings=ignore
    -jar
    C:\MYECLI~2\../MYECLI~1/Common/plugins/ORB7B5~1.JAR

    *** Subscription information
    Product Id: E3MP (MyEclipse Professional Subscription)
    License version: 3.0
    Full Maintenance Included
    Subscription expiration date (YYYYMMDD): 20140310
    Number of users: 30

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 10.1
    Build id: 10.1-20120316

    Blueprint: MyEclipse 10

    com.genuitec.myeclipse.database – 10.1.0.me201203170059
    com.genuitec.myeclipse.desktop – 10.1.0.me201203170059
    com.genuitec.myeclipse.editor – 10.1.0.me201203170059
    com.genuitec.myeclipse.enterprise.workbench – 10.1.0.me201203170059
    com.genuitec.myeclipse.geronimo – 10.1.0.me201203170059
    com.genuitec.myeclipse.glassfish – 10.1.0.me201203170059
    com.genuitec.myeclipse.icefaces.feature – 10.1.0.me201203170059
    com.genuitec.myeclipse.iedebugger – 10.1.0.me201203170059
    com.genuitec.myeclipse.imageeditor – 10.1.0.me201203170059
    com.genuitec.myeclipse.jboss – 10.1.0.me201203170059
    com.genuitec.myeclipse.jetty – 10.1.0.me201203170059
    com.genuitec.myeclipse.jonas – 10.1.0.me201203170059
    com.genuitec.myeclipse.jrun – 10.1.0.me201203170059
    com.genuitec.myeclipse.jsf – 10.1.0.me201203170059
    com.genuitec.myeclipse.matisse – 10.1.0.me201203170059
    com.genuitec.myeclipse.maven – 10.1.0.me201203170059
    com.genuitec.myeclipse.oracle – 10.1.0.me201203170059
    com.genuitec.myeclipse.orion – 10.1.0.me201203170059
    com.genuitec.myeclipse.persistence – 10.1.0.me201203170059
    com.genuitec.myeclipse.pulse – 10.1.0.me201203170059
    com.genuitec.myeclipse.reports – 10.1.0.me201203170059
    com.genuitec.myeclipse.resin – 10.1.0.me201203170059
    com.genuitec.myeclipse.struts – 10.1.0.me201203170059
    com.genuitec.myeclipse.sun – 10.1.0.me201203170059
    com.genuitec.myeclipse.tomcat – 10.1.0.me201203170059
    com.genuitec.myeclipse.uml2 – 10.1.0.me201203170059
    com.genuitec.myeclipse.visualvm – 10.1.0.me201203170059
    com.genuitec.myeclipse.visualvm.server – 10.1.0.me201203170059
    com.genuitec.myeclipse.weblogic – 10.1.0.me201203170059
    com.genuitec.myeclipse.websphere – 10.1.0.me201203170059
    com.genuitec.myeclipse.ws – 10.1.0.me201203170059
    org.eclipse.birt – 2.6.1.me201203170059
    org.eclipse.datatools.connectivity.feature – 1.9.0.me201203170059
    org.eclipse.datatools.enablement.feature – 1.9.0.me201203170059
    org.eclipse.datatools.sqldevtools.feature – 1.9.0.me201203170059
    org.eclipse.jpt.jpa.feature – 3.0.0.me201203170059
    org.eclipse.jpt.jpadiagrameditor.feature – 1.0.0.me201203170059
    org.eclipse.jst.common.fproj.enablement.jdt – 3.3.0.me201203170059
    org.eclipse.jst.enterprise_ui.feature – 3.3.0.me201203170059
    org.eclipse.jst.server_adapters.ext.feature – 3.3.0.me201203170059
    org.eclipse.jst.server_adapters.feature – 3.2.100.me201203170059
    org.eclipse.jst.server_ui.feature – 3.3.0.me201203170059
    org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201203170059
    org.eclipse.m2e.feature – 1.0.0.me201203170059
    org.eclipse.wst.common.fproj – 3.3.0.me201203170059
    org.eclipse.wst.server_adapters.feature – 3.2.100.me201203170059
    org.springframework.ide.eclipse.feature – 2.7.1.me201203170059

    com.collabnet.subversion.merge.feature – 2.2.4
    org.eclipse.cvs – 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C
    org.eclipse.equinox.p2.core.feature – 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129
    org.eclipse.equinox.p2.extras.feature – 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO
    org.eclipse.equinox.p2.rcp.feature – 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO
    org.eclipse.equinox.p2.user.ui – 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl
    org.eclipse.help – 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
    org.eclipse.jdt – 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
    org.eclipse.jsf.feature – 3.3.0.me201203170059
    org.eclipse.pde – 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E–0
    org.eclipse.platform – 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q
    org.eclipse.rcp – 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272
    org.tigris.subversion.clientadapter.feature – 1.6.12
    org.tigris.subversion.clientadapter.svnkit.feature – 1.6.15
    org.tigris.subversion.subclipse – 1.6.18
    org.tigris.subversion.subclipse.graph.feature – 1.0.9

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86_64
    -showsplash
    -launcher
    C:\MyEclipse 10\myeclipse.exe
    -name
    Myeclipse
    –launcher.library
    C:\MyEclipse 10\../MyEclipse/Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_4.2.0.v201201111650\eclipse_4201.dll
    -startup
    C:\MyEclipse 10\../MyEclipse/Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
    -exitdata
    d40_5c
    -install
    C:\MyEclipse 10
    -configuration
    C:\MyEclipse 10\configuration
    -vm
    C:\MyEclipse\Common\binary\com.sun.java.jdk.win32.x86_64_1.6.0.013\bin\javaw.exe

    I am using tomcat 6 and yes it is the same issue with sandbox tomcat. Also, I have also checked the file on the deployed directory after completely deleting the app from tomcat and redeploying it. This issue has nothing to do with tomcat.

    yes, the server is in debug mode and the code deployed in exploded mode.

    I think all xml files.

    I actually deleted the workspace and checkout the project again and it has the same issue.

    #326532 Reply

    support-swapna
    Moderator

    venakatasreekanth,

    Thank you for the details. I could replicate the issue with xml only when there were missing jar files in my project. I could not replicate the issue with the standalone js file hot deployment.

    1. Can you check if you can export the project as WAR file ? Do you see any error messages in the .log file which is located at<workspace dir>/.metadata/.log while trying to export the project as WAR file ? If yes paste them here for us.

    2. Can you recheck if the project is not missing any files or jars ? Go to project > Build Path > Configure Build Path and check if you see any red marks ?

    3. I suggest you create a web project, add Spring capabilities to it and check if you see the issue instead of checking with the existing project.

    Let us know how it works for you.

    #326548 Reply

    @support-swapna wrote:

    venakatasreekanth,

    Thank you for the details. I could replicate the issue with xml only when there were missing jar files in my project. I could not replicate the issue with the standalone js file hot deployment.

    1. Can you check if you can export the project as WAR file ? Do you see any error messages in the .log file which is located at<workspace dir>/.metadata/.log while trying to export the project as WAR file ? If yes paste them here for us. – yes I can export it as war

    2. Can you recheck if the project is not missing any files or jars ? Go to project > Build Path > Configure Build Path and check if you see any red marks ? – no red marks. this app is in production and will certainly cannot afford to have missing jar files.

    3. I suggest you create a web project, add Spring capabilities to it and check if you see the issue instead of checking with the existing project. – I want the project I am working on to work properly not some random project which is of no use to me.

    Let us know how it works for you.

    #326549 Reply

    venakatasreekanth,

    Thank you for the details. I could replicate the issue with xml only when there were missing jar files in my project. I could not replicate the issue with the standalone js file hot deployment.

    1. Can you check if you can export the project as WAR file ? Do you see any error messages in the .log file which is located at<workspace dir>/.metadata/.log while trying to export the project as WAR file ? If yes paste them here for us. – yes I can export it as war

    2. Can you recheck if the project is not missing any files or jars ? Go to project > Build Path > Configure Build Path and check if you see any red marks ? – no red marks. this app is in production and will certainly cannot afford to have missing jar files.

    3. I suggest you create a web project, add Spring capabilities to it and check if you see the issue instead of checking with the existing project. – I want the project I am working on to work properly not some random project which is of no use to me.

    Let us know how it works for you.

    #326564 Reply

    support-swapna
    Moderator

    venakatasreekanth,

    1. Can you check if the exported WAR file contains the updated XML file ?

    2. Can you clean the project and check if the updated XML file get deployed ?

    3. The reason I wanted you to try with a new project is to rule out issues with deployment. It might be project specific. If you can confirm that you are not seeing the issue with a new project it would help our investigation as we are not seeing the issue at our end.

    #326821 Reply

    @support-swapna wrote:

    venakatasreekanth,

    1. Can you check if the exported WAR file contains the updated XML file ?

    2. Can you clean the project and check if the updated XML file get deployed ?

    3. The reason I wanted you to try with a new project is to rule out issues with deployment. It might be project specific. If you can confirm that you are not seeing the issue with a new project it would help our investigation as we are not seeing the issue at our end.

    1. The exported contains the updated xml
    2. I have done numerous times with no benefit.
    3. I refuse to believe it is project specific. How can it be project specific ? The project contains only java code, xml config files and jsp. How are they a hindrance to deploying the right file (How is myeclipse picking up older files for deployment, is it caching the files some where ? these are the questions you should be asking ?). Are you part of the myeclipse development team. Can you verify that you code is working as it should and not otherwise ?

    #326865 Reply

    support-tony
    Keymaster

    venakatasreekanth,

    To recap, your issue is that any xml file in the project that is changed will not be deployed to the server in its updated form, only the form it was originally in when you first deployed the project. Is this correct? Does the updated file get deployed if you deploy immediately after restarting your workbench?

    We just want to be clear of the pattern here as we are having difficulty replicating the problem. We could only reproduce the issue when something stopped the build process (such as the missing jar files that Swapna mentioned), leaving the original xml file in the output directory. From that, I would have suggested that the output folder (somewhere under the web root folder) was not being fully updated and so something was failing in the build. However, you say that the updated XML file is getting exported to a WAR file (assuming you are using the “Export->Java EE->WAR file” function), so that would seem to rule out this explanation. I can confirm that MyEclipse does not cache the old file (though the old file is available from eclipse Local History, of course).

    As Swapna, explained, we cannot replicate the problem with a new Web project (either by adding Spring capability to get an applicationContext.xml file, or simply adding an xml file to the project) and so I can confirm that MyEclipse is working as expected, for the projects we’ve tried. Consequently, it might either be project specific or something in your setup that is causing your problem. This is the reason we’d like you to try the simple test of creating a Web project, adding an xml file and checking it gets deployed when updated. Also, it would help if you could clear the .log file, edit the xml file, deploy and then send us the resultant .log file.

    One last question, please try cleaning the project after editing the xml file (Project->Clean) to see if that affects the issue. Obviously, this is not something we would expect you to do in normal development but is just to help us resolve this problem for you.

Viewing 9 posts - 1 through 9 (of 9 total)
Reply To: Spring configuration changes not deployed

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