"Kruno" wrote : When runtime exception originates from method inside SFSB, which is called by pageflow it is not possible to see origin of exception just that pageflow can't call that method. So to actually debug one needs to bypass pageflow to see the real exception. | Is there any way to configure seam so that pageflow would not hide origin of stacktrace. | | Thanks in advance Kruno.
I have the same problem when simulating a Hibernate syntax error in a SFSB method marked with @End. And what is worse, "ERROR [SeamPhaseListener] uncaught exception java.lang.IllegalStateException: pageflow has not yet started" exception is rethrown in an endless loop :-( Seam 2.0.0.GA JBoss 4.2.2 GA JDK 1.5.0.14 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122145#4122145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122145 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
