On 20 jun 2006, at 00.37, Gunna Satria wrote:
Sorry, not looking that section correctly.. So, e.getMessage() is resulting null? Is it only do so if we do something like this,try{ throw new Exception(): } catch(Exception e){ System.out.println("message: "+e.getMessage); }
No. As you can see from the stack trace, the problem is not in my coding layer but inside invoke(). Still, I call invoke with no null parameters and in general, this works fine. I bet my @ss that Tapestry or my application server (jetty) somehow looses track of the visit class and invoke cannot find the method anymore due to lazy loading or uncaching that method. I am not sure what it is but I currently see no way how I could fix or work around this problem. Remember, it works fine for any time I run and test this up to the point where I leave the test server running for 1 or 2 days and then the first call to a page that contains this component will fail. Andreas Pardeike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
