The DebugPhaseListener just prints out debug information in the log file -- for example timing information about the phases in the JSF life cycle and messages found in the Faces Context.
The TobagoMultipartFormdataFilter is used to handle file upload and is more or less transparent in other occasions. These two actions you described shouldn't have an effect on the problem you described. Which navigation handler did you remove? Was it a Tobago DebugNavigationHandler? That one shouldn't have an effect either, because it's just logging debug information, too. Strange indeed. Best regards Arvid -----Original Message----- From: Groovie [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2008 10:20 PM To: [email protected] Subject: RE: [TOBAGO] CLOSED serious problems with managed-bean's Salut Arvid, i fixed that strange behaviour by saving the ole state in my CVS und uploading a simple(1) Tobago test over it. Lucky guy i was, seeing the test application running. Then i reintregrated my application into the test app and finally removed the test app components. Doing this step by step with a functional test of the demo-app and mine. Ok, this took 25Hours in one go 1 litre tee and 2 litres of best brewed bavarian beer. There are two files, that could cause the impact: 1) faces-config.xml 1.1)removed the navigation-handler from application tag 1.2)added <lifecycle> <phase-listener> org.apache.myfaces.tobago.util.DebugPhaseListener </phase-listener> </lifecycle> 2) in web.xml 2.1 removd <filter-mapping> <filter-name>multipartFormdataFilter</filter-name> <url-pattern>/faces/*</url-pattern> </filter-mapping> strange strange but its done. -- View this message in context: http://www.nabble.com/-TOBAGO--serious-problems-with-managed-bean%27s-tp19710817p19730967.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
