facebook

Refactoring WS name does not change deployment name

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #327765 Reply

    mongonv
    Participant

    I have had two cases now where using the refactoring to change the name of a JAX-WS web service project does not end with the generated deployment name changing .

    For example, change a project from “WsTemp16” to “WsTemp” still generates a WAR and internal tomcat deployment of “WsTemp16” for the URL needed to access the application.

    The only way I have been able to get around the generation issue is to create a new project and copy the settings and contents from the old one, this of course is not a reasonable solution.

    The project name and all references I can find reference the new “WsTemp” name, so does any know how to get ME to actually generate to the new name?

    I am using ME 10.5 on windows to do the development work.

    Thanks for any thoughts,
    Ed

    #327777 Reply

    support-swapna
    Moderator

    mongonv,

    Can you clarify if you have updated the context root for the project? You will have to update the web context root to the new name, from project > Properties > MyEclipse > Web > Context root.

    A Refactor/Rename would additionally need an update to the context root. Please change it and check if you are still seeing the issue.

    Let us know how it works for you.

    #327788 Reply

    mongonv
    Participant

    Thanks Swapna, That was the problem, changed that and it has the right web app name now.

    #327818 Reply

    support-swapna
    Moderator

    mongonv,

    Glad that it is working.
    Do let us know if you see any issues.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Refactoring WS name does not change deployment name

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