The problem is that exceptions are thrown by XWork (like in your example), but they are not caught/logged by Struts, so they end up in the container's log, instead of log4j (or the logger being used). I added a try/catch to the init method of dispatcher to log exceptions and rethrow them.
thanks for reporting musachy On Thu, Apr 2, 2009 at 3:03 PM, Christian Stone <xt...@stonescape.net> wrote: > Here is an example... > <package name="mypackage" extends="struts-authentication"> > <default-interceptor-ref name="guest"/> > ... > > If "guest" is not defined, the context will not load. > > With this said, reporting is much better than it used to be. There are > still a number of issues that will cause the configuration to choke... > > If this isn't clear, let me know! > > -- Christian > > On Apr 2, 2009, at 2:20 PM, Musachy Barroso wrote: > >> Could you show an example of a "typo or misconfigured action" problem >> that does not get logged? Also note that setting the "class" attribute >> in the configuration will/won't throw en exception depending on the >> ObjectFactory being used. > > -- > _,--" > cws `-._ ________-_______ "---- > _----'--'--------------------------------'--'----_ > //_| | \ Christian Stone, Software Engineer / | |_\\ > (_____|_|__= xt...@stonescape.net =__|_|_____) > _\_____=__ http://xtian.stonescape.net/ ___/_ > \/-(o)-~~-(o)-~~-(o)-`------'-(o)-~~-(o)-~~-(o)-\/ > > > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
