facebook

WTP spring+maven legacy projects interoperability

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

    ecapoccia
    Member

    Hi,
    I’m trying to switch from plain Eclipse Kepler to MyEclipse Pro; I’m having some issues deploying legacy WTP spring+maven based project on the Tomcat server. I have completed successfully the migration of the old projects.

    I’m still able open the workspace with the old kepler installation, and run the server with no problems; but when I try to deploy the same project to myeclipse embedded tomcat, then it fails on startup with some spring errors (Caused by: org.hibernate.DuplicateMappingException: duplicate import) which are not there when I start the application on plain kepler (for sake of completeness, the duplicate entities are in different packages, and are not loaded at the same time; they are legacy code which I cannot refactor).

    Apparently, myeclipse is loading the spring context differently from WTP, and I would like to understand and control the way it bootstraps the spring context; I need to interoperate with NON-myeclipse projects transparently, but would like to keep the benefit of running my eclipse.

    Can somebody help?

    #346232 Reply

    ecapoccia
    Member

    I forgot to mention, I’m using the mac version of MyEclipse Pro, and these instructions:
    http://www.myeclipseide.com/module-htmlpages-display-pid-443.html
    do not apply for such a version.

    #346257 Reply

    support-piotr
    Participant

    Hi Eecapoccia,

    We are sorry that you are having issues with switching from Eclipse JEE Kepler to MyEclipse. With MyEclipse 2013 or 2014 you should be able to share the same workspace with Eclipse JEE without troubles. The help page you have pointed to is no longer accurate and WTP projects require no special actions to be usable with ME 2013/2014 other then migration of target runtime.

    I would recommend you setting up a connector for the same Tomcat installation you are using with WTP. The issue you are reporting looks to be related to the server configuration rather then project configuration/deployment issue. However, to be sure, I would advise comparison of deployments created by WTP and ME. If you encounter any differences, please let us know and we will gladly assist you!

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: WTP spring+maven legacy projects interoperability

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