* WILL USE THIS THREAD TO POST SOME OBSERVATIONS ABOUT THE OPENEJB.LOG FILE *
Trying to work out some examples for the JNDI names documentation. Here are some of my observations regarding openejb.log 1. Error messages: Error messages are written to the log file. So if I try to deploy an EJB and there were deployment errors, the deploy command shows the stack trace on the console, also the error is written to the logs. However, if I place an ejb jar in the apps directory and then start the server, the server starts successfully, however there is no indication on the console that there was a deployment error. So if I don't check the logs after starting the server, I would come to know of the error after I write the client and lookup the EJB, and the lookup fails. Any suggestions on how this could be improved. Do you think the user could be notified of the error on server startup itself? -- Karan Singh Malhi
