facebook

Problem with Exploded(classic) deployment mode

  1. MyEclipse IDE
  2.  > 
  3. Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #314382 Reply

    sathis.g
    Member

    Hi all,

    I have a simple EAR and WAR project. My WAR project web.xml looks some like this..

    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee   http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <display-name>Sample</display-name>
     <servlet>
      <servlet-name>test</servlet-name>
      <servlet-class>com.sample.TestServlet</servlet-class>
     </servlet>
     <servlet-mapping>
      <servlet-name>test</servlet-name>
      <url-pattern>/test</url-pattern>
     </servlet-mapping>
    </web-app>

    When i tried to deploy the above Application in WAS 7.0 using Exploded (Classic) style.
    Everything looks fine, but when browse the deplyment folder, i failed to find the tag <display-name> in the web.xml. The above web.xml looks likes this after deployment.

    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee   http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <servlet>
      <servlet-name>test</servlet-name>
      <servlet-class>com.sample.TestServlet</servlet-class>
     </servlet>
     <servlet-mapping>
      <servlet-name>test</servlet-name>
      <url-pattern>/test</url-pattern>
     </servlet-mapping>
    </web-app>

    Hence the API call ServletContext.getServletContextName() does not yield correct result.
    This works correct in all other mode.

    I’m using MyEclipse 8.5, Build id: 8.5-Blue-20100319 and WAS 7.0

    #314415 Reply

    support-swapna
    Moderator

    sathis.g,

    1) Can you recheck if the issue is with Exploded or Packaged deployment? I checked on it and I can replicate it for packaged deployment and the exploded deployment works fine.

    2) Right click on the WAS 7.0 under the Servers tab and select ‘Configure Server Connector’. Send us the screenshot of your WAS 7.0 basic configuration.

    3) Can you also send us detailed steps about how you are adding application for deployment to the WAS 7.0 ?

    #314421 Reply

    sathis.g
    Member

    Hi,

    1. Yes the issue is there in both Exploded and packaged deplpyment.mode but if i export the EAR from the IDE it looks fine.

    2.

    3. Right click Server and choose Add Deplyoment. In the Project field select the correct EAR file and choose the Exploded mode. Click Finish” alt=””>

    #314464 Reply

    sathis.g
    Member

    Any update on this issue. It looks to me as bug in Version 8.6

    #314537 Reply

    support-swapna
    Moderator

    sathis.g,

    I could replicate it at my end for MyEclipse 8.6. Earlier I checked on ME 8.5 as you mentioned that you were working on it.I will file a PR for the dev team to look into it.
    Sorry for the inconvenience caused.

    #317667 Reply

    sathis.g
    Member

    Any fix available for this.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Problem with Exploded(classic) deployment mode

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