JSF 1.2 + Facelets = ClassNotFoundException

I have a pure Facelets application (no JSP) working just fine with JSF 1.1 on Tomcat 5.5.17. From what I understand, since I am not using any JSPs I should be able to just swap in JSF 1.2.
However, when I switch to JSF 1.2 I get ClassNotFoundExceptions on startup for my phase listeners and custom renders. Essentially, I get a class not found exception for any class in my faces-config.xml file.
Any thoughts? Anyone else have this issue?
Caused by: java.lang.ClassNotFoundException: com.myapp.web.faces.event.PartialRendererPhaseListener
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
     at com.sun.faces.util.Util.loadClass(Util.java:406)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:710)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:398)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:328)
Thanks,
Randy

Actually, I am just a bit of an idiot. Turns out I had a compile error that eclipse wasn't showing so it should not be surprising that I get class not found exceptions. :-)
Thanks.

Similar Messages

JSF 2.0: Facelets: No tag libraries (TLDs)?

Hi, I'm currently concerned with JSF 2.0 and Facelets. I found:
- Tags are no longer defined in taglibs (TLDs) (instead they appear to be hard-coded in Java code)
- On the other hand, jsf-impl.jar does ship two taglibs (for HTML and JSF Core), however, these solely include tags that have been existing since JSF 1.2 (the new tags are not defined there)
OK, that may be fine. Nonetheless, now there's a problem with code completion and validation in IDEs (Eclipse in my case).
Any ideas on how to get over that?
Thanks

[1] https://mojarra.dev.java.net/source/browse/mojarra/trunk/jsf-api/doc/web-facelettaglibrary_2_0.xsd?rev=6738&view=log
Excuse me, that's the XSD schema for facelet-taglib. I'd be requesting TLDs or XSDs that contain definitions for commandButton, button, etc.
[2] https://javaserverfaces.dev.java.net/nonav/docs/2.0/pdldocs/facelets/index.html
That's not a XSD or TLD definition file but just documentation. Moreover, it only covers JSF 1.2 tags, not JSF 2.0 tags. (I do know that it does ship with the JSF 2.0 specification.)
- Please remember that my final goal would be to have code completion and validation for JSF 2.0 in common IDEs, including Eclipse.
Thanks

JSF/Tiles: [java.lang.ClassNotFoundException: org.apache.tiles.servlets.Til

Hi,
I am working on JSF1.2 in SAP NetWeaver CE and I am using Tiles. Please help me to resolve the following issues.
~~~~~~~~~~~~~~~~~~~
1. File:G:\ws_wd\ce_ws.jdi\LocalDevelopment\DCs\demo.sap.com\lbsjsf\ear\_comp\gen\default\deploy\demo.sap.com~lbsjsf~ear.ear
     Name:lbsjsf~ear
     Vendor:demo.sap.com
     Location:localDevelopment
     Version:20090402105707
     Deploy status:Warning
     Version:NEW
     Description:
          1. Warning occurred on server 4585250 during deploy demo.sap.com/lbsjsf~ear : Web Class Existence Test: servlet class "org.apache.tiles.servlets.TilesServlet" cannot be found in the application class path. Possible reasons: 1) package or class name not correct; 2) missing referenced component (application or library); 3) missing reference to component (application or library)., file: demo.sap.com~lbsjsf~web.war#WEB-INF/web.xml, column 0, line 0, severity: warning
Warning occurred on server 4585250 during deploy demo.sap.com/lbsjsf~ear : Web Class Existence Test: The servlet "com.cg.lbs.ui.controller.StartupConfigurationServlet" must implement "javax.servlet.Servlet"., file: demo.sap.com~lbsjsf~web.war#WEB-INF/web.xml, column 0, line 0, severity: warning
          2. Warning exception has been returned while the 'demo.sap.com/lbsjsf~ear' was starting. Warnings:
