One of the primary things in software design is to place services into a
service layer. There should be service failure exceptions and those should be
distinctly different from “transport” or “implementation” exceptions. If your
code has “RemoteException” visible in the business logic, then yo
Just a comment on the complexity of Jini services. I agree that starting up
Jini services using the ServiceStarter is overly complex and arcane, which is
why other service frameworks like Rio, StartNow, and river-service-container
exist.
I’m hoping the river-examples project makes things a li
+1 Peter.
I also reccommend investigating and identifying bottlenecks first; this
will benefit other users as well.
Also, if there is any chance the bottleneck is in River, I would be
very, very interested in constructing a benchmark based on your workload
that demonstrates the scaling probl
On 12/06/2015 05:34, Palash Ray wrote:
> In my 2 years of using Jini, one feedback that I have as a developer is its
> overtly complex. For instance, if I want to configure security, its so
> complex, that I have to spend days together to get it up.
>
> I strongly believe that we should try to make
Hi Dennis,
The full story is documented in net.jini.loader.ClassLoading, I've
appended the javadoc below.
The quick summary is that Greg and Sim's works were integrated and
functionality of both was retained, but their class names weren't in
order to retain compatibility with existing implem
