아파치 소프트웨어 재단은 아파치 오픈 소스 소프트웨어 프로젝트 커뮤니티 지원을 제공합니다.
아파치 프로젝트는 협업과 개발 프로세스를 기반으로 하는 상호간의 공감대와 개방되어 있는 실용적인 소프트웨어 라이센스, 그 분야에서 선두를 달릴 수 있는 고품질 소프트웨어 개발을 추구하고 있습니다.
우리는 심플한 서버 공유 프로젝트의 모임이라고도 하지만 오히려 개발자와 사용자간의 커뮤니티라고 생각합니다.
MyFaces Core는 central Maven repository에서 그룹ID "org.apache.myfaces.core"로 활동하고 있습니다.
Release Notes - MyFaces Core - Version 2.0.0
Bug
* [MYFACES-2361] - Add missing component system event dispatches
* [MYFACES-2554] - myfaces's facelettaglibrary XSD incomplete
* [MYFACES-2615] - Conversion errors should add a FacesMessage instead of throwing a FacesException
* [MYFACES-2621] - BeanValidation does not work with Unified EL 2.2
* [MYFACES-2622] - BeanValidator has to handle CompositeComponentExpressionHolder when resolving the ValueExpression
* [MYFACES-2623] - validation-api and el-api 2.2 should be optional dependencies with scope compile in myfaces-api
* [MYFACES-2624] - Automatically add h:messages if ProjectStage is Development
* [MYFACES-2625] - TagLibrary using custom namespace fails to load composite component
* [MYFACES-2626] - Application.createResource does not trip extension from resource name when try to resolve composite component class automatically
* [MYFACES-2630] - HtmlBody 'onload' attribute encoding issues
* [MYFACES-2631] - javax.faces.Messages.zh lacks two properties.
* [MYFACES-2633] - Cannot set properties on custom composite component class when are implemented on getter/setter
* [MYFACES-2636] - Need to check for null ValueExpression in _BeanValidatorUELUtils.getUELValueReferenceWrapper()
* [MYFACES-2637] - Serious Bug! ajax cant work using multiple forms.
* [MYFACES-2639] - Make org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS param = auto the default
* [MYFACES-2641] - Use the application's ViewHandler to create the view in FaceletViewMetadata
* [MYFACES-2643] - Update Google App Engine APT Doc
* [MYFACES-2645] - The view state is saved before encodeAll() is called on every UIViewParameter in an AJAX request
* [MYFACES-2646] - Missing unit test for application.createComponent(FacesContext context, Resource componentResource)
* [MYFACES-2647] - MyFacesContainerInitializer doesn't check for null class name
* [MYFACES-2649] - Ajax chokes on script triggered onchange if input has onchange=""
* [MYFACES-2650] - chaining ajax onchange with existing onchange creates syntax error
* [MYFACES-2654] - Trinidad ajax-branch does not work with MyFaces2
* [MYFACES-2656] - Use UINamingContainer.getSeparatorChar instead NamingContainer.SEPARATOR_CHAR
* [MYFACES-2657] - Already escaped apostrophes are double-escaped while building the ClientBehavior JavaScript
* [MYFACES-2659] - TagDecorator in IMPL and API ...
* [MYFACES-2661] - h:link render conversationContext param multiple times
Improvement
* [MYFACES-2546] - Conversion rules for obtaing renderable String from the "value" property of SelectItem
* [MYFACES-2658] - Indicate a better error when using Facelet TAGs on JSP(X) pages
New Feature
* [MYFACES-2116] - TODO 65: Partial View Lifecycle
* [MYFACES-2644] - IDE Tutorials for Myfaces 2 Google App Engine support
Task
* [MYFACES-2124] - Enforce new API on UIViewRoot
* [MYFACES-2183] - Integrate Facelets
* [MYFACES-2323] - Implement <f:ajax> tag handler
* [MYFACES-2329] - Add Facelet taglib 2.0 schema
* [MYFACES-2619] - FacesContext.validationFailed() must be called on validation errors in validate()
* [MYFACES-2648] - AbstractMyFacesListener is not needed anymore
* [MYFACES-2653] - Fix implee6 include on code and clean myfaces impl pom.xml
* [MYFACES-2660] - Review Facelets api usage
See the full release notes below for details about this release.
Release Notes -- Apache Jackrabbit -- Version 2.1.0
Introduction
------------
This is Apache Jackrabbit 2.1.0, a fully compliant and production-ready
implementation of the Content Repository for Java Technology API, version 2.0
(JCR 2.0, http://jcp.org/en/jsr/summary?id=283).
Changes in this release
-----------------------
Jackrabbit 2.1 is an incremental feature release based on the earlier
2.0 release. The most notable changes in this release are:
* Remoting improvements. Both the WebDAV and RMI remoting layers have
been extended to support a wider subset of JCR 2.0 functionality
and include numerous other improvements and bug fixes over previous
releases. We recommend the WebDAV layer as the primary remoting option,
with the RMI layer as a secondary option if more functionality is needed.
* Command line repository access. The jackrabbit-standalone jar now
contains a simple command line tool for browsing and modifying both
local and remote repositories.
* Improved JCA packaging. The jackrabbit-jca package can now be used to
enable JCA-based access to any JCR repository that supports the JCR 2.0
RepositoryFactory interface.
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.