Warning occurred on server 4585250 during startApp demo.sap.com/lbsjsf~ear : Cannot load servlet [org.apache.tiles.servlets.TilesServlet]. Error is: [java.lang.ClassNotFoundException: org.apache.tiles.servlets.TilesServlet
------------------------- Loader Info -------------------------
ClassLoader name: [demo.sap.com/lbsjsf~ear]
Living status: alive
Direct parent loaders:
[system:Frame]
[service:servlet_jsp]
[service:ejb]
Resources:
F:\usr\sap\CE1\J00\j2ee\cluster\apps\demo.sap.com\lbsjsf~ear\servlet_jsp\lbsjsf\root\WEB-INF\classes
++++++++++++++below is my web.xml+++++++++
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
     id="WebApp_ID" version="2.5">
     <display-name>
          LocalDevelopment~LocalDevelopment~lbsjsf(2fweb~demo.sap.com
     </display-name>
     <filter>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <filter-class>
               org.apache.myfaces.webapp.filter.ExtensionsFilter
          </filter-class>
          <init-param>
               <param-name>maxFileSize</param-name>
               <param-value>20m</param-value>
          </init-param>
     </filter>
     
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          
          <servlet-name>Faces Servlet</servlet-name>
     </filter-mapping>
     
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
     </filter-mapping>
     
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
          <url-pattern>*.jsf</url-pattern>
     </filter-mapping>
     <servlet>
          <servlet-name>Tiles Servlet</servlet-name>
          <servlet-class>
               org.apache.tiles.servlets.TilesServlet
          </servlet-class>
          <init-param>
               <param-name>definitions-config</param-name>
               <param-value>/WEB-INF/tiles.xml</param-value>
          </init-param>
          <load-on-startup>3</load-on-startup>
     </servlet>
     <servlet>
          <servlet-name>Faces Servlet</servlet-name>
          <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup>2</load-on-startup>
     </servlet>
     <servlet>
          <servlet-name>StartupConfiguration</servlet-name>
          <servlet-class>
               com.cg.lbs.ui.controller.StartupConfigurationServlet
          </servlet-class>
          <init-param>
               <param-name>log4j-init-file</param-name>
               <param-value>sswblog4j.xml</param-value>
          </init-param>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>*.faces</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.html</welcome-file>
     </welcome-file-list>
</web-app>

That's a pretty decent error message. Have you eliminated the potential causes which were listed in the message?

Problem with Richfaces, JSF 1.2, Facelets application

Hello
I have trouble using Weblogic 10.3.3 with my JSF-application which is constructed using Richfaces 3.3.3 and Facelets. First I had problems with deployment but with adding weblogic.xml to project.
This is the weblogic.xml content :
<?xml version = '1.0' encoding = 'windows-1252'?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2</implementation-version>
<exact-match>false</exact-match>
</library-ref>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
This application works without problems in Glassfish 2.1 but when I try to access my application in Weblogic, I get following exception :
Error 500--Internal Server Error
javax.el.ELException: /Main.xhtml: The class 'katva.soa.logging.web.soaloggerweb.SessionController' does not have the property 'navigateToMonitor'.
     at com.sun.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:53)
     at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39)
     at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149)
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:942)
     at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
     at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100)
     at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:176)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109)
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
     at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
     at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
     at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
SessionController - managed bean has method mentioned above, here is the part of the page where the SessionController - bean is referenced:
<a4j:form id="linkForm">
<li><h:commandLink value="#{msgs.Main_logSearchLink}" action="#{SessionController.navigateToMonitor}"/></li>
<li><h:commandLink value="#{msgs.Main_maintenanceLink}" action="#{SessionController.navigateMaintenance}"/></li>
</a4j:form>
Could someone help with this ? I am getting desperate and I would need to solve this quite quickly...
Thank you for everyone who can help with this
Best Regards Tuomas Katva

This is probably related: Facelets not rendered on Weblogic 10.3.3
A step by step example
- create a web.xml file, with the following contents:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
         version="2.5">
    <context-param>
        <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
        <param-value>.xhtml</param-value>
    </context-param>
    <context-param>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>server</param-value>
    </context-param>
    <context-param>
        <param-name>org.richfaces.SKIN</param-name>
        <param-value>blueSky</param-value>
    </context-param>
    <context-param>
        <param-name>org.richfaces.CONTROL_SKINNING</param-name>
        <param-value>enable</param-value>
    </context-param>
    <filter>
        <filter-name>RichFaces Filter</filter-name>
        <filter-class>org.ajax4jsf.Filter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>RichFaces Filter</filter-name>
        <servlet-name>Faces Servlet</servlet-name>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
        <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
    <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <listener>
        <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
    </listener>
