After package extraction in DMT,the web.xml files appear as ignored when seen in package content and are not defined in the analysis unit as indicated in the screenshot below.
Release | Yes/No |
|---|---|
| 8.2.x |  |
| 8.1.x | |
| 8.0.x | |
| 7.3.x | |
| 7.2.x | |
| 7.0.x |  |
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS2 | |
| CSS1 | |
- Package the J2EE application in Delivery Manager Tool.
- Check the Package content.
- Web.xml files are ignored.
CASE 1: Issue with the option 'Exclude basic JSP project when a full JEE project also exists for the same web.xml file'
The Solution is to deselect the check-box with the option 'Exclude basic JSP project when a full JEE project also exists for the same web.xml file' to include the web.xml files in the package.
Note
The web.xml are ignored in two cases:
1)If there are empty projects inside
2)If there are no nature projects
The option 'Exclude basic JSP project when a full JEE project also exists for the same web.xml file' is the one to exclude them if they qualify for any of the above cases.
The main purpose of project natures is to create an association between a project and a given tool, plug-in, or feature set. By adding a nature to a project, you indicate that your plug-in is configured to use that project. For example, when the Java nature is added to a project, it indicates that the Java Development Tool (JDT) plug-ins are aware of that project, and have configured a classpath and a Java builder to work on that project.
So unless we don't have the java nature, it is not considered by the java discoverer.
An Eclipse no nature project is an Eclipse project in which the <nature> tag is not defined in the .project file.
It is mentioned in DMT->Help->Interface-an explanation of each page->Source code Package page->Package configuration tab->Which project should we take into account for the analysis?
CASE 2: Issue with the job changing from using a maven discoverer instead of an eclipse discoverer due to changes in the code
The Solution is to:
- Package the version
- Under package configuration, Unselect the Maven discoverer
- Package again the version
- The Eclipse project should be selected now.
- Deliver, Accept and Set as Current version.
- The web.xml file will be identified.
- In CAST-MS, after having set the new version as current version, missing class paths need to be added manually.
The issue here is that the maven and eclipse discoverer behave differently during the discovery process and depending on the information in the files provided may not provide the same information for the same job if the source files associated with one type are incomplete. Switching back to will resolve the issue.
Impact of issue: Web.xml files are ignored
Impact after applying solution: Web.xml files are selected.
