| <?xml version="1.0" encoding="ISO-8859-1" ?> | |
| <!-- | |
| Licensed to the Apache Software Foundation (ASF) under one | |
| or more contributor license agreements. See the NOTICE file | |
| distributed with this work for additional information | |
| regarding copyright ownership. The ASF licenses this file | |
| to you under the Apache License, Version 2.0 (the | |
| "License"); you may not use this file except in compliance | |
| with the License. You may obtain a copy of the License at | |
| http://www.apache.org/licenses/LICENSE-2.0 | |
| Unless required by applicable law or agreed to in writing, | |
| software distributed under the License is distributed on an | |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | |
| KIND, either express or implied. See the License for the | |
| specific language governing permissions and limitations | |
| under the License. | |
| --> | |
| <document> | |
| <properties> | |
| <title>FAQ</title> | |
| </properties> | |
| <body> | |
| <section name="FAQ"> | |
| <p> | |
| <ul> | |
| <li> | |
| <a href="#1. Setup">Setup</a> | |
| </li> | |
| <li> | |
| <a href="#2. Architecture">Architecture</a> | |
| </li> | |
| <li> | |
| <a href="#3. Development">Development</a> | |
| </li> | |
| <li> | |
| <a href="#4. Status">Status</a> | |
| </li> | |
| </ul> | |
| </p> | |
| </section> | |
| <section name="1. Setup"> | |
| <subsection name="1.1. Does Apache Trinidad depend on any particular implementation of JSF?"> | |
| <p> | |
| No. Apache MyFaces Trinidad runs on any implementation | |
| of the JSF 1.1 specification (or later). Apache Trinidad can be used | |
| with either the Sun Reference Implementation or MyFaces. Apache Trinidad | |
| offers a JSF 1.2-based branch that requires a JavaEE 5 engine. | |
| </p> | |
| </subsection> | |
| <subsection name="1.2. What runtime or design time tools can I use to run the demo WAR?"> | |
| <p> | |
| Please see the platform section on the <a href="installation.html#Platform Information">installation</a> page for information on how to deploy to JDeveloper, standalone OC4J, and Tomcat. We'd appreciate any contributions of information on | |
| deployment to other servlet engines (as best as we know, all are supported). | |
| </p> | |
| </subsection> | |
| </section> | |
| <section name="2. Architecture"> | |
| <subsection name="2.1. Can I use standard Faces or MyFaces Tomahawk tags with Apache Trinidad?"> | |
| <p> | |
| Yes; standard Faces tags and Tomahawk tags can be used with MyFaces Trinidad. You can even use <h:form> instead of <tr:form> without losing any MyFaces Trinidad functionality. | |
| </p> | |
| </subsection> | |
| <subsection name="2.2. Why would I use MyFaces Trinidad instead of standard Faces?"> | |
| <p> | |
| Good question. Here's a list of some of the advantages | |
| </p> | |
| <ol> | |
| <li>Rich DHTML client-side renderers </li> | |
| <li>Provide more efficient implementations of client-side state saving (reduced per-component size) </li> | |
| <li>Rich set of components, validators, and converters</li> | |
| <li>MyFaces Trinidad tags often offer more features than the standard tags; for example, | |
| all input components offer built-in label and message display support ( | |
| For more information on the differences between the MyFaces Trinidad tags and the | |
| standard Faces tags, please see the <a href="spec-diff.html">following | |
| document</a>).</li> | |
| <li>Client-side converters/validators - JavaScript enabled converters and validators that attempt to catch and display errors on the client</li> | |
| <li>MyFaces Trinidad tags can be used inside of the <tr:forEach> tag (it is, unfortunately, not possible to support standard tags inside <tr:forEach>). (This limitation does not apply in JSF 1.2.)</li> | |
| <li><i>Accessibility</i> - support for Section 508 </li> | |
| <li><i>Bidirectional language support</i> - Apache Trinidad components automatically render themselves appropriately for bidirectional languages. Users can also use the "start" and "end" constants instead of "left" and "right"</li> | |
| <li><i>Partial Page Rendering (PPR)</i> - Javascript-free support for rerendering any of the Trinidad components</li> | |
| <li><i>Skinning</i> - support for adjusting the look-and-feel of components with an extended CSS format</li> | |
| </ol> | |
| </subsection> | |
| <subsection name="2.3. What is the relationship between Apache Trinidad and ADF UIX?"> | |
| <p> | |
| Apache Trinidad is a significant evolution of the ADF UIX code. The | |
| proprietary API (<code>UINode</code>, <code>RenderingContext</code>, etc.) | |
| of ADF UIX has been replaced with the standard JSF API, and we've added | |
| many features to our components that take advantage of the JSF architecture. | |
| In making this change, we've also overhauled nearly all our component | |
| names and attribute names to fit in closely with JSF naming conventions. | |
| ADF UIX and Apache Trinidad can be installed in a single web application | |
| without conflicts. | |
| </p> | |
| </subsection> | |
| </section> | |
| <section name="3. Development"> | |
| <subsection name="3.1. When I run a JSP, I see 'javax.servlet.jsp.JspException: Cannot find FacesContext'"> | |
| <p> | |
| You cannot directly point to a JSF JSP file; you either need to add "/faces" after the servlet context path, or change the suffix (in the URL only) to ".faces". | |
| </p> | |
| </subsection> | |
| <subsection name="3.2. I'm getting a java.lang.ClassCastException in UIXComponentTag.setProperties()"> | |
| <p> | |
| JSF requires the <f:view> JSP tag around all JSF JSP tags; this obscure error is the result of failing to include <f:view>. (As of May 2007, a | |
| better error message is given.) | |
| </p> | |
| </subsection> | |
| <subsection name="3.3. I'm having a problem seeing dialog windows"> | |
| <p> | |
| You may have trouble seeing dialogs if you have popup blockers installed. | |
| </p> | |
| </subsection> | |
| <subsection name="3.4. My page looks really bad, as if it was totally unstyled"> | |
| <p> | |
| You may have not have configured your Resources Servlet in your web.xml. Please refer to installation instructions to configure the ResourceServlet. | |
| </p> | |
| </subsection> | |
| <subsection name="3.5. My input field is just showing as plain text when not in read-only mode."> | |
| <p> | |
| You may be missing the "setXyz()" function matching the | |
| "getXyz()" function that is controlling your field's value, or | |
| you might have mispelled its name. This makes that property | |
| read-only. When Apache Trinidad detects that an input | |
| field is using a read-only model property, it automatically | |
| switches the field to read-only mode, which is why it looks | |
| like plain text. For what it's worth, if you tried the same model | |
| property with <h:inputText>, it'd look fine when you first render | |
| the page, but JSF would throw an exception when you posted back | |
| to the server and it couldn't write the new value into the model. | |
| </p> | |
| </subsection> | |
| </section> | |
| <section name="4. Status"> | |
| <subsection name="4.1. What is the status of the Apache Trinidad Podling?'"> | |
| <p> | |
| Apache Trinidad graduated from the Incubator in April, 2007. | |
| </p> | |
| </subsection> | |
| </section> | |
| </body> | |
| </document> |