</web-app>- create a faces-config.xml file with at least the following contents:
<?xml version='1.0' encoding='UTF-8'?>
<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"
              version="1.2">
    <application>
        <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
    </application>
</faces-config>- create an example page
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
        PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"
      xmlns:h="http://java.sun.com/jsf/html"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:a4j="http://richfaces.org/a4j"
      xmlns:rich="http://richfaces.org/rich">
<head>
    <title></title>
</head>
<body>
<a4j:form id="form">
    <rich:panel header="Login" style="width: 750px">
        <h:panelGrid columns="3">
            <h:outputText id="label" value="Password"/>
            <h:inputText id="login" value="Type Your Password"/>
            <rich:message for="login"/>
            <f:facet name="footer">
                <rich:toolBar height="20" itemSeparator="line">
                    <rich:toolBarGroup location="right">
                        <h:commandButton value="Click To Login"/>
                    </rich:toolBarGroup>
                </rich:toolBar>
            </f:facet>
        </h:panelGrid>
    </rich:panel>
</a4j:form>
</body>
</html>- package this into the following structure:
WAR
    WEB-INF
         faces-config.xml
         web.xml
         lib
            commons-beanutils-1.7.0.jar
            commons-collections-3.2.jar
            commons-digester-1.8.jar
            commons-logging-1.0.4.jar
            jhighlight-1.0.jar
            jsf-api.jar
            jsf-facelets.jar
            jsf-impl.jar
            jstl-api-1.2.jar
            jstl-impl-1.2.jar
            richfaces-api-3.3.1.GA.jar
            richfaces-impl-3.3.1.GA.jar
            richfaces-ui-3.3.1.GA.jar
    test.xhtmlAnd deploy it to WebLogic. Upon deployment the following logging is observed:
Jul 4, 2011 2:09:44 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra (1.2_14-b01-FCS) for context '/JSFFaceletsRichFaces'
Jul 4, 2011 2:09:45 PM com.sun.faces.spi.InjectionProviderFactory getProviderInstance
SEVERE: JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
Jul 4, 2011 2:09:45 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFO: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.CacheManager getCacheFactory
INFO: Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.LRUMapCacheFactory createCache
INFO: Creating LRUMap cache instance using parameters: {org.richfaces.CONTROL_SKINNING=enable, javax.faces.STATE_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, com.sun.faces.injectionProvider=com.bea.faces.WeblogicInjectionProvider, org.richfaces.SKIN=blueSky}
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.LRUMapCacheFactory createCache
INFO: Creating LRUMap cache instance of default capacity
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.CacheManager getCacheFactory
INFO: Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.LRUMapCacheFactory createCache
INFO: Creating LRUMap cache instance using parameters: {org.richfaces.CONTROL_SKINNING=enable, javax.faces.STATE_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, com.sun.faces.injectionProvider=com.bea.faces.WeblogicInjectionProvider, org.richfaces.SKIN=blueSky}
Jul 4, 2011 2:09:45 PM org.ajax4jsf.cache.LRUMapCacheFactory createCache
INFO: Creating LRUMap cache instance of default capacityEnter the URL to access the application, for example, http://localhost:7001/JSFFaceletsRichFaces/faces/test.xhtml
et voila RichFaces and Facelets on WebLogic

Has anyone successfully implemented the JSF Viewer with Facelets?

We have recently started integrating Crystal into one of our web apps that is using JSF + Facelets + Seam.
I've built a taglib for the jsf viewer and configured it in web.xml and faces-config. I'm pulling an IReportSource from a backing bean using com.crystaldecisions.reports.sdk.ReportClientDocument and that is using a .rpt file stored on a directory. This all seems to be working, as I can step through the code and see the IReportSource being generated.
However, when the page loads, I am seeing the crystal javascript being converted in the page source, but nothing is loading on the page.
Has anyone seen an issue similar to this tied to Facelets? I've seen numerous documentation on Crystal and JSP, but very little on JSF or Facelets.
Has anyone been able to get a setup like this or similar to work properly?
I've also noticed an error when adding the viewer:
java.io.IOException: Recover report client document state failed.
at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.readExternal(SourceFile:1492)
at com.crystaldecisions.sdk.occa.report.application.AdvancedReportSource.readExternal(SourceFile:131)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
I believe this to be related to me switching over to the serializable ReportClientDocument: com.crystaldecisions.sdk.occa.report.application.ReportClientDocument versus using the nonserializable version.
When using the non-serializable version, I am seeing a constructor issue with the JPEReportSource
Exception: java.io.InvalidClassException: com.crystaldecisions.reports.reportengineinterface.JPEReportSource; no valid constructor
Has anyone seen this issue before or able to offer any suggestions?

