Hello JXTA Community,
When the next jxta-java version released?
Has been more than a year did not release a new version, and there is no news.
Will JXTA die?
It is not dead according to my knowledge.
Java Training in Chennai
Yep, sinun tulisi olla optimistinen. Älä ajattele, että se on jo kuollut! Se on shokki!
I'm trying to reanimate JXTA for OSGI. Help is welcome!
2.6 beta 2 has been released. If you are optimistic it is alive, if you are not, call it living dead... but it is still moving...
There are some people, who still believe in the potential of JXTA.
It is important to question.
Especially in these difficult times for Sun, and deficiencies in the dev. java.net
It will not be easier to start over?
And re-implement the protocols from the scratch in, Apache web site :-)
Why JXTA Failed ?
i have heard lots of performace issues regarding jxta under benchmarking and that there isnt a standard benchmark developed. i have also heard lots of great things regarding its protocol suite. im sorta confused as to the practical functionailty of the jtax protocol suite under a heavy load in a wan enviroment. can anyone direct me to stable ground.
If JXTA is not dead can anyone point me to a non-trivial/non-academic system that actually uses JXTA? And don't point me to the Boeing JXTA/C project because that thing is a mess!
At Sun :
Ok...Hmmm...the Java Store link is just a pointer to a place to the Java Warehouse and the Shoals link is a framework. The Shoals link does contain information on companies that use Shoals (which appears to use JXTA...although I haven't read the full docs on it) but it doesn't really say how they are being used.
What I really want to see is a mature deployed commercial/government system that uses JXTA as the primary means for service discovery. The Shoals link may have it there and I just haven't found it.
Shoal is a clustering and messaging framework which utilizes JXTA for cluster formation (discovery), monitoring, failover, and across cluster addressing and messaging.
Shoal is the cluster foundation for GlassFish and SailFin. Both products are widely used commercially and by governments.
The JavaStore utilizes GlassFish and specifically Shoal for elastic scaling load balancing of the back-end infrastructure. It uses the ClusterView to create a load balance map and a failover strategy, and the cross cluster messaging to trigger cache refreshes.
"Both products are widely used commercially and by governments."
How so and where?
I have used it for a telecom giant, Boeing, and several startups. I am currently using it for a board game that is ever closer to release. Yes, there are issues, but it is indeed the only thing I have found that lets me do what I need. I am certainly one of the more vocal critics, but it is very viable despite the flaws.
oneDrum are using for distributed collaboration and currently investing in performance and scalability improvements of the JXSE implementation. We aim to take the implementation to a level limited by the physical resources of the machine running on i.e. Number of sockets available on the machine.
We are in private beta with the software at present.
collanos also uses.
what are you planning to use JXTA for and you can help decide if there is experience in this are in the community and give you confidence to use.
Thanks for your reply. I am using jxta to develop the software about im and resource shared. Jxta far behind the development of bittorrent.
I hope to be able to see the roadmap of the jxta, or else i can not understand the development state of the jxta.
I am a supporter of jxta, but I am very disappointed about the development of jxta .
Following the investigation...to find an acceptable answer.
The issue is not new.
Thread: Is jxta going to be a dead cat :
It seems, there are people who work on projects that use JXTA, but do not want to disclose. Distributed algorithms are expensive. Be carefull with plagiarism :-)
Sixearch: Social Web search via adaptive peers :
In jxta, there are different aspects and we are not obliged to use them all.
-Communication(Pipes, BidiPipes, JxtaSockets...use java Sockets)
-Groups (membership...use it is good)
-Discovery ( you can use centralised discovery, for efficiency)
-Through firewalls (work in local area network)
-SÃ©curity (thanks to bouncycastle.org )
Jxta is not dead. The proof, i use it !
I started JXTA on 25 February 2001.
So I try to understand, why the last 8 years there is no killer application JXTA.
I use evry day, for my work, this tool : http://www.collanos.com/
Actually, I already know this new book.
Which the exemples, is a very good thing for the JXTA community.
Another book :
Joy keynotes the O'Reilly Peer-to-Peer Conference Thursday, February 15, "From UNIX to Java to XML to Peer-to-Peer."
O'Reilly openp2p.com escorting a JXTA project, but then changed course towards the WEB2.0. The solution for the JXTA project is perhaps closer to the WEB2.0 see why not WEB3.0 . Perhaps that Oreilly would be more interested.
From the beginning, not everyone is excited:
They will talk about JXTA in this Expo (Web 2.0 ExpoWeb 2.0 Expo) ?
Web 2.0 ExpoWeb 2.0 Expo
March 31-April 3, 2009
San Francisco, CA
Spring of 2002 :
JXTA Protocols were submitted as a draft-rfc to bootstrap the process leading to an IETF P2P Working Group. But IRTF P2P RG begin 2003.
But IETF formalized in 2002-2004 Jabber (XMPP), why ?
JXTA and Grid computing appears to compromise.
The JXTA way to Grid: a dead end?
Performance scalability of the JXTA P2P framework :
From work of project : http://juxmem.gforge.inria.fr/
InfraSearch (a.k.a. gonesilent.com) was acquired by Sun Microsystems in February to become part of Sun's JXTA (Juxtapose) project :
Can we use JXTA for distributed search ?
Some conclusions, after 8 years of JXTA :
We need something like jxta.
And if the solution was in Social network :
To make progress, look at what are the other projects.
Tapestry,Chimera , FreePastry , Pastry , Chord, CAN , Jabber , XtremWeb , confiit , Freenet , Gnutella Groove Network , PtPTL , Windows P2P , JGroups
Xpeer , GNUnet , Bamboo , OpenDHT , P2PS , JAIN SIP ...
Best regards !
JXTA does not die as long as there are people to use it.
There is 8 years of JXTA !!!
JXTA is a HOPE and is normal to have some deceptions.
I beleive in the ideas and the work of JXTA community.
BUT, for a developer who hopes to use JXTA in applications.And who closely follows what happens in the project jxta.
he asked himself legitimate questions :
If JXTA is not dead :
1-Why the 6 books about JXTA, is finish in 2002. A principal exemple is one reference JXTA in a Nutshell O'Reilly?
2-Why there is a lot of vapor projects that are ended, or aborted?
3-Why the change from the site jxta.org to dev.java.net ?
4-Why Sun dont use himself JXTA in Sun's Java Enterprise System, a bundle of server software formerly called Sun ONE or its N1 system for managing data centers ?
See : Sun Microsystems Inc. says its Jxta technology for peer-to-peer computing is gathering steam and may SOON make its way into some of its own products.
5-Why GlassFish V3 Prelude dont use JXTA Shoal yet ?
5-Why there is a lot of links in the site of project that does not found (for exemple Planet JXTA) ?
6- Do Bill Joy use JXTA in his projects ?
7- Why there is no more publications about JXTA ?
8- Why project JXME proxyless is not very clear (the version is JXME 2.1.3 (Giza) or 2.5)?
23- January 2008 : JXME 2.5 Edge protocols binding for CLDC/MIDP 2.0 open sourced ?
Some responses :
1- The algorithmes Or the Reference Implementation are not efficient and too difficult.
2- The project JXTA dont benefit of the bad reputetion of P2P (no economique model,security,violate the Copyright Law).
3- Sun do not put means in the project JXTA, like IBM with Eclipse.
4- There is a problem with organisation, and no resources to work in projects (but at the beginning of the project there was resources).
5- JXTA need more documention updated.
6- JXTA need to be more easy to use by the developers.
7- The distributed systems is very very very complicated.And there is not a lot of talents to resolve the problems.
Some people say good things about JXTA-C, effect of Boeing project ?
We need JXTA, for the distributed systems. So we hope that JXTA goes continue to progress.
I have published a recent book about JXTA last year: see www.practicaljxta.com.
The next JXSE release is being planned/coordinated by Fabrice DiMeglio. A firm date for the next release hasn't been chosen yet I don't believe.
There is still active work such as the ContentService being developed as well as optimizations and bug fixes of the existing functionality. Neither JXTA nor JXSE is dead or dying. The focus and approach of the project has changed significantly as the software stack has matured. Most users are content with the current 2.5 release and cherry pick only the bug fixes that impact their use.
Producing a formal release is a lot of work and unfortunately no community members have been able devote the time. Fabrice has bravely volunteered to help coordinate the next release but he can certainly use the assistance of any other community members who would like to participate.
Can you tell Fabrice I can help with the next release?
(Charles L. Perkins, Virtual Rendezvous)
It is not dead as far as I know, I talked to Bernard T. recently about the JXTA/C Boeing project and it is ongoing, and fold back its changes into the Java JXTA project.
Look around for more on the C version of JXTA if you want the latest changes and are willing to switch to C.
The question is, what changes? Nobody is really talking about what is going on and what the plans are. It would be nice, because we could use this to help the Java version.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.