Jump to: navigation, search

Difference between revisions of "EMF/Net4j 1.0/New and Noteworthy"

< EMF
(New page: EMF 2.4 (available as part of [http://www.eclipse.org/ganymede/ Ganymede] and also separately on the [http://www.eclipse.org/modeling/emf/ EMF] site, contains a number of important and lon...)
 
Line 1: Line 1:
EMF 2.4 (available as part of [http://www.eclipse.org/ganymede/ Ganymede] and also separately on the [http://www.eclipse.org/modeling/emf/ EMF] site, contains a number of important and long-awaited features, changes, and enhancements.  
+
Net4j 1.0 (available as part of [http://www.eclipse.org/ganymede/ Ganymede] and also separately on the [http://www.eclipse.org/modeling/emf/ EMF] site, contains a number of important and long-awaited features, changes, and enhancements.  
  
  
== Overview ==
+
==Core Features==
 +
* Extensible signalling framework for '''application protocols''' (IProtocol, SignalProtocol)
 +
* Extensible transport framework for '''physical transports''' (IConnector, IAcceptor)
 +
* '''Multiplexing''' of different application protocols (IChannel)
 +
* Fast, asynchronous and non-blocking '''buffering kernel''' (IBuffer)
 +
<br>
  
* Support for Content Types
+
==Transports==
:* Applications using EMF can now register its resources using content types
+
* NIO-based '''TCP''' transport implementation (ITCPConnector, ITCPAcceptor)
:* Content types in EMF can be used both in stand-alone and Eclipse based applications.  For the latter, it integrates seamless with Eclipse’s content type support
+
* In-process '''JVM''' transport implementation (IJVMConnector, IJVMAcceptor)
 +
* Polling '''HTTP''' transport implementation (IHTTPConnector, IHTTPAcceptor)
 +
<br>
  
* A new role for URIConverters
+
==Examples==
:* In addition to the creation of input and output streams for URIs, URIConverters now support several operations, including deletion, and timestamp and existence queries
+
* Extensible collaborations platform with buddy list, chat, fileshare, ...
:* Easier integration with REST applications
+
* JMS(TM) provider implementation (experimental but functional)
:* Easier customization via URIHandlers
+
<br>
  
* Support for Data Binding
+
==Utilities==
:* EMF now provides the hooks to easily integrate instances of Ecore models and Eclipse’s data binding API
+
* Caching and monitoring framework
:* Terrific example of the community stepping up to provide an important feature
+
* Special collections
 +
* Concurrency support
 +
* Wiring framework (managed containers)
 +
* Event framework
 +
* Factory framework
 +
* Generic finite state machine (FSM)
 +
* I/O tools
 +
* Lifecycle framework
 +
* Operations and maintenance framework (OM)
 +
** Platform abstraction (OSGi, Eclipse runtime, stand alone)
 +
** Bundle abstraction
 +
** Logging abstraction
 +
** Tracing abstraction
 +
** Preferences abstraction
 +
** Progress monitoring framework
 +
* Memory sensitivity framework
 +
* Transactional and notifying registries
 +
* Extensible security framework
 +
* Generic transactional operations framework
 +
* Debugging Tools
 +
** Remote tracing (OM extension + Eclipse UI)
 +
** Container view (Eclipse UI)
 +
** Introspector view (Eclipse UI)
 +
* Extensible DB abstraction framework
 +
** Derby DB adapter implementation
 +
** HSQLDB adapter implementation
 +
** MySQL adapter implementation
 +
<br>
  
* Installable Examples
+
==More information==
:* The EMF examples can now be installed to the workspace via wizards located under Eclipse’s “Example” category
+
  
* Several performance and usability improvements, including
+
The Net4j project uses dynamically-generated [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=net4j&version=HEAD release notes], using Bugzilla and CVS data to create accurate lists of bugs closed in each build. This also allows developers and users to see what [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.net4j+days%3A+7 files were changed] for each bug, by who, and when. For details on how this is done, see [[Search CVS#Parameter_List | Search CVS]].
:* Support for defining the fonts and colors on Item Providers
+
:* Binary serialization and deserialization
+
  
== More information ==
+
* [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=net4j&version=HEAD Release Notes]
 
+
* [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.net4j+days%3A+7 Search CVS], [[Search CVS#Parameter_List | Parameter List]]
The EMF project uses dynamically-generated [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=emf&version=HEAD release notes], using Bugzilla and CVS data to create accurate lists of bugs closed in each build. This also allows developers and users to see what [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7 files were changed] for each bug, by who, and when. For details on how this is done, see [[Search CVS#Parameter_List | Search CVS]]. You can also read about [http://www.eclipse.org/modeling/emf/docs/#whatsnew bleeding edge] changes between builds, or see the [[:Category:EMF | EMF Wiki Category]] for EMF 2.4-specific documents.
+
 
+
* [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=emf&version=HEAD Release Notes]
+
* [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7 Search CVS], [[Search CVS#Parameter_List | Parameter List]]
+
* [http://www.eclipse.org/modeling/emf/docs/#whatsnew The Bleeding Edge]
+
 
* [[:Category:EMF | EMF Wiki Category]]
 
* [[:Category:EMF | EMF Wiki Category]]
  
Line 36: Line 62:
 
----
 
----
  
 
''Note: this page is a [[Ganymede#Should_Do | Should Do]] requirement for participation in Ganymede.''
 
  
 
[[Category:Modeling]] [[Category:EMF]]
 
[[Category:Modeling]] [[Category:EMF]]

Revision as of 06:13, 29 May 2008

Net4j 1.0 (available as part of Ganymede and also separately on the EMF site, contains a number of important and long-awaited features, changes, and enhancements.


Core Features

  • Extensible signalling framework for application protocols (IProtocol, SignalProtocol)
  • Extensible transport framework for physical transports (IConnector, IAcceptor)
  • Multiplexing of different application protocols (IChannel)
  • Fast, asynchronous and non-blocking buffering kernel (IBuffer)


Transports

  • NIO-based TCP transport implementation (ITCPConnector, ITCPAcceptor)
  • In-process JVM transport implementation (IJVMConnector, IJVMAcceptor)
  • Polling HTTP transport implementation (IHTTPConnector, IHTTPAcceptor)


Examples

  • Extensible collaborations platform with buddy list, chat, fileshare, ...
  • JMS(TM) provider implementation (experimental but functional)


Utilities

  • Caching and monitoring framework
  • Special collections
  • Concurrency support
  • Wiring framework (managed containers)
  • Event framework
  • Factory framework
  • Generic finite state machine (FSM)
  • I/O tools
  • Lifecycle framework
  • Operations and maintenance framework (OM)
    • Platform abstraction (OSGi, Eclipse runtime, stand alone)
    • Bundle abstraction
    • Logging abstraction
    • Tracing abstraction
    • Preferences abstraction
    • Progress monitoring framework
  • Memory sensitivity framework
  • Transactional and notifying registries
  • Extensible security framework
  • Generic transactional operations framework
  • Debugging Tools
    • Remote tracing (OM extension + Eclipse UI)
    • Container view (Eclipse UI)
    • Introspector view (Eclipse UI)
  • Extensible DB abstraction framework
    • Derby DB adapter implementation
    • HSQLDB adapter implementation
    • MySQL adapter implementation


More information

The Net4j project uses dynamically-generated release notes, using Bugzilla and CVS data to create accurate lists of bugs closed in each build. This also allows developers and users to see what files were changed for each bug, by who, and when. For details on how this is done, see Search CVS.