Well, according to the tutorials I have seen on the internet, I believe CrystalReport was successfully implemented and tested with jsp, to have it working with Facelets, we need to do a little bit of work around. We need to make a new JSF custom component and assign it to an external renderer. then we can use it to view the report
please follow these and it should work after then,
1- bring the following jars into your libs
commons-configuration-1.2.jar
Concurrent.jar
CrystalCommon.jar
CrystalContentModels.jar
CrystalDatabaseConnectors.jar
CrystalFormulas.jar
CrystalQueryEngine.jar
CrystalReportEngine.jar
CrystalReportingCommon.jar
icu4j.jar
jrcadapter.jar
jrcerom.jar
keycodeDecoder.jar
MetafileRenderer.jar
rasapp.jar
rascore.jar
rpoifs.jar
serialization.jar
URIUtil.jar
webreporting.jar
webreporting-jsf.jar
xercesImpl.jar
xml-apis.jar
2- bring the folder "crystalreportviewers115" right under the "WebContent".
3- implement the custom FacesComponent and make it extend the "UIReportPageViewer" as follows;
import packagename.CustomReportRenderer;
@FacesComponent ("packagename.newReportViewer")
public class UIReportViewer extends com.crystaldecisions.report.web.jsf.UIReportPageViewer implements Serializable{
    public UIReportViewer () {
        this.setRendererType("packagename.CustomReportRenderer");
4- implement the renderer and make it extend the "ViewerHtmlRenderer" as follows;
@FacesRenderer(componentFamily="CrystalReports.DHTMLViewer", rendererType="packagename.CustomReportRenderer")
public class CustomReportRenderer extends com.crystaldecisions.report.web.jsf.ViewerHtmlRenderer implements Serializable {
5- make a new tag library xml file next to the web.xml so the application can find the tag configurations. name it "taglib.xml" and add the following inside it;
<facelet-taglib xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee"
    version="2.0">
    <namespace>http://new-jsf-custom-components/</namespace>
    <tag>
        <tag-name>ReportViewer</tag-name>
        <component>
            <component-type>packagename.newReportViewer</component-type>
            <renderer-type>packagename.CustomReportRenderer</renderer-type>
        </component>
    </tag>
</facelet-taglib>
6- configure the web.xml with the following
<context-param>
        <description>
        State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2</description>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>server</param-value>
    </context-param>
    <context-param>
          <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
        <param-value>/WEB-INF/taglib.xml</param-value>
    </context-param>
    <context-param>
        <param-name>crystal_image_uri</param-name>
        <param-value>../../crystalreportviewers115</param-value>
    </context-param>
7- implement the reportViewer.xhtml and make sure you have the following;
- in the tag libraries add the namespace schema xmlns:crystalnmcps="http://new-jsf-custom-components/"
- add the new reportViewer component
<crystalnmcps:ReportViewer reportSource="#{youController.reportSource}" displayToolbarLogo="false" parameterFields="#{youController.parameterFields}" allowParameterPrompting="false" />
Now run your app.
I hope this helps. good luck

How to remove an object from session with JSF 2.0 + Faceletes

hi all,
I have a facelets page which calls a backing bean of session scope. Now when ever i click on this page i want the existing bean object to be removed from the session . In my existing jsp i have a logic something like this to remove the object from session
<% if (request.getParameter("newid") != null) {
request.getSession().removeAttribute("manageuserscontroller");
%>
Now i have to refactor my jsp to use facelets and i should not be using scriplets anymore . I did try with JSTL but the <c:remove> tag is not supported by facelets.
Can someone help me how can i refactor this code to work for my facelets?
I really appreciate your help in advance
Thank you

r035198x wrote:
Redesign things so that the remove is done in a backing bean method rather than in a view page.Exactly that. I tend to cleanup session variables at the start and at the end of a page flow; generally the end is some sort of save or cancel action being invoked through a button but that is application specific.

Problem with EL (forEach) in Facelets + JSF 1.2

I am trying to upgrade my application from JSF 1.1 to JSF 1.2. However, I have run into a problem that I can't quite grasp.
I have a backing bean with the following method
public List<String> getFoos() {
return foos;
With JSF 1.1 + Facelets the following EL worked fine
     <c:forEach var="foo"
          items="${page.foos}">
          #{foo}
     </c:forEach>
However, once I upgraded to JSF 1.2 suddenly this EL resolves to nothing. In fact, my getFoos() method on my backing bean is not even called. I have googled around but I cannot seem to find what changed in JSF 1.2 that would break this.
If anyone has any ideas, your help is greatly appreciated.
Thanks,
Randy

I have had problems using Java v8 with CUC. I had to go back to Java v7 to use the Media Master bar. Works fine now.
If that doesn't work you could set up a Greetings Administrator call handler to record the greetings. You could even set up a hidden option to press * (or any digit) from your existing call handler to transfer to the Greetings Administrator call handler. Just need to set an owner for the call handler you want to record the greetings for (Edit/Call Handler Owner), then call the original call handler, press *, put in the username (VM extension), VM password and extension of the call handler you want to record.

Do we need jsf-facelets.jar with JSF2?? Please Help

Hello,
In the VDL Section of this article [http://andyschwartz.wordpress.com/2009/07/31/whats-new-in-jsf-2/#facelets|http://andyschwartz.wordpress.com/2009/07/31/whats-new-in-jsf-2/#facelets]
It says that JSF 2 already has facelets. So do we need facelets jar with jsf2 jars??
I am facing few issues concerning this. Once of them is below.
INFO: Initializing Mojarra 2.0.1 (FCS b02) for context ''
Nov 25, 2009 11:31:48 AM com.sun.faces.config.processor.ApplicationConfigProcessor processViewHandlers
WARNING: JSF1069: Disabling the JSF 2.0 Facelets ViewHandler as an older FaceletViewHandler, com.sun.facelets.FaceletViewHandler, has been explicitly configured. If this is not desired behavior, remove the older FaceletViewHandler and library from your application.
Nov 25, 2009 11:31:48 AM com.sun.faces.config.ConfigManager initializeThanks for responding!

- Not sure of Intellij internals, but you should be able to override the default mapping of the URI to some xml resource that describes the tags -
How do I do that? Should I extract the *.tld files from the jsf-impl.jar and put in WEB-INF and then include the path to it in the facelet?
- How were you making the taglib.xml known to the older runtime? The doctype shouldn't make a difference here. -
I just included my test-component.taglib.xml in the web.xml like this and is still the same.
<context-param>
        <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
        <param-value>/WEB-INF/test-component.taglib.xml</param-value>
    </context-param>This is my taglib file. Any thing wrong below?
<?xml version="1.0" encoding="UTF-8"?>
<facelet-taglib xmlns="http://java.sun.com/xml/ns/javaee"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
             http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd"
             version="2.0">
    <namespace>http://tahir.components/comp</namespace>
        <tag>
            <tag-name>test</tag-name>
            <component>
                <component-type>testComponent</component-type>
                <handler-class>com.customcomponent.handler.TestComponentHandler</handler-class>
            </component>
        </tag>
</facelet-taglib>So when I include the uri in the xhtml file, it says it doesnt recognize the URI. When I add the facelet jar it recognizes it. Not sure whats going on.
Thanks for your time, appreciate it.
Edited by: tz_coder on Nov 27, 2009 7:39 AM

Heap Memory Issue in weblogic 9.2 for a JSF 1.1 web application

Hi,
We are running a JSF application (Myfaces, facelets, tomahawk, richfaces & iBATIS) in weblogic 9.2 server on Solaris 10. This application is deployed in production and works fine under normal circumstances. But when there is a heavy user load we are facing a memory issue. The memory usage is gradually increasing and when it reaches to max, Full GC kicks in again & again which choks up all requests. We don't save anything in session scope. All our backing beans are saved in request scope hence they should be garbage collected after each request done, but this is not happening.
We took the heap dump from production after this issue and analyzed it. After my analysis, I found all objects which are set in request object not being garbage collected and the root referers of all these objects is weblogic.servlet.internal.MuxableSocketHTTP.
I reproduced the similar behaviour in one of our development environment using JMeter. I ran 100 concurrent users in JMeter for almost 1 hour and saw the similar behaviour. Below is the result of all weblogic objects which are still hanging in heap after test was over (I also ran manual Garbage Collector from admin server).
1) weblogic.servlet.internal.MuxableSocketHTTP - 1774 objects - retained heap (1 GB)
2) weblogic.servlet.internal.ServletRequestImpl - 1774 objects - retained heap (1 GB)
My understanding is that every request made to weblogic server goes through the MuxableSocketHTTP object which creates the ServletRequestImpl to serve it. Once the request is served these objects are suppose to be removed. As a result of that whatever is saved in your request will still be hanging.
I am not able to understand why these objects are hanging after request is done. Could anybody answer to my question. I appreciate your help in advance.
The GC setting for weblogic server while startup is:
-XX:MaxTenuringThreshold=15 -XX:+PrintTenuringDistribution -XX:+AggressiveHeap -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:PermSize=128m -XX:MaxPermSize=128m -Xms3g -Xmx3g -XX:NewSize=512m -XX:MaxNewSize=1024m
Thanks MaKK

What happened with this issue? We are seeing something similar on WebLogic 9.2 MP1 in Solaris (Jdk 1.5. patch 10. 32 bit). Out of Memory's with thousands if instances of weblogic.socket.MuxableSocket hanging around.
Our thinking was initally the Java heap, then we thought that maybe the sockets weren't being closed properly, possible in WebLogic or in LiveCycle.
Any info would be greatly appreciated.
Snippet of our stack trace:
<16-Feb-2010 04:30:13 o'clock GMT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
>
javax.ejb.EJBException: EJB encountered System Exception: : java.lang.OutOfMemoryError: Java heap space
     at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:145)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvokeCleanup(BaseLocalObject.java:550)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvokeCleanup(BaseLocalObject.java:496)
     at com.adobe.idp.um.businesslogic.directoryservices.DirectorySynchronizationManagerBean_f5g74_ELOImpl.synchronizeProviders(DirectorySynchronizationManagerBean_f5g74_ELOImpl.java:267)
Joel

Facelets + tomahawk + SJSAS

Hi
I had posted this in the wrong forum. So I apologise if this looks familiar to some of you.
I am creating a JSF application using Facelets and tomahawk, deploying on SJSAS 8.1.
I have noticed some weird behavior:
1. If there is a problem with a tomahawk component, it is not registered in the log. For example, if I specify an invalid EL expression, normal HTML components will register this as an error in the log, tomahawk components do not.
2. I have an action that gets a record for the database and fills a Javabean (using OJB) or will create a new object. It will then navigate to a new page. If I add invalid information to a page, it registers the validation message in a messages component. However, if I redeploy the application and try opening a new record, I get the following error:
javax.faces.FacesException: #{promotionSelectPage.editPromotion}: javax.faces.el.EvaluationException: /promoSearch.xjsf @16,89 action="#{promotionSelectPage.editPromotion}": java.lang.IllegalStateException
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:78)
javax.faces.component.UICommand.broadcast(UICommand.java:312)
javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267)
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381)
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:225)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:193)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
java.security.AccessController.doPrivileged(Native Method)
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
3. Probably related to the previous issue, the tomahawk messages component (which I am using) is meant to display the label of the offending field. However, this does not work for me.
Any ideas of what could be wrong or how to debug this?
Cheers.

