I have a few custom finders (those implemented in the bean) that end up in a single bean instance found rather than a Collection. This works fine except that when I throw a FinderException because no row is found the exception ends up in the log as an ERROR even though it is being caught by the session bean that called the finder. Caught exceptions for other types of finders do not end up in the log (ex. findByPrimaryKey). Is there something I can do different so that the caught exception is not logged on a custom finder?
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
