I just did some more testing (I always seem to gain insight after I
post...) and I discovered that it is the SECOND occurrence of a
present/notPresent on a page that dies. If I have a present that fails, and
then have another present/notPresent, on the same bean or a different bean,
it will die whether or not the bean is present of not. I can verify this by
moving the dying present/notPresent before the successful one, and then the
failing one works and the successful one dies. It would appear from the
error message and my cursory investigation of the Struts source that when
an attempt is made to find a bean, an exception is being caught and stored
in the org.apache.struts.action.EXCEPTION, and subsequent attempts to
replace that value with another caught exception are what is hosing it
down.
So, has anyone else seen/verified this situation and what can/should I
do about it?
Joey
-- Sun Certified Java2 Programmer
-- Political Rants: www.joeygibson.com
-- My Pocket Smalltalk Stuff: www.joeygibson.com/st
--
-- "We thought about killin' him, but we kinda
-- hated to go that far...."