Apologies, wrong forum. I would remove this, if I knew how.
Message was edited by:
KamBha

JSF 1.2 and

Hello!
I used MyFaces + Facelets and have no problems with After switching to JSF 1.2_01 I getting this strange error:
XML Parsing Error: undefined entity
Location: http://boris.nikom.ru:8080/test.jsf
Line Number 16, Column 14: <tr><td> </td></tr>
The original file looks like (please note I use   not directly):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:t="http://myfaces.apache.org/tomahawk">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<head>
<link rel="STYLESHEET" type="text/css" href="/css/style.css"/>
</head>
</head>
<body>
<table>
<tr><td> </td></tr>
</table>
</body>
</html>
My enviroment is: Resin 3.0.20, JSF 1.2_01, Facelets 1.1.11
WEB-INF/lib context:
commons-beanutils-1.7.0.jar commons-logging-1.0.4.jar
commons-codec-1.3.jar el-api.jar
commons-collections-3.1.jar el-ri.jar
commons-digester-1.6.jar jsf-api.jar
commons-el-1.0.jar jsf-facelets.jar
commons-fileupload.jar jsf-impl.jar
commons-lang-2.1.jar

Hello!
Detailed explanation of problem:
1) FireFox send HTTP Accept header with text/xml,application/xml,application/xhtml+xml ... etc
2) JSF 1.2 returns Content-Type: application/xhtml+xml
3) Based on the return type FireFox tries to validate XML and fails.
MyFaces always returns content-type text/html. So, question to gurus - is this correct behavior of JSF 1.2 or should be reported as bug?
With respect,
Boris

