This turned out to be a very bad/confusing bug.
If any of our screens/actions/layouts etc were to throw a Throwable that
wasn't a subclass of Exception we would just get no content.
Configurations will do this if you have two strings with the same name:
---
java.lang.ExceptionInInitializerError: java.lang.ClassCastException:
login.message doesn't map to a String object
at
org.apache.java.util.Configurations.getString(Configurations.java:206)
at
org.apache.java.util.Configurations.getString(Configurations.java:181)
---
So now instead of a global
try {
} catch (Exception e)
...
It is now going to also have a:
try {
} catch (Throwable t) {
...
}
Right below that.
Also, I modified Log.java so that it takes a Throwable as an option.
The native method for printStackTrace is in this object.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
