Anyway this code will be removed from nuxeo ear deployer since the
preprocessing step will be done
as part of the build process (this code is already integrated as a maven
plugin)
So we will no more have hot preprocessing in future since it is not
compatible with other JEE AS servers.
Bogdan
Alain Escaffre wrote:
This method is called on the lowest layer of Nuxeo platform : if this
one is not deployed correctly, the application mustn't start. So it
makes sens to stop the process on error. We could argue that it is a
problem for other running app, but usually in production, you isolate
the applications in different jvm, so that they don't bother with each
other.
Best regard,
Alain
Le 17 juil. 07 à 09:21, Filipchik Alexander a écrit :
When we had investigated your code we found that your developers uses
System.exit(1) in several cases.
We found 11 usages of it. For example:
org.nuxeo.runtime.jboss.deployment.preprocessor.DeploymentPreprocessor
//line 412
try {
// initialize
processor.init();
// and predeploy
processor.predeploy();
} catch (Exception e) {
e.printStackTrace();
System.exit(1);
}
And also you use deleteOnExit() when creating temp files. It can
cause different faults.
System.exit – kills JBoss Server when executed
_______________________________________________
ECM mailing list
[email protected] <mailto:[email protected]>
http://lists.nuxeo.com/mailman/listinfo/ecm
------------------------------------------------------------------------
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
