아파치 소프트웨어 재단은 아파치 오픈 소스 소프트웨어 프로젝트 커뮤니티 지원을 제공합니다.
아파치 프로젝트는 협업과 개발 프로세스를 기반으로 하는 상호간의 공감대와 개방되어 있는 실용적인 소프트웨어 라이센스, 그 분야에서 선두를 달릴 수 있는 고품질 소프트웨어 개발을 추구하고 있습니다.
우리는 심플한 서버 공유 프로젝트의 모임이라고도 하지만 오히려 개발자와 사용자간의 커뮤니티라고 생각합니다.
** Bug
* [FELIX-1162] - Component.getReferences returns null if a component that has references is not enabled.
* [FELIX-1166] - SCR does not rebind ConfigurationAdmin service in Sling jcrinstall tests
* [FELIX-1173] - Concurrency Issues while containing bundle is stopping
* [FELIX-1177] - Components must correctly be disposed off
* [FELIX-1178] - Component may remain deactivated after a reference has been unregistered and registered again
* [FELIX-1185] - If a static/mandatory reference to a service is unregistered, the component should be deactivated synchronously instead of asynchronously
* [FELIX-1195] - NullPointerException in ComponentActivatorTask if component is destroyed
* [FELIX-1238] - NPE when invoking "scr list" with no components registered
* [FELIX-1252] - NullPointerException in "scr list" command
* [FELIX-1413] - Newly registered services must not immediately bound for static references
* [FELIX-1414] - Service ranking is only obeyed on first component activation
* [FELIX-1416] - Wrong factory configuration behaviour
* [FELIX-1436] - Descriptors with duplicate implementation and/or service elements are invalid
* [FELIX-1437] - DS 1.1 signatures for activators and bind methods only available for declaration with new namespace
* [FELIX-1440] - Abort method (binder, activator) method search on non-accessible suitable methods
* [FELIX-1445] - When a component is deactivated due to the deactivation of a service to which it staticly 1..1 references, this component is not reactivated when that service is reregistered.
* [FELIX-1503] - Component Factory instances are not let gone after dispose
* [FELIX-1504] - ComponentInstance implementation is reused accross reactivations
* [FELIX-1658] - Deadlocks caused by component activation and deactivation
* [FELIX-1666] - Missing support for DS 1.1 specified lazy activation behavior
* [FELIX-1674] - typo in scr and webconsole - "unsatisifed"
* [FELIX-1714] - typo in scr command
* [FELIX-1733] - Disposed components are not removed from the component registry
* [FELIX-1825] - Configurations of delayed components are not deactivated if not used any more
* [FELIX-1826] - ComponentException must be thrown if ComponentFactory.newInstance cannot create a component instance
* [FELIX-1827] - Check permission before getting or registering services
* [FELIX-1830] - Support for DS 1.1 character property type name
* [FELIX-1832] - ServiceFactory must not be deactivated if the instances fails to be created
* [FELIX-1833] - Stopping the Felix SCR bundle may leave traces behind thus preventing the class loader from being GC-ed
** Improvement
* [FELIX-1186] - Defer the construction of a log message
* [FELIX-1223] - Replace ManagedService[Factory] by ConfigurationListener based component configuration
* [FELIX-1239] - AbstractComponentManager.getServiceReference need not be synchronized
* [FELIX-1313] - Declarative Services bundle should not export Configuration Admin package
* [FELIX-1314] - Restructure SCR implementation package
* [FELIX-1443] - Unify Method lookup
* [FELIX-1447] - Remove ComponentMetadata parameter from AbstractComponentManager.log method signature
* [FELIX-1530] - Extend the SCR introspection API to reflect the new DS 1.1 features
* [FELIX-1686] - Missing activate or deativate methods show up as Error in LogService
* [FELIX-1735] - Use system property to provide bundle jar file to integration tests
* [FELIX-1823] - Drop support for Framework API 1.3 (R4.0)
** New Feature
* [FELIX-924] - No component instance if no Configuration
* [FELIX-925] - Extend SCR to allow alternate activate and deactivate method signatures
* [FELIX-927] - Allow bind and unbind methods to receive the service properties
* [FELIX-928] - Allow use of wildcards in Service-Component header
* [FELIX-929] - Making name attributes optional
* [FELIX-930] - XML schema namespace change
* [FELIX-1232] - Do not use private configuration properties as service properties
* [FELIX-1284] - Support for the 'modified' operation (DS in OSGi 4.2 compendium)
** Task
* [FELIX-1711] - Remove OSGi library source from SVN and depend on official R4.2 libraries
The Apache Software Foundation together with Sri Lankan FOSS community invites you to submit a proposal for a presentation at APACHE ASIA ROADSHOW 2009.
If you are a community member of any Apache projects or If you have worked with Apache projects or have a revolutionary idea on the use of an Apache project, then we would like to hear from you!
Please use the following link for submissions http://www.foss.lk/events/apacheasia09/cfp and the due date for submission is November 8th. APACHE ASIA ROADSHOW 2009 (Colombo) will be held in Colombo, Sri Lanka from December 3rd to 5th, 2009.
See the full release notes below for details about this release.
Release Notes -- Apache Jackrabbit -- Version 2.0-beta1
Introduction
------------
This is a beta release of Apache Jackrabbit 2.0. This release is a fully
compliant implementation of the JCR 2.0 API that was specified by the
Java Specification Request 283 (JSR 283, http://jcp.org/en/jsr/detail?id=283).
However, the beta status of this release means that some parts of the
implementation are not yet ready for normal production use.
Changes in this release
-----------------------
Jackrabbit 2.0 is a major upgrade from the earlier 1.x releases. The most
notable changes in this release are:
* Upgrade to JCR 2.0. This Jackrabbit release implements and is based
on the official JCR 2.0 API. All of the features required by the JSR 283
specification have been implemented.
* Upgrade to Java 5. All of Jackrabbit (except the jcr-tests component)
now requires Java 5 as the base platform. Java 1.4 environments are no
longer supported.
* Removal of deprecated classes and features. Jackrabbit 2.0 is not
backwards compatible with client code that used any classes or features
that had been deprecated during the 1.x release cycle.
* Separate JCR Commons components. Many of the general-purpose JCR
components like JCR-RMI and OCM are now developed and released
separately from the Jackrabbit content repository. See the individual
components for their most recent releases.
* Data store feature enabled in the default repository configuration.
* Full text indexing with Apache Tika. Jackrabbit can now extract and
index the full text content of many new types of documents, including
the Office Open XML files produced by Microsoft Office 2007 and higher.
For more detailed information about all the changes in this and other
Jackrabbit releases, please see the Jackrabbit issue tracker at
This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.
The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS.
About Apache Jackrabbit
-----------------------
Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR). A content repository is a
hierarchical content store with support for structured and unstructured
content, full text search, versioning, transactions, observation, and
more.
About The Apache Software Foundation
------------------------------------
Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.