It is normal for the stacktrace to be empty since we enforce that for
performance improvements. What isn't normal though is that this
exception bubbled up. Is this something that recently started to
happen? Can you try with earlier snapshots? Are you getting this
while running inside a servlet container?
On 30 Jun 2006, at 12:20, Andrés González wrote:
Hi.
I'm using rife-1.5M3-snapshot-jdk15-20060627.jar and i'm getting the
following exception:
com.uwyn.rife.engine.exceptions.ExitTriggeredException
The strange thing is, in the logs (I use log4j) i only get:
ERROR 2006-06-30 12:18:04,217 [http-192.168.0.150-443-Processor25]
(Usuarios.java:126) - Error. Acción = u:alta
com.uwyn.rife.engine.exceptions.ExitTriggeredException
without stacktrace nor nested exception(s).
I did an "e.printStackTrace()" in the code just for check and obtained
the same result (in the catalina.out of tomcat):
com.uwyn.rife.engine.exceptions.ExitTriggeredException
Is this normal?
--
-=-=-=-=-=-=-=-=-=-=-=-=-
Andrés González.
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
