On 07.07.2014, at 18:42, Carsten Ziegeler <cziege...@apache.org> wrote:
> This doesn't really convince me - the same argument would hold true for > every API where the exception (cause) is logged, but the method just gives > back true/false,object/null. Even for APIs throwing an exception it might > be hard to get a meaningful message to developer. So this isn't done for > other APIs, why should we do it differently for adaptTo? > In addition, if you have a lot of client code using the adapter pattern, > then you end up in converting the exception to a meaningful message in > various places. > > It would be so easy to let the adapter factory do a meaningful log > statement and there are tools/apis to pick up this log message and display > it to the dev without requiring the developer to go to the log Ack. Cheers, Alex