| TWiki . Projects . SunJSFImplFaq |
javax.servlet.ServletException: Cannot find FacesContext How do I fix this?
FacesServlet. Make sure you have properly mapped the FacesServlet. You need to follow the insructions in Writing the web.xml File
and
Invoking the FacesServlet in the JavaServer Faces Tutorial.JavaServerFaces team practices Test First Design. All code checked in must be accompanied by a new automated testcase that exercises that code, or changes to an existing automated testcase that exercises the code. When writing your code, you have the choice of whether a unit test or a system test would be more appropriate to verify the correctness of your code. Unit tests live in the jsf-ri/test directory, and system tests live in the jsf-ri/systest directory. Please read this article, other literature, or contact project owner for an introduction to Test First Design.
repository is described in a "change bundle" and sent to dev@javaserverfaces.dev.java.net for review by module owners. If the change-bundle is to fix a bug, the change-bundle can be posted to the bug (either as an attachment or a comment) and a pointer to the bug can be sent to dev@javaserverfaces.dev.java.net.
The change bundle should be sent in a way that is easiest for the reviewer to review. Examples of change-bundles can be found here.
For your convenience, you can simply fill out the change-bundle template, deleting the text in []. Please refer to the issue "id" in the bundle and in the subject of your email.Looks good, r=edburnsant'ant test' on jsf-api and 'ant test' on jsf-ricvs -n update -d -Pcvs update -d -P
and go to the top of this process.cvs commit
Type in your log message, or import it from a message file via cut and past or some such.com.sun.faces.util.Util you find some usefull constants for
logging:
FACES_LOGGER=javax.enterprise.resource.webcontainer.jsf: It concerns every logger.
Other logger constants are:
RENDERKIT_LOGGER = ".renderkit"TAGLIB_LOGGER = ".taglib"APPLICATION_LOGGER = ".application"CONTEXT_LOGGER = ".context"CONFIG_LOGGER = ".config"LIFECYCLE_LOGGER = ".lifecycle"TIMING_LOGGER=".timing"javax.enterprise.resource.webcontainer.jsf.renderkit.
<java-config> element, and add there a <jvm-options>.
If you have put the "jsf-log-config" file in "domains/domain1/config/", for example, your jvm-options looks like this:
<jvm-options>-Djava.util.logging.config.file=${com.sun.aas.instanceRoot}/config/jsf-log-config</jvm-options>
$JAVA_HOME/lib/ext/sunjce_provider.jar to glassfish.home/lib.GlassFish.home/domains/domain1/config/domain.xml . Look for java-config element. Set "debug-enabled" to "true". Restart the server.
NetBeansdebugger. Use the following values for Attach and click on "OK".
SocketAttachTransport: dt_socket Host: your host name Port: 9009 (If you modified domain.xml to use a different port, use that port number) Now, when you deploy and run your JSF application, you should see the debuuger stop at your break points.
The JSF Team has a new, experimental, download offering in its
Documents and Files section that will overlay the latest JSF nightly
onto a given glassfish install directory. Please visit the nightly build section of the JSF Documents and Files project and
download the jsf-glassfish-updater.jar. This file contains
the latest JSF nightly and can be executed as follows to install it into
glassfish.
java -jar jsf-glassfish-updater.jar <PATH_TO_YOUR_GLASSFISH_INSTALL_DIRECTORY>
Where PATH_TO_YOUR_GLASSFISH_INSTALL_DIRECTORY is the
parent of the lib, bin, domains
(and so on) directories.
The jsf-glassfish-updater.jar file will be updated nightly with the latest JSF nightly build, and is a great way to get the latest JSF in cases where there is no available Glassfish build with the bug-fix you need, or you just don't want to download a whole new Glassfish.
| Parameter name | Deprecated name | Description | Default value |
|---|---|---|---|
| com.sun.faces.numberOfViewsInSession | com.sun.faces.NUMBER_OF_VIEWS_IN_SESSION | Defines the maximum number of serialized views stored in the session. Works with server state saving. | 15 |
| com.sun.faces.numberOfLogicalViews | com.sun.faces.NUMBER_OF_VIEWS_IN_LOGICAL_VIEW_IN_SESSION | 15 | |
| com.sun.faces.preferXHTML | com.sun.faces.PreferXHTML | For the case where a browser supports xhtml and html without a quality. When enabled and this case occurs, then xhtml will be set as the content type. | false |
| com.sun.faces.compressViewState | com.sun.faces.COMPRESS_STATE | When true the view is compressed after it is serialized and before base64 encoded. Works with client state saving. | true |
| com.sun.faces.disableVersionTracking | n.a. | Version tracking detects 1.1 artifacts (FacesContext? or Application implementations as an example) within the 1.2 runtime. If you have a pure 1.2 environment, then you could disable it. | false |
| com.sun.faces.compressJavaScript | n.a. | If true, then the JavaScript rendered by h:commandLink will be compressed to reduce the amount of whitespace transmitted in the response. If false then the JavaScript will be rendered to the client in a well formatted manner. | true |
| com.sun.faces.externalizeJavaScript | n.a. | When true a script element with a src attribute. This allows browsers to cache the JS resource instead of having to write it each time the page is accessed. | false |
| com.sun.faces.sendPoweredByHeader | n.a. | The servlet specification defines an optional header that can be sent by a container to communicate the version of the JSP/Servlet the response was generated by. If this is enabled, then JSF/1.2 is included in this header. | true |
| com.sun.faces.verifyObjects | n.a. | When true JSF makes sure all managed beans components,validators, etc can be instantiated by the runtime | false |
| com.sun.faces.validateXml | n.a. | When true JSF validates the configuration files. | false |
| com.sun.faces.displayConfiguration | n.a. | If true then all web configuration information (context initialization parameters and environment entries) will be written to the log. This is useful during development to confirm your application is configured as expected. Valid values for this parameter are true and false | false |
| com.sun.faces.injectionProvider | n.a. | This parameter specifies a class that implements the InjectionProvider SPI. This implementation represents a hook the JSF implementation will use to provide resource injection support. See the documentation of the InjectionProvider interface for more details | NONE |
| com.sun.faces.serializationProvider | n.a. | This parameter specifies a class that implements the SerializationProvider SPI. This implementation represents a hook the JSF implementation will use in order to allow the use of alternate Serialization implementations. See the documentation of the SerializationProvider interface for more details | NONE |
| com.sun.faces.managedBeanFactoryDecoratorClass | n.a. | Specifies decorator class for the managed bean factory. | NONE |
| com.sun.faces.responseBufferSize | n.a. | This parameter specifies the size, in bytes, of the buffer that is used to write all generated content exluding state. | 4096 |
| com.sun.faces.clientStateWriteBufferSize | n.a. | This parameter specifies the size, in bytes, of the buffer that is used to write client state. It should be noted, that the buffer used is split - half is for raw bytes, the other half is for the Base64 encoded characters of said bytes. So, for example, if the default, 8192, is used, then 4096 of that is used for the bytes, and the other 4096 is used for the Base64 encoded characters. | 8192 |
| com.sun.faces.writeStateAtFormEnd | n.a. | Per the renderkit doc specification, the state information for the view will be written out prior to closing the form tag. However, it may be desirable to have the state information written out after the opening form tag. If this is the case, specifiy this parameter in the web.xml with a value of false (@since 1.2_04). | false |
What are some FrameMaker tips?
Here is a dump of Ed's collected Frame Crib Sheet
Launch frame by double clicking on the book. Then open all the chapters.
Update dates. On TitlePage?.fm update the expert draft version.
Make sure page numbers are updated. File->Edit->Update Book, make sure all boxes are checked.
File->Save as Book. Choose PDF type and location, and accept defaults in setting window, pressing Set on that window.
It's in the Settings window:
How to get rid of them.
Format->Document->Change Bars. Do this for each chapter.
When all of the work for a spec revision has been completed, check the work in, tag the workspace, then clear the changebars in all the chapters, and re-check in the files so they're ready for more revisions.
The character catalog is accessed with the little "f" icon in the upper right hand corner of the inividual MDI window. The Default Font mode is the normal mode. The code mode is for code. The emphasis mode is for italics. Don't use the Italic button.
The paragraph catalog is like the character catalog, but it's a paragraph symbol that accesses it. Commonly used ones are:
Paragraph is the default
Code Bullet 1 is when quoting the API method and signature
Bullet 1 is a bulletted list.
*Codeline is nice for showing XML code. You have to hit the tab key one more time than you think.
Tables
Like word, but not as nice.
Make sure the both the source and target documents are loaded into Frame.
Go to where you want to put the "source" of the reference, and usually, you type "please see". Right click and choose "Cross-Reference".
In the "Cross-Reference" dialog, twiddle the "Document:" drop-down to choose the document in which the target resides.
Twiddle the "Source Type" widget to say "Paragraphs"
Twiddle the "Paragraph Tags" option list to choose the paragraph type, say "Head2" to which you want to refer. As you choose different paragraph types, the section headers should show up in the "Paragraphs" list, to the right. Choose the one you want!
Twiddle the "Format" widget to show the right style, usually "SectionNumber&Title".
Press Insert.
If you can re-create those images as PCX files, you can import them in to the document and they should look good.
To reorder them:
Frame doesn't strip it out, but you can show/hide conditional text before you generate the PDF.
The Show Condition Indicators checkbox toggles whether conditional text should use colors (on) or be black (off). For instance, the Comment conditional text setting makes the text red and underlined when Show Condition Indicators is checked.
A tip on hiding all conditional text in a book:
If you are marking an entire paragraph as conditional text, make sure you select the paragraph marker (viewable when you select View>Text Symbols). If you don't, there will be empty lines in the book when you turn off the conditional text.
----- Revision r50 - 23 Jan 2009 - 20:00:53 - Main.edburns
|