Subject: JXTA JSE 2.5 "Pavlova" Beta 1 Release
The next release of JXTA Java SE, 2.5 "Pavlova", is scheduled for March
12th, 2007. This release will contain important and significant
enhancements to JXTA Java SE along with the usual mix of refinements and
bug fixes.
A beta test version of JXTA JSE 2.5 is now available. This beta test is
the result of significant development and testing. Because this release
contains major changes in the internal implementation we are planning
two beta releases before the final release of JXTA JSE 2.5.
This is the first release and is being offered for compatibility and
regression testing. If you have not been following the CVS daily builds
of JXTA JSE then now would be a very good time to test the upcoming
release with your applications. The second beta release will be released
in a couple of weeks and will focused on performance and documentation
issues.
This is a Beta release. It is possible (and perhaps likely) that bugs
and incompatibilities still remain. It's critical that we find and fix
those bugs before the official final release. Your input is essential in
this task!
Acknowledgments
=======================================================================
Special thanks to all of the community members who have already
contributed ideas, reported problems, provided patches, and have helped
greatly to improve the quality, and robustness of this release.
Also, thanks in advance to all of the community members who spend time
trying this beta release, file issues and contribute to the final
release. We won't be able to do it without you!
How to Get Involved
=======================================================================
1. Download or Build JXTA JSE 2.5 Beta 1 using the instructions below in
"Downloading and Installing".
2. Rebuild your applications with JXTA Java SE 2.5 Beta 1 and test them
to ensure that they still function as expected.
3. Communicate! Share your feedback, observations, comments, criticisms
and perspectives at <mailto:[EMAIL PROTECTED]>. Contribute to the JXTA wiki
at <http://wiki.java.net/bin/view/Jxta/> If you are blogging about JXTA
we encourage you to add your name to the JXTA blogroll on the JXTA FAQ
Page <http://wiki.java.net/bin/view/Jxta/JxtaFAQ>.
4. File bugs, propose patches using the JXTA JSE Issue Tracker
<http://platform.jxta.org/servlets/ProjectIssues>.
5. Follow the progress of issues and test fixes using the nightly
automated builds : <http://download.jxta.org/build/nightly>
Downloading and Installing
======================================================================
Prebuilt JXTA Java SE 2.5 Beta1 builds can be installed from :
<http://download.jxta.org/build/release/jse/2.5_beta1/>
You can also build from cvs, refer to the following URL on how to build
from CVS in general.
<http://wiki.java.net/bin/view/Jxta/BuildingJXTA>
Remember to set cvs.version property to "JXTA_JSE_2_5_BETA1" for this
beta release, the command should be like this:
ant -f bootstrap.xml -Dcvs.version="JXTA_JSE_2_5_BETA1"
JXTA JSE 2.5 Dependencies
======================================================================
- Java Standard Edition 5.0 Compatible VM (http://java.sun.com)
- BouncyCastle 1.34 (http://www.bouncyCastle.org)
[Will be updated to 1.35 for security fixes before final release]
- Servlet 2.3 (http://java.sun.com)
- Jetty 4.2.25 (http://jetty.mortbay.com)
- Log4J is no longer required by JXTA JSE. Application developers using
Log4J in their applications will need to include it in their classpath.
For the optional jxtaext.jar the following are also required for the
configuration UI it includes :
- JDOM 1.0beta10 (http://www.jdom.org/)
- SwiXML 1.1 (#139) (http://www.swixml.org/)
Release Highlights
======================================================================
- NIO based TCP transport implementation. (#1583)
- Rewritten relay and rendezvous seeding implementation that connects
faster and more reliably (#1591)
- Log4J has been replaced with java.util.logging (#1537)
- Much greater use of Java 5.0 generics in the core APIs while
maintaining backwards compatibility.
- Inclusion of a new NetworkManager class to manage invoking,
configuring and shutting down JXTA. (#1539)
- Improvements to JXTA Socket reliability and performance. (#1463)
Known incompatibilities between JXTA 2.5 and prior JXTA 2.x releases
======================================================================
- A small number of classes and methods which have been deprecated for a
long time were removed as part of this release. Details and discussion
regarding the API changes in this release can be found at :
<http://platform.jxta.org/issues/show_bug.cgi?id=1616>. The final
release notes for JXTA JSE 2.5 will include a full itemization of all
removed items with the current alternatives.
- A several internal interfaces (net.jxta.impl.*) have changed.
Applications which depended upon these internal classes may break as a
result of these changes.
- For the authors of Peer Group services, there have been important
changes in how services are started. Services which depended upon being
able to get references to other services in their init() method will now
fail. See <http://platform.jxta.org/issues/show_bug.cgi?id=1600> for
more information.
Other Important Changes
======================================================================
- JXTA JSE has converted from using Log4J to java.util.logging for it's
logging functionality. If you were previously using a custom
log4j.properties file to control logging or setting logging options
using one of the JXTA configuration APIs you will need to adapt to the
new logging infrastructure.
Overall JXTA logging support is now regulated via a global system
property rather than a value in the PlatformConfig file. You can set the
default JXTA logging level when you invoke Java :
java -Dnet.jxta.level=CONFIG -jar myApp.jar
For finer grained control similar to what was available with the
log4j.properties file you can use a logging.properties file in addition
to the system property :
java -Dnet.jxta.logging.Logging=CONFIG \
-Djava.util.logging.config.file=logging.properties \
-jar myApp.jar
Note that depending on how your Java installation configures logging by
default it may be necessary to provide your own logging config file in
all cases due to default message filtering settings in the default
configuration. You can normally find the default logging configuration
file in the "lib" directory of your Java runtime. The default file is
also a good initial template for building your own customized logging
configuration file.
Updated Programmers Guide
======================================================================
In conjunction with the JXTA JSE 2.5 release Mohamed Abdelaziz is
leading the effort to prepare a new edition of the JXTA Programmers Guide.
This new version of the Guide will include updated examples to match the
2.5 release, several new chapters and many other updates to the existing
material. You can track the progress of the new edition on the Guide
project <http://guide.jxta.org> mailing lists and CVS. Draft versions of
the new edition are available in ODF format at :
<http://guide.jxta.org/source/browse/guide/src/guide_v2.4/>. The Guide
chapter authors and editors are eager to receive feedback and comments
on the new edition.
Known issues in JXTA Java SE 2.5
======================================================================
For a complete list of known issues with the JXTA JSE 2.5 release :
<http://platform.jxta.org/issues/buglist.cgi?issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=2.5+Pavlova>
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
