Hi Vincent, I should have sent another mail regarding this but I have been dealing with the deployment for the last several hours.
It turned out that another exception occurred during the construction of the tests and JBuilder TestRunner (in version 7) tried to construct the stack trace string. Somehow, the LogService gets involved and threw an exception because it was not initialized properly. I switched to JUnit Text UI test runner and that revealed the problem. The true problem behind is, however, is strange as well. Somehow the cactus.properties file is ALWAYS required to be in the class path, even when you specified the cactus.config property through the VM parameter. Is there a reason for this? For the record, I am using JBuilder 7, BES server, JUnit 3.7 and Cactus 1.3 for J2EE 1.3 Vincent Massol wrote: >Hi Shane, > >This is very strange and it should not happen. It simply means that >somehow the Cactus logging initialization step was skipped ... somehow >... > >Can you give us more information on : >- Cactus version >- JUnit version >- How do you start it ? From JBuilder ? (I'm just asking as I saw >Borland in your email ! :-)). With what Test Runner ? > >I was going to say : "the easiest would be for you to send the logs", >but obviously this won't work ... > >Have you tried running the Cactus sample which is packaged in the Cactus >distribution ? Is it working ok ? > >Thanks >-Vincent > > > -- Disclaimer: I join all the news groups out of my own interest. All opinions expressed here are my own and not necessarily those of my employer. Borland -- Enabling the digital world where our customers have the freedom of choice to develop, deploy, and integrate applications across the enterprise and the Internet. http://www.borland.com This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately and permanently delete the original and any copy of any e-mail and any printout thereof. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
