perfsonar development work

[Roman Lapacz <>]

Michael Bischoff wrote:
> Szymon Trocha wrote:
> > Maciej Glowiak wrote:
> Hello all,
>
> let me first introduce: I'm Michael Bischoff I work at surfnet for 
> perfsonar on the java flow selection and aggregation MA.

Hi Michael
> while familiarizing myself with the codebase I noticed how perfsonar 
> uses only checked exceptions. When these are thrown they are passed 
> along/bubble up to the message handler which deals with them by 
> returning an appropriate message to the client. In between code 
> doesn't handle these exceptions which makes sense. However since the 
> code in between doesn't handle them why not make PerfSONARException a 
> unchecked/runtime exception? this would allow the removal of all those 
> throws 'decorations'. Given that the ServiceEngine's javadoc would 
> reflect this there shouldn't be any trouble with it. In the cases 
> (which I haven't encountered), where a checked PerfSONARException 
> would make sence, I doubt if PerfSONARException is the exception to 
> throw.

Very good idea. I think using runtime exception fits in our code perfectly.

Thanks

Roman