Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.0, 2.0.x, 2.1
-
Security Level: public (Regular issues)
-
None
-
Two Linux boxes on the same subnet with remoteDeployAddress reconfigured from localhost to the external interface
-
Regression
Description
Remote deploy of an EAR that doesn't have a application.xml fails, because the EARConfigBuilder.getEarPlan() is looking for the module/earFile to end with ".ear" to determine if it is an EAR w/o an app plan, but when using the remoteDeployer, the files are created as temp files without an extension, like remote-deploy31452 -
private ApplicationInfo getEarPlan(File planFile, JarFile earFile, ModuleIDBuilder idBuilder) throws DeploymentException {
String specDD;
ApplicationType application = null;
if (earFile != null) {
try
catch (XmlException e)
{ throw new DeploymentException("Could not parse application.xml", e); } catch (Exception e) {
//ee5 spec allows optional application.xml, continue with application == null
if (!earFile.getName().endsWith(".ear"))
//TODO return application.xml that we can make metadata complete?
}
}