James Carman wrote:
Tapestry and HiveMind don't always use exceptions to print the line-precise error messages. Sometimes, it's just an error/warning message sent to a Log (JCL) (you forgot to include an implementation for a service point in HiveMind). Does your Cocoon code support that also or is it more exception-oriented? I would assume that since the classes on the stack are able to determine their location information that they could just print it out as a logging message.
Exactly! Actually, the location package provides nothing special regarding logging, but doesn't prevent it :-)
Locatable objects provide their location to exceptions they throw to allow for located stacktrace, and they of course can append their location to messages they log. The LocationUtils.toString() method provides a uniform string representation, whatever the actual implementation of Location is.
Sylvain -- Sylvain Wallez Anyware Technologies http://people.apache.org/~sylvain http://www.anyware-tech.com Apache Software Foundation Member Research & Technology Director --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
