Issue with the display-name of web.xml for WARs inside EARs

Description

I have observed the following strange thing. I have configured the cargo-maven2-plugin to start WebSphere, deploy an application (ear) into an WebSphere App server 8.5.5. and afterwards stop the WebSphere, but it failed with the following:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 [INFO] [talledLocalContainer] ADMA5016I: Installation of cargo-deployable-cargocpc started. [INFO] [talledLocalContainer] ADMA5058I: Application and module versions are validated with versions of deployment targets. [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5053I: The library references for the installed optional package are created. [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5001I: The application binaries are saved in C:\Java\profiles\was855profile1\AppSrv1\wstemp\Script14197b970a6\workspace\cells\ BPC60103Node02Cell\applications\cargo-deployable-cargocpc.ear\cargo-deployable-cargocpc.ear [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] SECJ0400I: Successfully updated the application cargo-deployable-cargocpc with the appContextIDForSecurity information. [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5005I: The application cargo-deployable-cargocpc is configured in the WebSphere Application Server repository. [INFO] [talledLocalContainer] ADMA5113I: Activation plan created successfully. [INFO] [talledLocalContainer] ADMA5011I: The cleanup of the temp directory for application cargo-deployable-cargocpc is complete. [INFO] [talledLocalContainer] ADMA5013I: Application cargo-deployable-cargocpc installed successfully. [INFO] [talledLocalContainer] WebSphere 8.5 started on port [9081] [INFO] [INFO] --- cargo-maven2-plugin:1.4.4:deploy (deploy-to-container) @ com-byteslounge-it --- [INFO] [talledLocalContainer] WASX7209I: Connected to process "server1" on nodeBPC60103Node02 using SOAP connector; The type of process is: UnManagedProcess [INFO] [talledLocalContainer] WASX7017E: Exception received while running file "C:\Users\be02606\AppData\Local\Temp\cargo-websphere-commandFile-7820894370339836928.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: "[com-byteslounge.war, com-byteslounge.war,WEB-INF/web.xml, default_host]" for task "MapWebModToVH". The supplied option must match with the existing task data in the application and the existing task data are: "[This com-byteslounge.war,WEB-INF/web.xml] " [INFO] [talledLocalContainer] [INFO] [stalledLocalDeployer] The deployment has failed: org.codehaus.cargo.util.CargoException: Deploy failed

I would like to emphasize the following line:

1 2 3 exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: "[com-byteslounge.war, com-byteslounge.war,WEB-INF/web.xml, default_host]" for task "MapWebModToVH". The supplied option must match with the existing task data in the application and the existing task data are: "[This com-byteslounge.war,WEB-INF/web.xml] "

After some investigation I found out that after changing the display-name in the web.xml of the war file into `<display-name/>` it works without any problems.
This sounds like a bug to me. Or do i misunderstand a thing?

Status

Assignee

Savas Ali Tokmen

Reporter

Karl Heinz Marbaise

Components

Fix versions

Affects versions

1.4.4

Priority

Critical