myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Myfaces Wiki] Update of "Drafts/Site/Core" by BartKummel
Date Sat, 12 Feb 2011 14:26:04 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "Drafts/Site/Core" page has been changed by BartKummel.
http://wiki.apache.org/myfaces/Drafts/Site/Core?action=diff&rev1=2&rev2=3

--------------------------------------------------

- ## page was renamed from myfaces/Drafts/Site/Core
+ = The Apache MyFaces Core project =
+ 
  The Apache MyFaces Core project is where it all started. It does not do much more than implement
the JSF standard. There are currently three relevant versions of this standard:
   * JSF 1.1: This version of the standard fixes some bugs in the original 1.0 version. Both
the 1.0 and the 1.1 versions were specified by the Java Specification Request (JSR) number
JSR 127. The versions of MyFaces Core implementing this version of JSF are numbered 1.1.x.
   * JSF 1.2: This version of the JSF standard was specified by a separate JSR, with the number
JSR 252. JSF 1.2 adds some important improvements over JSF 1.1. The MyFaces Core versions
implementing JSF 1.2 are numbered 1.2.x.
   * JSF 2.0: This is the latest version of the JSF standard, part of the Java EE 6.0 platform.
JSF 2.0 is specified in JSR 314, which had its final release on July 1, 2009. The versions
of MyFaces Core implementing JSF 2.0 are numbered 2.0.x. 
  
- The Core project currently has branches for each of these JSF versions. The 1.1, 1.2 and
2.0 versions are stable and are updated regularly. Every Java EE application server comes
with a bundled JSF implementation. Often the reference implementation (RI), known as "Mojarra",
is used for this. However, you can bundle an alternative JSF implementation to be used with
your project. This way, you can use MyFaces Core as JSF implementation on every Java EE application
server. One of the benefits of using MyFaces Core is that it generates more informative logging,
which can be handy while debugging.
+ The Core project currently has branches for each of these JSF versions. The 1.1, 1.2 and
2.0 versions are stable and are updated regularly. 
  
+ == Why should I use MyFaces Core? ==
+ Every Java EE application server comes with a bundled JSF implementation. Often the reference
implementation (RI), known as "Mojarra", is used for this. However, you can bundle an alternative
JSF implementation to be used with your project. This way, you can use MyFaces Core as JSF
implementation on every Java EE application server. One of the benefits of using MyFaces Core
is that it generates more informative logging, which can be helpful while debugging. If you're
looking for an application server that uses MyFaces Core by default, you should take a look
at Apache Geronimo.
+ 
+ == Getting started ==
+ So you want to use MyFaces Core as the JSF implementation in your project. This section
tells you how to get started.
+ 
+ === Maven ===
+ If you're using Maven to manage dependencies, you can use on of the Maven archetypes provided
by the [[Drafts/Site/MavenArchetypes|Maven archetypes]] sub project to generate an empty project
with all of the libraries you need already in place. See the [[Drafts/Site/MavenArchetypes|Maven
archetypes]] for details.
+ 
+ === Managing dependencies manually ===
+ If you're not using Maven, you'll have to manage your dependencies manually. This section
describes what's needed to add MyFaces Core as a dependency to you project.
+ 
+  1. '''Downloading Apache MyFaces Core'''.
+     a. The latest version of MyFaces Core can be downloaded from the [[http://myfaces.apache.org/download.html|MyFaces
Core donwload page]]. Depending on hte JSf version you want to use, you should download a
MyFaces Core 1.1.x, 1.2.x or 2.0.x version. (I.o.w.: the first two digits of the MyFaces Core
version correspond to the JSf version it is designed for.)
+     a. MyFaces Core is available as .zip and .tar.gz file. If you're working on Windows,
you should download the .zip, otherwise, you can download the .tar.gz.
+  1. '''Unpacking the downloaded file'''. Use your favorite unzip / unarchive tool to unpack
the downloaded file. If everything went well, you should end up with a single directory called
{{{myfaces-core-x.y.z-bin}}}, where {{{x.y.z}}} is the version number.
+  1. '''Adding the JARs to you classpath'''. Inside the {{{myfaces-core-x.y.z-bin}}} directory
is a {{{lib}}} directory, that contains a collection of {{{.jar}}} files. For your reference,
here's a drill down of the contents of the {{{lib}}} directory in the distribution:
+     * {{{myfaces-impl-x.y.z.jar}}}: the MyFaces Core JSF implementation.
+     * {{{myfaces-api-x.y.z.jar}}}: the JSF API. These are all the interfaces and classes
that are called from the outside. In other words, these are those things you import from the
{{{javax.faces}}} package.
+     * {{{myfaces-bundle-x.y.z.jar}}}: a combination of the previous two in one single JAR.

+     * {{{commons-......jar}}}: a series of libraries from the Apache Commons project, that
MyFaces Core depends on. 
+    You should add either the {{{myfaces-impl-x.y.z.jar}}} and {{{myfaces-api-x.y.z.jar}}}
or the {{{myfaces-bundle-x.y.z.jar}}} to your project's classpath. Further more, all {{{commons-......jar}}}
files should also be added to the classpath. The procedure to add JARs to a classpath differs,
depending on the IDE you are using for your project.
+ 

Mime
View raw message