How to Overcome Negatives with JXTA
A key difference between JXTA and other P2P systems is JXTA's ability to add new functionality and to do so in a predictable way with either its protocols or its various APIs. JXTA is also segmented to allow protocols to be used as stand-alone services similar to a router, a DNS, a firewall, or other appliance.
JXTA is also a multipurpose system as compared to most other P2P frameworks. For example, Freenet is meant to be a way to distribute and access documents without fear of censorship or monitoring of content. To use the Freenet platform for collaboration where all the parties know each other defeats the original purpose and would be less efficient than a direct approach.
The key difficulty is choosing a solution. There are many open projects at JXTA.org, but some may be incomplete or may not meet your needs. Already a few companies are creating their own solutions to sell to JXTA developers. Of course, you can also create your own solutions. The choice comes down to cost, suitability, and schedule. Making the right choice is why software architects like me get paid the big bucks.