JSF 1.2 + Shale Tiles Example needed

Hello,
I'm trying to develop application by using jsf 1.2 and Shale tiles. I have a problem with configuration. I was working before with Struts Tiles and MyFaces but it isn't the same.
Can somebody provide my some exanle simle aplication of using Shale Tiles and JSF 1.2?
Thx.

To make templates in JSF we use Facelets here. I think Tiles = Strus , Facelets = JSF.
Cya.

JSF 1.2 app is deployed only in exploded archive mode if JSF 2.0 facet used

Hi.
I'm developing JSF 1.2 + facelets application. The only way to configure eclipse WTP editors to properly handle xhtml pages is to install JSF 2.0 facet (there was facelets plugin before, but it was superseded by JSF 2.0 facet if I'm not mistaken). When application is deployed on WL, OEPE show message that JSF 2.0 applications can be deployed only in exploded archive mode.
Is there any way to make OEPE to believe that this application is based on JSF 1.2 (as really is)?
Regards,
Vadim.

Hi, Ian.
You are stating that it's a JSF 2.0 app by selecting that facet - the tooling relies on your facet selection to determine what features are available.Thought as much. Determining which JSF implementation will be active at deployment time looks like very complicated task and facet version is a reliable source of such kind info. Sadly :)
What "eclipse WTP editors" are you trying to configure?"HTML editor". Without JSF 2.0 facet it doesn't handle JSF taglibs' namespaces and EL expressions content assist/navigation.
The other option is to install JBoss Tools richfaces support, but for various reasons I'd like not to.
After using exploded deployment for a week now I see that it is not that slow as I initially thought (at least for a small project): JSP/XHTML changes picked up, class methods reloaded. Manual republishing is still not as fast as in case of the splitsource deployment, but it don't call it often.
Thanks.
Edited by: user3269289 on Apr 8, 2011 2:34 AM

