date:20121005

Re: River exception usage.

2012-10-05 Thread Gregg Wonderly

Deriving from IOException would seem like a viable choice? Gregg Sent from my Phone On Oct 5, 2012, at 7:17 AM, Simon IJskes - QCG wrote: > On 05-10-12 13:29, James Grahn wrote: > >> I think the analogy holds with the JAXB example, which unified its >> thrown exceptions to offer "something wr

Re: WELCOME to dev@river.apache.org

2012-10-05 Thread Peter Firmstone

Hi Bishnu, Sorry for the slow reply, River is maintained by volunteers, we don't have as much time as we'd like. Your service browser is interesting. There are significant challenges with security, River (Jini) has constraints, which allow clients and services to require integrity, confiden

Re: River exception usage.

2012-10-05 Thread Simon IJskes - QCG

On 05-10-12 13:29, James Grahn wrote: I think the analogy holds with the JAXB example, which unified its thrown exceptions to offer "something wrong relating to the XML". RiverException would similarly be "something wrong with the network" except during initial development when you'd care more a

Re: River exception usage.

2012-10-05 Thread James Grahn

I generated this Jira issue because of my practical experiences working on a project that conducted most/all of its networking over Javaspaces. Because the majority of our interactions over network were conducted through Javaspaces/Jini, invariably all exceptions wound up meaning the same thing.