At the very least, change it to throw MissingResourceException or something, not just Exception :-(
L.
Quinton McCombs wrote:
I am about to start working going through the entire intake service and making some changes. When I first got started with intake, it was a little confusing at first (2.1). Seeing the posts on the user's list, this is an area where many people seem to have some trouble. My main goal is to make it a little easier to get working for people new to Turbine.Here is a brief list of things that I am planning to address. - Better error reporting to the log file. It can be very difficult to troubleshoot a simple mistake in intake.xml. - Fix the problem of not being able to set a mapped property to null. - Update the documentation to fully describe the types of fields, attributes, available rules, etc. - Backport any bug fixes in the fulcrum version back to the coupled version. - Update the javadocs - Better error handling - Develop some JUnit tests Is there anything else that anyone would like to suggest? Have we decided on what to do about logging? I suppose that I could just keep it using the current logging mechanism if that debate is not over yet. -- To unsubscribe, e-mail: For additional commands, e-mail:
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
