To be more specific, I meant a util function in ExceptionUtils. Like this, ExceptionUtils.createCompositeException(String overallErrorMessage, Throwable... throwables)
This would return a CompositeException which would contain all the Throwables and whose getCause() and printStackTrace() methods have been overridden to given out a verbose cause and stacktrace which would be an aggregation of the throwables supplied. Pardon me if this is not the correct platform or right mechanism to propose such changes. Please let me know the correct way to proceed. Thanks, Adwait. On Fri, Jul 17, 2020 at 5:18 PM Adwait Kumar Singh < theadvaitkumarsi...@gmail.com> wrote: > Hi Commons devs, > > Use case : Ability to a single exceptions with multiple causes. This > required in validation or initialization scenarios for example when I want > to Validation/Initialization failures for multiple reasons and each reason > having a unique cause. > RxJava provides something similar > <https://github.com/ReactiveX/RxJava/blob/3.x/src/main/java/io/reactivex/rxjava3/exceptions/CompositeException.java> > . > > Wanted to know if this makes sense, would raise a PR if it does. > > Thanks, > Adwait. >
