Glassfish 3.1.2 deployment changes

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

    Scott Dunbar

    Hi all,
    I’ve recently upgraded my Glassfish installation to 3.1.2 – the current version available. Unfortunately, Glassfish seems to have changed the autodeploy naming conventions. Before 3.1.2 MyEclipse would create domain/domain1/appname.war and I would access it at http://localhost:8080/appname. Now, however, I need to access it at http://localhost:8080/appname.war.

    Is there any configuration I can do to prevent the Glassfish chunk of MyEclipse to not put the .war on now? To me this is a Glassfish bug/breaking change but I wondered if there was a quick way to have MyEclipse handle it.

    Thanks for any info.

    #324009 Reply


    stdunbar ,

    Thank you for pointing to it.I have filed a PR for the dev team to investigate the issue.
    They are looking into it now.

    #324046 Reply



    We are still investigating this though I think you’re right that Glassfish is now treating the full name of the exploded directory as the context root.

    I see that you’ve raise an issue against Glassfish, so I hope that gets picked up soon. However, there is a better workaround than changing the context root in the admin console each time. You can specify the context root in a glassfish-web.xml file. This file should be in the WEB-INF directory, alongside the web.xml file. Here is a sample, for just setting the context root:

    <!DOCTYPE glassfish-web-app PUBLIC "-//GlassFish.org//DTD 
    GlassFish Application Server 3.1 Servlet 3.0//EN" 

    I hope this helps.

    #324086 Reply

    Scott Dunbar

    Gaah! Too many years of changing between app servers and I forget about the app server specific config files! And 4 years at BEA with tons of them too.

    Excellent, simple work around – thank you very much!

    #324093 Reply



    Life is getting much too complicated in our line of business! And we thought things were meant to get simpler.

    So I guess you’re saying that this was a problem with earlier glassfish releases too. We should still do something about it, though, so the problem report will stay.

    I’m glad you’re back working to full capacity and thanks for getting back to us.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Glassfish 3.1.2 deployment changes

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