Skip to main content

Project Plan For NET4J [archived] [Net4j], version 2.0


This document lays out the feature and API set for the second release of the Net4j Signalling Platform Project (Net4j), version 2.0. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:
  • Net4j Signalling Platform SDK (includes Runtime, UI, DB, Examples, Documentation and Source).
  • Net4j Signalling Platform Runtime (contains the Net4j core and transport provider plugins, tcp, jvm and http).
  • Net4j Signalling Platform Examples (contains the general Net4j examples, the buddies collaboration and chat examples and the experimental JMS provider implementation plugins).
  • Net4j Signalling Platform Tests (contains the Net4j test plugins).

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 week; that is, until the final 3.5 release of the Platform, upon which Net4j and other projects will release simultaneously. Net4j will deliver its milestones within one week of the Eclipse Platform. It is anticipated that Net4j will synchronize its milestones with the Galileo milestone schedule.
API freeze
Feature Freeze
Net4j will produce maintenance releases to align with the Ganymede SR releases, that includes the Eclipse Platform 3.4.2 release. Net4j may produce interim maintenance releases in addition to these in order to satisfy clients requests. Maintenance releases will only be published if they have any new fixes to offer.
  • Friday, October 3, 2008 - Net4j 1.0.1 maintenance release (if necessary)
  • Friday, February 27, 2009 - Net4j 1.0.2 maintenance release (Ganymede Service Release 2) (if necessary)
  • A list of issues indicated for the 1.0.x maintenance stream can be found in bugzilla, or by using links on maintenance stream build pages.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Net4j Signalling Platform Project (Net4j) depends upon on the Platform and other projects, which are mostly "pure" JavaTM. Net4j will target the same Java version as the CDO Model Repository, which currently requires Java 5. Eclipse Platform SDK 3.5 will be tested and validated on a number of reference platforms. Net4j will be tested and validated against a subset of those listed for the platform.


The Net4j Signalling Platform is a runtime technology with most of the components having no user interface. The remaining user interface parts of Net4j are considered exemplary and thus no attention has been paid to externalize them for internationalization.

Table of Contents

Compatibility with Previous Releases

The 2.0 release of the Net4j Signalling Platform will contain a large set of new functionality and an enhanced API as driven by the community. Therefore Net4j will not be binary compatible with previous releases. Careful attention has been paid to minimize the API related changes and the resulting impact to existing applications based upon Net4j.

Table of Contents

Themes and Priorities

A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

Power to the People

Major improvements in the API and configuration will give clients considerably more control over the behaviour and performance of their repositories and sessions.

Appealing to a Broader Community

The Net4j project has a proven record of robustness and flexibility. However, in the past best results could only be achieved with EMF models specifically genererated for the usage with Net4j. The upcoming 2.0 release will be less invasive to the client models and applications by being better aligned with EMF and other standards.

Lighter, Faster and Better

The Net4j project has a proven track record of quality, reliability, and extensibility but all these aspects can be continuously improved. Existing and new clients often desire more functionality from the framework while long established clients generally desire mostly improvements in performance. Often these two are at odds since additional extensibility often has a performance cost and any changes, even performance boosting ones, potentially impact reliability. Every effort will be made to introduce new capabilities so that they have negligible impact on established clients based on the guiding principle: if you don't use it, you don't pay for it. Because service and support has and always will take priority over new development work, development commitments and schedules are subject to arbitrary change, slippage, or even deferral. Be sure to establish direct communication to ensure that any hard commitments are seen as that by the development team itself!

Table of Contents

Appendix A: Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.

Table of Contents

Back to the top