Does anyone happen to know of a class in Java 5 that changed in such a way that its serialized format was incomaptible with Java 1.4, either forwards or backwards? i.e. I'm looking for a class whose Java 5 serialized instances could not be deserialized in Java 1.4 or vice versa. In the examples I've looked at so far Sun's been quite careful to maintain forwards and backwards compatibility despite dire warnings that one can't rely on this. If you happen to know of such a case, please drop me a line. Or failing a Java 5 difference, I could also use differences between Java 1.4 and 1.3. Thanks.
Day Software has submitted JSR-283 Content Repository for Java Technology API 2.0 to the JCP. According to the JSR:
Since this JSR represents an enhancement of JSR-170, the same general goals apply to this JSR as to JSR-170 (from the JSR-170 proposal):
The aim is to produce a content repository API that provides an implementation independent way to access content bi-directionally on a granular level. A content repository is a high-level information management system that is a superset of traditional data repositories. A content repository implements ?content services? such as: author based versioning, full textual searching, fine grained access control, content categorization and content event monitoring. It is these ?content services? that differentiate a content repository from a data repository. Many of today?s (web) applications interact with content repositories in various ways. This API proposes that content repositories have a dedicated, standard way of interaction with applications that deal with content. This API will focus on transactional read/write access, binary content (stream operations), textual content, full-text searching, filtering, observation, versioning, handling of hard and soft structured content.
In particular, the following functional areas will be reviewed by the expert group for possible inclusion in version 2.0:
- Extensions in the area of management of a content repository such as access control management, workspace and nodetype management, retention aspects of content or repository construction patterns.
- Improvement of content repository interoperability through the addition of new standardized node types, including node types for meta information and internationalization.
- Extensions to content modelling capabilities.
- Federation, cross-repository and cross-workspace functionality.
- Active development of existing query-languages, versioning and observation.
- Remoting and client/server protocol mappings.
- Possibly other enhancements.
Comments are due by September 19.