Where do I put the Jakarta files standard.jar and jstl.jar when developing with JSF 2.0 in OEPE using web logic server

hi everybody, I am wondering what should i do with the standard.jar and jstl.jar files when using we logic. I tried putting both files into
the directory c:\oracle\middleware\oracle_home\user_projects\domains\base_domain\bin. I don't know if this is correct. Thanks in
in advance for the help.

Anyways I found this link on www.oracle.com website by the same author of the book I am reading Deepak Vohra - Templating with JSF 2.0 Facelets.
although here he is using Weblogic 11g although I don't think it makes a difference. have a look at the Setting up the Environment section
where he says to download the jstl.jar and standard.jar files.
http://www.oracle.com/technetwork/articles/java/facelets-454361.html

Migrating from JSP to Facelets

Hello,
we have an old application based on JSPs which we like to migrate to JSF and Facelets.
For a phase 1 we decided to leave the JSPs as untouched as possible, but establish the use of JSF and the Facelet templating mechanism.
So the question is, how can we keep the content of the JSP page for a first step and use that within a part of the template, e.g. the ui-composition "content"?
I found some articles about the general transition to Facelets, but I have problems with the details, especially, how to deal with all that Java-Code within <% ... %> blocks?
Thanks in advance,
Geziefer

Thanks for the clear answer - although I'd wish it was different.
Well, basically the existing application must be reimplemented. But as it is still important, heavily in use and the logic within the pages should be kept, we plan to do a page-by-page migration to JSF/Facelets.
And that's why I hoped to be able to do the templates and the navigation and all the framework stuff in a step 1 and keep all the rest, and only after finishing that do the page-by-page migration.
Is it possible to kind of call or include the old jsp as an intermediate step within the facelet?
Geziefer

JSF 1.2 + Facelets = ClassNotFoundException

Similar Messages

Maybe you are looking for