Rendering problem ADF Faces OC4J

Hello to everybody , I was trying to install ADF Faces with the new Jdeveloper , but we I run the demo, I don't get anything. I followed all the instructions of
http://www.oracle.com/technology/products/jdev/howtos/10g/adfjsf/how-to-adf-faces-10gjdev.htm
This is the log of OC4J
07/08/2005 03:44:06 AM oracle.adf.view.faces.component.UIXComponentBase _getRendererImpl
ADVERTENCIA: Could not find renderer for CoreOutputText[OutputTextFacesBean, id=text1], rendererType = oracle.adf.Text

Hi,
this one worked for me
<h:form binding="#{backing_untitled1.form1}" id="form1">
<af:commandLink text="Click me"
binding="#{backing_untitled1.commandLink1}"
id="commandLink1" partialSubmit="true"
action="#{backing_untitled1.commandLink1_action}"/>
<af:outputText value="Message"
binding="#{backing_untitled1.outputText1}"
id="outputText1" partialTriggers="commandLink1"/>
</h:form>
The action called sets a new value to the output text
public String commandLink1_action()
// Add event code here...
this.getOutputText1().setValue("Hello");
return null;
Frank

Similar Messages

  • Problems with combination of ADF Faces, Tomahawk, Facelets and MyFaces

    Hello,
    I am trying to combine all things named in the Subject and run into several problems:
    1. ADF Render Kit forces the Tomahawk Components to be rendered in a wrong way or stop there functionality.
    Example 1: The clickable parts of the t:dataScroller Tag can not be accessed because an empty a Tag will be rendered after the outputText.
    Example 2: The t:commandSortHeader Tag can be clicked but the table content will not be sorted anymore.
    The given examples works if i remove the default-render-kit-id element from the faces-config.xml
    2. The ad:table Tag runs into an ClassCastException, only when I put a simple example code snipped into my xhtml file.
    Code snipped:
    <af:table>
    <af:column>
    <f:facet name="header">
    <af:outputText value="Firstname"/>
    </f:facet>
    </af:column>
    <af:column>
    <f:facet name="header">
    <h:outputText value="Lastname"/>
    </f:facet>
    </af:column>
    </af:table>
    The stack trace look like this:
    java.lang.ClassCastException at oracle.adfinternal.view.faces.renderkit.core.xhtml.DesktopTableRenderer._renderRegularColumns(DesktopTableRenderer.java:1029)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.DesktopTableRenderer.renderSingleRow(DesktopTableRenderer.java:109)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.TableRenderer.encodeAll(TableRenderer.java:229)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.DesktopTableRenderer.encodeAll(DesktopTableRenderer.java:79)
         at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeEnd(CoreRenderer.java:159)
         at oracle.adf.view.faces.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:624)
         at oracle.adf.view.faces.component.UIXCollection.encodeEnd(UIXCollection.java:438)
         at oracle.adfinternal.view.faces.renderkit.RenderUtils.encodeRecursive(RenderUtils.java:54)
         at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeChild(CoreRenderer.java:232)
         at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeAllChildren(CoreRenderer.java:255)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:65)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:117)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:147)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:60)
         at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeEnd(CoreRenderer.java:159)
         at oracle.adf.view.faces.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:624)
         at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
         at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
         at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
         at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:521)
         at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
         at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367)
         at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336)
         at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196)
         at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
         at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:122)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    I followed all steps for the ADF installation and the suggested steps for using ADF with Facelets.
    Used versions:
    - Oracle ADF Faces 10.1.3 Early Access
    - myFaces 1.1.1
    - Facelets 1.1.1
    - oc4j 10.1.2.0.2
    Has somebody try to use these things together, too?
    Thanks,
    Carsten

    Hi,
    Inside our fusion applications(ADF/Webcenter) using combination of JSTL and ADF Faces is good practice or pitfal?
    To suggest a a rule of thumb: Try ADF Faces on-board functionality first before reaching out to JSTL. The difference between JSF in general and JSTL is that the JSTL expressions are evaluated at page compile time wheras JSF expressions are evaluated deferred. This difference may have an impact to PPR refreshes and the data rendering (which in many cases I assume you can fix by setting the ADF Faces component content delivery to immediate instead of deferred). On a training slight I flagged JSTL with a "heads up" alert because of this
    Frank

  • MyFaces not rendering, ADF faces IS rendering

    I'm installing my app on the websphere application server, Version 6.1 After having issues of both adf and myfaces not working, I came accross this link which helped me somewhat. http://wiki.apache.org/myfaces/Websphere_Installation .
    By "not working" I mean that my jsp would have <h:commandLink>'s and <af:commandButton/> however the html was never actually generated. (You could view the pages source and the resulting html page was blank).
    After following those instructions, ADF components are correctly rendered, and the html works. However, I can not use any <h:> or <h:> components.
    Keep in mind, every single part of this used to work while using Tomcat (I think it was 5.5, not 6).
    faces-config-app.xml (our replacement for faces-config).
    <?xml version="1.0"?>
    <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
      "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
    <faces-config>
         <!-- ************ Application wide settings **************** -->
         <application>
              <!-- Spring resolve allows access to spring managed beans from <managed-bean> tags -->
              <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
              <!-- Local setup -->
              <locale-config>
                   <default-locale>en</default-locale>
                   <supported-locale>en</supported-locale>
              </locale-config>
              <!-- Message bundle base name -->
              <message-bundle>messages</message-bundle>
              <!-- Use the ADF Faces render kit -->
              <default-render-kit-id>oracle.adf.core</default-render-kit-id>
         </application>
         <lifecycle>
                <phase-listener id="responseHeaderController">com.unyric.cias.cm.web.util.HttpResponseHeaderController</phase-listener>
         </lifecycle>
    </faces-config>web.xml (Yes there is a lot of extra things in there such as application context params, but I wanted to paste the whole thing. Please bear with me).
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
         <display-name>CIAS Case Management Web</display-name>
         <context-param>
              <description>JSF state setting: Keep state of views on client</description>
             <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
             <param-value>client</param-value>
         </context-param>
         <context-param>
              <description>JSF configuration files</description>
             <param-name>javax.faces.CONFIG_FILES</param-name>
             <!-- faces-config.xml contains applicaiton level configuration
                   faces-config-nav.xml contains screen flow configuration
                   faces-config-beans.xml contains managed bean definitions -->
             <param-value>/WEB-INF/faces-config-app.xml,/WEB-INF/faces-config-nav.xml,/WEB-INF/faces-config-beans.xml</param-value>
         </context-param>
         <context-param>
              <description>Spring configuration files</description>
              <param-name>contextConfigLocation</param-name>
              <!-- presentationContext.xml contains presentation tier object configuration
                         applicationContext.xml contains Service & Dao object configuration as well as transaction demarcation
                         securityContext.xml contains Acegi Security configuration
                         hibernate.cfg.xml contains Hibernate specific configuration -->
                <param-value>/WEB-INF/presentationContext.xml classpath*:spring/applicationContext.xml classpath*:spring/validationContext.xml classpath*:spring/securityContext.xml classpath*:spring/hibernate.cfg.xml</param-value>
         </context-param>
         <context-param>
              <description>Validates JSF configuration files on startup</description>
             <param-name>org.apache.myfaces.validate</param-name>
             <param-value>true</param-value>
            </context-param>  
         <context-param>
              <description>Timmer Setting for Case Queue screen</description>
                 <param-name>pollingTimer</param-name>
                 <!-- Units are milliseconds -->
                 <param-value>60000</param-value>
         </context-param>
         <context-param>
              <description>Maximum number of rows shown in tables.</description>
                 <param-name>tableRowsPerPage</param-name>
                 <param-value>25</param-value>
         </context-param>
         <servlet>
              <description>JSF controller</description>
                 <servlet-name>FacesServlet</servlet-name>
                 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
                 <load-on-startup>1</load-on-startup>
         </servlet>
         <!-- Requests handled by JSF -->      
         <servlet-mapping>
               <servlet-name>FacesServlet</servlet-name>
                <url-pattern>*.do</url-pattern>
         </servlet-mapping>
         <servlet>
                <description>Serves up ADF Faces resources</description>
                <servlet-name>AdfResourceServlet</servlet-name>
                <servlet-class>oracle.adf.view.faces.webapp.ResourceServlet</servlet-class>
         </servlet>
         <servlet-mapping>
             <servlet-name>AdfResourceServlet</servlet-name>
             <url-pattern>/adf/*</url-pattern>
         </servlet-mapping>
         <listener>
              <description>Initializes Spring on application startup.</description>
              <display-name>Spring context loader</display-name>
              <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
         </listener>
         <filter>
              <description>Enables Acegi Security framework integration. Acegi is used to secure services.
              Standard J2EE is used to secure web requests.</description>
              <filter-name>AcegiFilterChainProxy</filter-name>
              <filter-class>org.acegisecurity.util.FilterToBeanProxy</filter-class>
              <init-param>
                   <param-name>targetClass</param-name>
                   <param-value>org.acegisecurity.util.FilterChainProxy</param-value>
              </init-param>
         </filter>
         <filter-mapping>
              <filter-name>AcegiFilterChainProxy</filter-name>
              <servlet-name>FacesServlet</servlet-name>
         </filter-mapping>
         <filter>
                <description>Pre-processes requests to enable MyFaces extensions</description>
              <filter-name>MyFacesExtensionsFilter</filter-name>
              <filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
             <init-param>
             <!-- Set the size limit for uploaded files.
               Format: 10 - 10 bytes
                       10k - 10 KB
                       10m - 10 MB
                       1g - 1 GB
               -->
                   <param-name>uploadMaxFileSize</param-name>
                    <param-value>6m</param-value>
             </init-param>
             <init-param>
                   <param-name>uploadThresholdSize</param-name>
                    <param-value>100k</param-value>
             </init-param>        
         </filter>
         <!-- MyFaces extension mapping for adding <script/>, <link/>, and other resource tags to JSF-pages  -->
           <filter-mapping>
                <filter-name>MyFacesExtensionsFilter</filter-name>
             <servlet-name>FacesServlet</servlet-name>
         </filter-mapping>
         <!-- MyFaces extension mapping for serving page-independent resources (javascript, stylesheets, images, etc.)  -->
         <filter-mapping>
             <filter-name>MyFacesExtensionsFilter</filter-name>
             <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
         </filter-mapping>
         <filter>
              <description>Pre-processes requests to enable ADF Faces functionality</description>
              <filter-name>AdfFacesFilter</filter-name>
              <filter-class>oracle.adf.view.faces.webapp.AdfFacesFilter</filter-class>
         </filter>
           <filter-mapping>
                <filter-name>AdfFacesFilter</filter-name>
             <servlet-name>FacesServlet</servlet-name>
         </filter-mapping>
         <!-- Sitemesh Template Filter --> 
         <filter>
              <filter-name>sitemesh</filter-name>
              <filter-class>com.opensymphony.module.sitemesh.filter.PageFilter</filter-class>
         </filter>
         <filter-mapping>
              <filter-name>sitemesh</filter-name>
              <url-pattern>/*</url-pattern>
         </filter-mapping>     
         <!-- Keep Hibernate sessions open until request completes. This allows lazy loading
              of data in all tiers. -->
         <filter>
              <filter-name>OpenSessionInViewFilter</filter-name>
              <filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
              <init-param>
                   <param-name>sessionFactoryBeanName</param-name>
                   <param-value>ciasSessionFactory</param-value>
              </init-param>
              <init-param>
                   <param-name>singleSession</param-name>
                   <param-value>false</param-value>
              </init-param>
         </filter>
         <filter-mapping>
              <filter-name>OpenSessionInViewFilter</filter-name>
              <servlet-name>FacesServlet</servlet-name>
         </filter-mapping>
         <!-- The application automatically sends requests at timed intervals. This causes
                    the standard J2EE session to be refreshed at the timed intervals and thus it will
                    never timeout. This filter is used to distinguish between user prompted and
                    automatic requests. -->
         <filter>
              <filter-name>SessionTimeout Filter</filter-name>
              <filter-class>com.unyric.cias.cm.web.filter.SessionTimeoutFilter</filter-class>
              <init-param>
                   <!-- URL to be displayed after session timeout -->
                   <param-name>redirectUrl</param-name>
                   <param-value>timeOut.jsp</param-value>
              </init-param>
              <init-param>
                   <param-name>sessionTimeout</param-name>
                   <!-- Units are in minutes -->
                   <param-value>20</param-value>
              </init-param>
         </filter>
         <filter-mapping>
              <filter-name>SessionTimeout Filter</filter-name>
              <url-pattern>/secure/*</url-pattern>
         </filter-mapping>
         <!-- Session Timeout (in minutes)
              We are essentially disabling container session
              handling in favor of SessionTimout Filter -->
           <session-config>
                <session-timeout>99</session-timeout>
           </session-config>
           <!-- Security Configuration -->
           <security-constraint>
                <web-resource-collection>
                     <web-resource-name>FacesServlet security</web-resource-name>
                     <url-pattern>*.do</url-pattern>
                     <!-- No <http-method> tag implies all methods -->
                </web-resource-collection>
                <web-resource-collection>
                     <web-resource-name>View security</web-resource-name>
                     <url-pattern>/secure/*</url-pattern>
                     <!-- No <http-method> tag implies all methods -->
                </web-resource-collection>
                <auth-constraint>
                     <description>Allow any authenticated user</description>
                     <role-name>*</role-name>
                </auth-constraint>
          </security-constraint>
           <login-config>
                <auth-method>BASIC</auth-method>
                <realm-name>CIAS-CM</realm-name>
           </login-config>
           <security-role>
                <!-- Roles recognized by Case Management. -->
                <!-- EXACT NAMES MUST BE COORDINATED WITH CHOICEPOINT -->
                 <role-name>case</role-name>
         </security-role>
         <welcome-file-list>
              <welcome-file>index.jsp</welcome-file>
         </welcome-file-list>
         <!--  CIAS CM Database -->
         <resource-ref>
              <res-ref-name>jdbc/cias</res-ref-name>
                <res-type>javax.sql.DataSource</res-type>
                <res-auth>Container</res-auth>
                <res-sharing-scope>Shareable</res-sharing-scope>
            </resource-ref>
         <!--  CIAS Error Handling   -->
           <error-page>
                 <error-code>500</error-code>
                 <location>/secure/errorPage.jsp</location>
           </error-page>
           <error-page>
              <exception-type>javax.faces.FacesException</exception-type>
              <location>/secure/errorPage.jsp</location>
           </error-page>     
    </web-app>Does anyone have any suggestions? Telling websphere to load the web-inf\lib directory before the AppServer\lib directory seems to have somewhat worked, but not completely.
    On a side note, if I have a page such as (ignoring the extra h, f and t declarations)
    <%@ taglib prefix="h"uri="http://java.sun.com/jsf/html" %>
    <%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
    <%@ taglib prefix="t" uri="http://myfaces.apache.org/tomahawk" %>
    <%@ taglib prefix="af" uri="http://xmlns.oracle.com/adf/faces" %>
    <f:view>
         <af:document>
              <af:form>
                   <af:outputText value="hello2"/>
                   <af:commandLink id="button" action="#{exploreCaseListAction.promptPersonalQueue}" text="Login"/>
              </af:form>
         </af:document>
    </f:view>When I click on the commandLink button, I receive an error that states
    java.lang.ClassCastException: org.apache.xalan.processor.TransformerFactoryImpl incompatible with javax.xml.transform.TransformerFactory
    at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
    at com.ibm.ws.jsp.translator.visitor.validator.PageDataImpl._getInputStream(PageDataImpl.java:125)
    at com.ibm.ws.jsp.translator.visitor.validator.PageDataImpl.getInputStream(PageDataImpl.java:117)
    at org.apache.taglibs.standard.tlv.JstlBaseTLV.validate(JstlBaseTLV.java:156)
    at org.apache.taglibs.standard.tlv.JstlCoreTLV.validate(JstlCoreTLV.java:96)
    at com.ibm.ws.jsp.translator.visitor.validator.ValidateVisitor.validateTagLib(ValidateVisitor.java:988)
    at com.ibm.ws.jsp.translator.visitor.validator.ValidateVisitor.visitJspRootStart(ValidateVisitor.java:467)
    at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:138)
    at com.ibm.ws.jsp.translator.visitor.JspVisitor.visit(JspVisitor.java:121)
    at com.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:121)
    at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:181)
    at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:83)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:349)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:317)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:226)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:131)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)
    at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:416)
    at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
    at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
    at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:907)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
    at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:174)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196)
    at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
    at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264)
    at com.unyric.cias.cm.web.filter.ThreadContextSessionIntegrationFilter.doFilter(ThreadContextSessionIntegrationFilter.java:46)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
    at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
    at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
    at org.acegisecurity.wrapper.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:81)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
    at com.unyric.cias.cm.web.filter.CiasIntegrationFilter.doFilter(CiasIntegrationFilter.java:112)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
    at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:193)
    at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
    at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148)
    at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)I believe they are related, though I can't 100% say for sure. Any thoughts?

    I'm having the same problem, did you get any luck with this ?
    Thanks

  • Panel Page in ADF Faces using Facelets not rendering correctly

    Hi, I am attempting to integrate facelets into a web app built using adf faces and am running into a problem with the panel page component. I have integrated facelets and adf faces without any problems by adding relevant jars (jsf-facelets and adf-facelets) to the project and specifying alternate facelets view handler in web.xml.
    However, when I try to render any component inside <af:document> or <af:html> tags, all the font style in components seems to be lost ( all the text and input fields turn large and ugly!).
    I tried to leave out the <af:document> tag and put the <f:view> inside some vanilla html instead, but then panelPage component dosen't render properly and I get following message on top of page :
    "Skip navigation elements to page contents"
    So seem to be in a bit of a catch 22. By the way, this all works fine if I don't use facelets (remove the facelets view handler from web.xml and page renders correctly).
    Does anyone have any ideas or examples of panelPage rendering correctly with facelets or an alternative to using adf faces html tags that will allow panelpage to be displayed?
    The following is the code from a simple test jspx page :
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:afh="http://xmlns.oracle.com/adf/faces/html"
    xmlns:af="http://xmlns.oracle.com/adf/faces"
    xmlns:c="http://java.sun.com/jsp/jstl/core"
    xmlns:ui="http://java.sun.com/jsf/facelets">
    <f:view>
    <af:document>
    <af:form>
    <af:panelPage title="Title 1">
    <af:panelHorizontal>
    <af:panelGroup layout="vertical">
    <af:outputLabel value="Username"/>
    <af:inputText id="lo_username" value="" columns="20"/>
    <af:objectSpacer width="1" height="10"/>
    <af:outputLabel value="Password"/>
    <af:inputText id="lo_password" secret="true" value="" columns="20"/>
    <af:objectSpacer width="1" height="15" />
    <af:panelHorizontal>
    <af:objectSpacer width="50" height="1"/>
    <af:commandButton id="lo_loginButton" text="Login"/>
    </af:panelHorizontal>
    </af:panelGroup>
    <af:objectSpacer width="50" height="1"/>
    <af:panelGroup layout="vertical">
    <af:outputLabel value="Please use your windows account username"/>
    <af:outputLabel value="and password to logon to the system"/>
    <af:objectSpacer width="1" height="50"/>
    </af:panelGroup>
    </af:panelHorizontal>
    </af:panelPage>
    </af:form>
    </af:document>
    </f:view>
    </jsp:root>

    The problem was the <jsp:root> tag. Removed this tag and modified <af:document> to the following so that namespaces are declared :
    <af:document xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:af="http://xmlns.oracle.com/adf/faces"
    xmlns:afh="http://xmlns.oracle.com/adf/faces/html"
    xmlns:ui="http://java.sun.com/jsf/facelets">
    Page now renders properly using facelets.
    Message was edited by:
    mjc

  • Problem deploying ADF Faces component demo to Glassfish 3.1.2

    Hi,
    Jdev 11.1.2.3
    ADF Essentials
    Glassfish 3.1.2
    Windows 7 (64-bit)
    Following the instructions on https://blogs.oracle.com/shay/entry/deploying_oracle_adf_applications_to I'm able to deploy and run a very simple ADF Faces application.
    But when I try to deploy ADF Faces component demo (rfc-dvt-demo.war) I get following error:
    [#|2012-10-17T10:06:48.541+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=27;_ThreadName=Thread-2;|
    XML-22101: (Fatal Error) DOMSource node as this type not supported.
    |#]
    [#|2012-10-17T10:06:48.541+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=27;_ThreadName=Thread-2;|
    XML-22900: (Fatal Error) An internal error condition occurred.
    |#]
    [#|2012-10-17T10:06:48.557+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=27;_ThreadName=Thread-2;|
    XML-22101: (Fatal Error) DOMSource node as this type not supported.
    |#]
    [#|2012-10-17T10:06:48.557+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=27;_ThreadName=Thread-2;|
    XML-22900: (Fatal Error) An internal error condition occurred.
    |#]
    [#|2012-10-17T10:06:48.572+0200|SEVERE|glassfish3.1.2|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=27;_ThreadName=Thread-2;|Critical error during deployment:
    com.sun.faces.config.ConfigurationException: java.util.concurrent.ExecutionException: com.sun.faces.config.ConfigurationException: Unable to parse document 'jndi:/server/faces-11.1.2.3.0/WEB-INF/dvtManagedBeans.xml': XML-22900: (Fatal Error) An internal error condition occurred.
         at com.sun.faces.config.ConfigManager.getConfigDocuments(ConfigManager.java:672)
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:322)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225)
         at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:4750)
         at com.sun.enterprise.web.WebModule.contextListenerStart(WebModule.java:550)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:5366)
         at com.sun.enterprise.web.WebModule.start(WebModule.java:498)
         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)
         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733)
         at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2018)
         at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1669)
         at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)
         at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
         at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
         at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
         at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:353)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
         at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:145)
         at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:575)
         at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:461)
         at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:389)
         at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:380)
         at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:220)
         at java.util.TimerThread.mainLoop(Timer.java:512)
         at java.util.TimerThread.run(Timer.java:462)
    Caused by: java.util.concurrent.ExecutionException: com.sun.faces.config.ConfigurationException: Unable to parse document 'jndi:/server/faces-11.1.2.3.0/WEB-INF/dvtManagedBeans.xml': XML-22900: (Fatal Error) An internal error condition occurred.
         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
         at com.sun.faces.config.ConfigManager.getConfigDocuments(ConfigManager.java:670)
         ... 31 more
    Caused by: com.sun.faces.config.ConfigurationException: Unable to parse document 'jndi:/server/faces-11.1.2.3.0/WEB-INF/dvtManagedBeans.xml': XML-22900: (Fatal Error) An internal error condition occurred.
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:920)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:865)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at com.sun.faces.config.ConfigManager.getConfigDocuments(ConfigManager.java:656)
         ... 31 more
    Caused by: javax.xml.transform.TransformerException: XML-22900: (Fatal Error) An internal error condition occurred.
         at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:915)
         at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:502)
         at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:1013)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:911)
         ... 35 more
    Caused by: javax.xml.transform.TransformerException: XML-22101: (Fatal Error) DOMSource node as this type not supported.
         at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:917)
         at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:488)
         ... 37 moreI have also tried
    - to re-create the WAR file with "platform=Glassfish" in the deployment profile but with the same result
    - to create an EAR file with "platform=Glassfish" in the deployment profile but with the same result (I have read in the ADF docs that for ADF applications deployment of WAR files only works witin EAR files)
    From my knowledge the ADF Faces Component demo should be deployable on the certified and supported version of Glassfish as it consists of ADF Essentials features only.
    Anyone already succeeded with deployment of ADF Faces demo application on Glassfish?
    regards
    Peter

    Okay, so my problem was that the URL I was using was the OC4J launch url (http://host/applicationname and my welcome-file-list was
    <welcome-file-list>
    <welcome-file>LoginPage.jsp</welcome-file>
    </welcome-file-list>
    I tried these two variations
    <welcome-file-list>
    <welcome-file>LoginPage.faces</welcome-file>
    </welcome-file-list>
    <welcome-file-list>
    <welcome-file>faces/LoginPage.jsp</welcome-file>
    </welcome-file-list>
    and neither of these worked either. (I did restart the OC4J node between each attempt.)
    I finally created an index.html file for the application with an automatic refresh content="0;URL=faces/LoginPage.jsp" and this is working.
    Should the welcome-file-list have worked? Am I doing something wrong here?
    Thanks for the help. Mark

  • ER - Problem with ADF Faces filter when running ADF Faces within a portlet

    I am attempting to get ADF Faces to run within Oracle Portal, i.e. within a portlet using the JPDK.
    This, I am sure you are about to tell me, is not something that is fully supported, as yet.
    However, I have been successful in getting MyFaces to run within a portlet, by customizing the form tag.
    MyFaces, it seems, keeps track of the current viewid by storing it in the session, then uses this within the viewhandler and navigationhandler to determine the next view to load, based on the faces-config.xml navigation entries.
    By customizing the form tag it is then possible to retrieve this viewid from the faces context and outputting it in the form's action parameter.
    It is also possible, with a few more customizations, to run JSF RI within a portlet, i.e. by adding a custom viewhandler and loading a session variable with the current viewid from the faces context, then retrieving the viewid and outputting it as the action string in the customized form tag .
    Unfortunately there does not appear to be any way of getting ADF Faces (EA19 version) to run as a portlet, with either the RI or with MyFaces.
    I have configured a basic .jspx document in the <showPage> tags of the provider.xml file.
    This uses only the form tag and a few input tags and works when executed directly within my portlet project in JDeveloper (http://localhost:8988/TestJSFAppContext/faces/htdocs/facesportlet/index.jspx) using a redirectfilter (*.jspx htdocs -> /faces/htdocs).
    It is not possible to run ADF Faces with RI as a portlet since customization of the ADF Faces ViewHandler appears not to be supported.
    When attempting to run this with MyFaces as a portlet, however, I get the following message:
    oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl verifyFilterIsInstalled
    WARNING: The AdfFacesFilter has not been installed. ADF Faces requires this filter for proper execution.
    I am having difficulty in understanding as to why this is happening but am guessing it must be something to do with either redirect URLs or due to the .jspx files being under /htdocs, i.e. the ADF Faces renderkit is checking that the ADF Faces filter is configured but the check fails since the filter does not execute.
    I have configured the filter in web.xml, as detailed in the documentation:
      <filter>
        <filter-name>adfFaces</filter-name>
        <filter-class>oracle.adf.view.faces.webapp.AdfFacesFilter</filter-class>
      </filter>
      <filter-mapping>
        <filter-name>adfFaces</filter-name>
        <servlet-name>ADF Faces Servlet</servlet-name>
      </filter-mapping>
    <servlet>
        <servlet-name>ADF Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
      </servlet>
      <servlet-mapping>
        <servlet-name>ADF Faces Servlet</servlet-name>
        <url-pattern>/faces/*</url-pattern>
      </servlet-mapping>and have modified the provider.xml file as follows:-
          <renderer class="oracle.portal.provider.v2.render.RenderManager">
             <renderContainer>true</renderContainer>
             <renderCustomize>true</renderCustomize>
             <autoRedirect>true</autoRedirect>
             <contentType>text/html</contentType>
      <showPage>/faces/htdocs/facesportlet/index.jspx</showPage>        
             <editPage>/htdocs/facesportlet/FacesportletEditPage.jsp</editPage>
             <editDefaultsPage>/htdocs/facesportlet/FacesportletEditDefaultsPage.jsp</editDefaultsPage>
          </renderer>with the following tags also set:
       <session>true</session>
       <passAllUrlParams>true</passAllUrlParams>In order to ensure that the session stays alive so that the views are retrieved.
    As I say, the page loads OK when run directly within the JPDK project within JDeveloper, with a redirect filter (*.jspx -> /faces/*.jspx) but not when run from within Oracle Portal.
    In fact I have found that this filter is very sensitive, i.e. ADF Faces will not run in any project unless the configuration is exactly as above.
    It seems that the MyFaces team have got around the problem of maintaining session state with redirections but that ADF Faces needs the page URL that is passed in to the filter to be consistent.
    Is there some way around this, i.e. some kind of customization that I can implement to get the filter working?
    Thnks

    I have found a way to go round the problem.
    I use the servlet 2.4/jsp 2.0 route and then
    change the web.xml header to the servlet 2.3/jsp 1.2
    format. Everything then works fine after this!
    Please fix this for production.
    Behnam

  • ADF 12c Rendering Problems at design time

    Hi all,
    I am experimenting the following unexpected rendering problems at Design time with JDEV 12c:
    -  Sometimes a complete page is showed empty or blank but the components exists on the page (you can see them in the structure panel) and the page has no warnings.
    -  Sometimes I cannot click a component because it is behind the container.
    -  Sometimes the containers are rendered in other place on the page.
    -  Sometimes the containers not stretching
    I remember some posts about this problem in 11.1.2.x but I think it was not fixed in 12c. For this reason, I have some questions:
    What is the "real" memory requirement  of Jdev 12c to avoid render problems?
    What is the best configuration in jdev.conf?
    Is it only a memory issue or Is it also a dependency reference problem? According to a blog post of Frank Nimphius:
    Though with Oracle JDeveloper 11g the problem of the IDE not rendering JSF pages properly in the visual editor has become rare, there always is a way for the creative to break IDE functionality. A possible reason for the visual editor in JDeveloper to break is a failed dependency reference, which often is in a custom JSF PhaseListener configured in the faces-config.xml file. To avoid this from happening, surround the code in your PhaseListener class with the following statement (for example in the afterPhase method)
    public void afterPhase(PhaseEvent phaseEvent) {   if(!ADFContext.getCurrent().isDesigntime()){ ... listener code here ... } }
    The reason why the visual editor in Oracle JDeveloper fails rendering the WYSIWYG view has to do with how the live preview is created. To produce the visual display of a view, JDeveloper actually runs the ADF Faces view in JSF, which then also invokes defined PhaseListeners. With the code above, you check whether the PhaseListener code is executed at runtime or design time.If it is executed in design time, you ignore all calls to external resources that are not available at design time.
    source:
    https://blogs.oracle.com/jdevotnharvest/entry/when_jdeveloper_ide_doesn_t
    if it is a known problem, then Why is not fixed in 12c?
    Jhon
    Jdev 12c

    Jhon, what Frank mentioned can't be fixed from the outside. You or the developers who use phase listens without thinking about the design view are the ones to fix this. Frank provided you with the solution for this.
    However, we don't know if you use any self written phase listener. If you don't do this you have another problem. I do see some of your symptoms but can't reproduce them at the moment. As long as we can't reproduce the problem somehow it's difficult to to get a solution.
    My advise is to keep your eyes open (add I do) and whenever you can reproduce this behaviour come back and tell us about it. It's hard or impossible to give the 'best' settings for Jdev.conf as they depend on other factors e.g. operating system, memory, other applications running at the same time and many more.
    Personally I don't change the parameters as long as I can't put the problems to low memory (which I can't at the moment).
    Timo

  • Step by Step Deploying ADF Faces to OC4J 10.1.2

    Hi there,
    I've already read the previous topic about deploying ADF Faces to OC4J 10.1.2.
    But I'm still getting failed to deploy it.
    Some clue that I know are:
    - Using JDK 1.4.2 (not 1.5)
    - Using J2ee 2.3 (not 2.4)
    - Using ADF Runtime installer to OC4J 10.1.2
    But i've got some problem, when I'm trying to run my project using jdk 1.4.2. It gives me an error like this:
    classloader.util.AnnotatedClassFormatError: MBeanServerEjbHome_StatefulSessionHomeWrapper1
         Invalid class: MBeanServerEjbHome_StatefulSessionHomeWrapper1
         Loader: system.root:0.0.0
         Code-Source: /D:/av/src/Jdev1013/jdev/system/oracle.j2ee.10.1.3.36.73/embedded-oc4j/application-deployments/admin_ejb/deployment-cache.jar
         Configuration: <ejb> in wrappers
         Dependent class: com.evermind.server.ejb.deployment.SessionBeanDescriptor
         Loader: oc4j:10.1.3
         Code-Source: /D:/av/src/Jdev1013/j2ee/home/lib/oc4j-internal.jar
         Configuration: &lt;code-source> in META-INF/boot.xml in D:\av\src\Jdev1013\j2ee\home\oc4j.jar
    Can anyone tell me how to deploy ADF Faces to 10.1.2 step by step?
    Thanx in advance :),
    Andre

    I have the same problem. My applications works fine with Jdev 10.1.3 but after deploying it on the application server I'm getting this error.
    Started
    adfmobile: jsp: init
    adfmobile: Started
    adfmobile: resources: init
    adfmobile: JspServlet: unable to dispatch to requested page: Exception:oracle.jsp.parse.JspParseException:
    /index.jspx: Line # 9, <jsp:output omit-xml-declaration="true" doctype-root-element="HTML" doctype-system="http://www.w3.org/TR/html4/loose.dtd"
    doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN" xmlns:jsp="http://java.sun.com/JSP/Page"/>
    Error: jsp:output is not a registered tag in that namespace.
    adfmobile: JspServlet: unable to dispatch to requested page: Exception:oracle.jsp.parse.JspParseException:
    /index.jspx: Line # 9, <jsp:output omit-xml-declaration="true" doctype-root-element="HTML" doctype-system="http://www.w3.org/TR/html4/loose.dtd"
    doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN" xmlns:jsp="http://java.sun.com/JSP/Page"/>
    Error: jsp:output is not a registered tag in that namespace.
    Any hints?
    Regards,
    Thomas

  • ADF faces logout problem

    Hi.
    I've a problem with ADF faces that I didn't had when I was using the JSF reference implementation. W're using Jboss as a container, but that has nothing to do with this.
    Basicly, the users triggers a logoff by clicking a link that leads to the "logoff" JSF page.
    This page has exactly this content, and nothing more:
    <%-- Tag libraries --%>
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ taglib uri="/WEB-INF/tlds/refdataportal.tld" prefix="r" %>
    <%
    org.mycompany.Util util = new org.mycompany.Util();
    util.logoff(request);
    response.sendRedirect("Goodbye.jsp");
    // code DOES reach this point
    %>
    The logoff function does this:
    // invalidate faces
    FacesBean.releaseContext();
    // invalidate the current session for good measure
    HttpSession session = request.getSession(false);
    if (session != null)
    session.invalidate();
    // force the old session to go to the eternal fields of session objects
    request.getSession(true);
    The redirect to Goodbye.jsp is needed to force a "JBOSS" logoff as well.
    Goodbye.jsp is a JSP page (** not ** JSF) which a simple goodbye message.
    Anyway, since using ADF I get the stacktrace shown below.
    I did try to call release() on AdfFacesContext, but that didn't help.
    Do note that we actually reach the line "// code DOES reach this point" shown in the logoff JSF page above... so the redirect() statement is executed.
    Anybody knows how to deal with this?
    Remember, it used to work perfectly fine with the reference impl.
    Regards,
    Falco Paul
    12:33:44,580 ERROR [Engine] StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw excep
    tion
    java.lang.IllegalStateException
    at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:382)
    at com.sun.faces.context.FacesContextImpl.getExternalContext(FacesContextImpl.java:110)
    at oracle.adfinternal.view.faces.context.AdfFacesPhaseListener._releaseContextIfNecessary(AdfFacesPhaseListener.
    java:129)
    at oracle.adfinternal.view.faces.context.AdfFacesPhaseListener.afterPhase(AdfFacesPhaseListener.java:60)
    at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:211)
    at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:356)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:325)
    at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:190)
    at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at com.abnamro.crd.admin.PortalFilter.doFilter(PortalFilter.java:113)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
    at java.lang.Thread.run(Thread.java:534)

    Hi!
    Unfortunally your suggestion didn't work. I did however discover that the exception is only thrown if one uses ADF faces components. There is no error message if reference implementation components are used (even if using the ADF faces renderer class).
    Anyway, this is what I trie:
    I first did a a regular faces responseComplete() call, as I figured that could be the missing action, but again I got the same exception:
    java.lang.IllegalStateException
         com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:382)
         com.sun.faces.context.FacesContextImpl.getExternalContext(FacesContextImpl.java:110)
         oracle.adfinternal.view.faces.context.AdfFacesPhaseListener._releaseContextIfNecessary(AdfFacesPhaseListener.java:129)
         oracle.adfinternal.view.faces.context.AdfFacesPhaseListener.afterPhase(AdfFacesPhaseListener.java:60)
         com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:211)
         com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:356)
         oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:325)
         oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:190)
         oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
         com.abnamro.crd.admin.PortalFilter.doFilter(PortalFilter.java:113)
         org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
    Then later I tried this actually calling the faces "sendRedirect" function shown below (that is: prior to calling the logoff() code), but again I got the same Oracle exception (see above).
    // helper method: redirect to some URL (which may be either absolute or relative)
    public synchronized static void redirect(String url)
    ExternalContext external = getExternalContext();
    if (external == null)
    return;
    try {
    external.redirect(url);
    catch (Exception e)
    e.printStackTrace();
    responseComplete();
    So... unfortunally I did still not get much further...
    Regards,
    Falco

  • ADF Faces: Changing "rendered" property in PPR: JDev 10.1.3

    Hello all,
    I have an ADF Faces page that has an af:CommandButton on it. The rendered property of the button is set to an EL expression that references the model (ADF BC). When the page is submitted (via an af:CommandButton with PartialPage=true), the rest of the page refreshes properly to reflect the changed model state, but the command button with the conditional rendered property is not disappearing as expected (the button is initially rendered=true). I remember reading recently about a similar issue if the button is initially not visible, and I'm not sure if this is related.
    Interestingly, if I click on the button (which should no longer be visible after the PPR event), it does nothing - so it appears to be merely a visual problem. I have also tried setting the disabled property to an EL expression that is the opposite of the rendered property, and the button does not change to be disabled, either.
    Any thoughts? At this point, it looks like a bug/feature.
    Kind regards,
    John
    Should I be able to do this?

    John,
    if you wrap the button in a panel (e.g. buttonpanel) and set the PPR to this panel, does it work ?
    Frank

  • Problems while deploying a JSF/ ADF Faces App to Apps Server 10.1.3.0.1

    Dear All,
    I built a JSF based application (Using ADF Faces Components) developed in JDeveloper 10.1.3.1.0 (Application Configuration: [JSF, ADF BC]. The application is running fine with the embedded OC4J intance (automatically aunch by JDeveloper).
    I am now trying to deploy it on the installed Oracle Application Server (running on the same local machine). The details of the versioning for different components in this App server are as follows:
    1. OracleAS J2EE 10.1.3.0.0
    2. Oracle ADF 10.1.3.1.0
    The deployment steps I followed (as given in Chapter 34 of 'Oracle ADF - Developer's Guide for Forms/4GL Developers') seems to be running smoothly. This is because the deploy process ends up showing no erros in the message window.
    However when I tried to test the application with a browser using the Apps Server URL (HTTP://localhost:8888/<my-app>/<firstfile.jspx>), I am finding 'Page not found error'.
    I also tried a manual deployment (using deploy to a WAR file then copy the resulting war & ear files and the xml descriptor file to the Apps server's http root) and gives the war file URL in the browser.
    In this case now I am getting the following error page:
    =====================================================
    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
    An invalid character was found in text content. Error processing resource
    'http://localhost:8888/HousingWithADF.war'.
    =====================================================
    Any idea?
    Regards,
    Irfan Ilyas
    PS: I am doubtful about creation of Deployment Descriptors step as the documentation is not very clear about exactly which descriptors we need to create. Using my own idea, I tried to create J2EE descriptor, and one tld (taglibrary) file. However, the manual war deployment generates only the tld file in the deploy folder.

    Thanks for the hint.
    OBSERVATION #1:
    After looking through the administration console for OC4J instance, I found my application name with UP status. When drill-down further, the console gives me the URL which can be used to test the application.
    While using the URL, a different error message was found:
    URL: http://localhost:8888/KFUPMHousing/
    Error:
    ====================
    HTTP 403:(Forbidden)
    ================
    You are not authorized to view this page
    You might not have permission to view this directory or page using the credentials you supplied.
    From my experience of Microsoft IIS, I know here I may need to configure the folder permissions for a web-user. But exactly which user and where it is defined (at OS Level or in AS), I am not much sure.
    Can you elaborate?
    OBSERVATION #2:
    The log text for my application shows the following error (for the attempt I did with the URL shown above)
    Log Text
    07/01/05 22:43:38.62 HousingWithADF: JspServlet: unable to dispatch to requested page: Exception:java.io.FileNotFoundException: C
    :\product\10.1.3.1\OracleAS_1\j2ee\home\applications\HousingWithADF\HousingWithADF\HosReqInfo.jspx (The system cannot find the file specified)
    However, I can browse the file on my local disk in the path specified with a little change in the path. The file is found in 'pages' folder within the last folder,named HousingWIthADF. I tried to move the file in the exact path specified in the log and now finding the 'Page not found' error.
    Any idea?
    Irfan Ilyas

  • JDeveloper Visual Editor not rendering ADF Faces

    Hi guys, thanks for read my post.
    I'm working on a MVC application, and using ADF Faces in view. I did any changes, editing my jsf pages sources.
    Now JDeveloper doesn't show the design view of no one jsf pages.
    I followed the steps enumerated by Didier Laurent in:
    http://blogs.oracle.com/Didier/2006/11/22
    (thanks Didier), but it didn't resolve the trouble.
    When i run jdev.exe instead jdevW.exe I watch the following lines:
    (digester.Digester 164) [ConverterRule]{faces-config/converter} Merge(javax.faces.Short,null)
    (digester.Digester 164) [ConverterRule]{faces-config/converter} Merge(null,java.lang.Short)
    (digester.Digester 164) [ConverterRule]{faces-config/converter} Merge(javax.faces.Byte,null)
    (digester.Digester 164) [ConverterRule]{faces-config/converter} Merge(null,java.lang.Byte)
    But I can't see the error cause,
    Have you seen this problem before?
    Thanks in advance

    Hi again, thanks for your reply Shay. I had followed this steps to, but I don't reach to get the misconfiguration or error in my faces pages for showing design time messages in log. Log is empty and if I run JDeveloper from jdev.bin I don't see more than some lines I sent before.
    Thanks

  • Problem in accessing ADF Faces Table portlet in Oracle 10.1.4 portal server

    I created one ADF Faces Portlet ,showing a simple table in 10.1.3.1
    When i do run from Jdevloper it works fine.
    But after registering it as WSRP in oracle portal server 10.1.4 ,when i am adding this portlet in a page ,it is giving javasript error.
    I am not able to figure out problem.
    Any help will be appreciated.
    Thanks in Advance....

    It is giving error in this line.
    addJSL("http://ipaddess/portal/page/portal/TEST/COMPANY/test82?mode=16&_rtarget=36_14157_36_14154_14154&_piref36_14157_36_14154_14154.__ora_type=proxy&_piref36_14157_36_14154_14154.__ora_resource=http%3A%2F%2Fisaha%3A8888%2FListAll3%2Fportletresource%2FC%253A192.168.11.162%253A-ce9ef7a%253A12214125dd4%253A-7ffe%2FS%253A192.168.11.162%253A-ce9ef7a%253A12214125dd4%253A-7ffc%253AE%253A0%253A192.168.11.162%253A-ce9ef7a%253A12214125dd4%253A-7ffd%2Fadf%2FjsLibs%2FCommon10_1_3_2_0.js"
    But instead of http:// if it is http://// It is ok.But is is generated by Portal server.
    Do I need to install any patch.
    Any help will be appreciated.
    Thanks in advance ......

  • ADF Faces components are not rendered in Jdeveloper visual editor

    Hi!
    I'm using Jdeveloper 1013 Developer Preview. I found that the components of ADF Faces EA16 are not shown on the visual editor in Jdeveloper, but the ADF Faces EA15 components are shown. I'm just wondering if this is normal, and there is anything that can be done to fix this?
    Meen

    I know there's a recent release with a visual editor problem, but I'm not sure which one it is. This thread says you need a fresh install? Can you try that?
    Re: ADF Faces tutorial/code sample for data table?

  • ADF Faces - Panel Accordion rendering issue

    Hi, I am trying to follow this tutorial about adf faces:
    http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_55/jdtut_11r2_55_2.html
    but when I click on the detail items in the accordion component, the objects inside desappears and I could see a strange rendering behavior with the rest of the objects.
    No errors are shown in the console. I tested it in chrome, ie8 and firefox with the same result.
    Software used: jdeveloper 11.1.1.6.0, weblogic 11gR1 on win7.
    Any ideas?

    You are aware that the sample is for jdev 11.1.2.x, so this may well be the reason why you see this behavior.
    Timo

Maybe you are looking for

  • How to connect a 2nd screen

    I'm going to college soon and i wanted to get some extra workspace. I wanted to maybe use my screen on my macbook and connect it together with my lcd screen from my old pc so that my mouse would go from one screen to the other but work as a unit. Wha

  • How do I get my money back for an App I bought yesterday that has crashed?

    How do I get my money back for an App I bought yesterday that has crashed?

  • Lightroom 1.2 and Camera Raw 4.2 now available

    http://blogs.adobe.com/lightroomjournal/ Regards, Tom Hogarty

  • IMovie date problems

    I uploaded some film from a camera onto iMovie and it says the date is the year 2025. I am trying to figure how to change that to the proper year. Does anybody know how? Thanks, Julien Message was edited by: Julien Witowski

  • Corrupted datafile after cloning

    Good Day I have done a restore from the production system to the test system some time ago . Today I got an error on my test system saying ORA-00376: file 375 cannot be read at this time . After checking I found that the file seems to be missing on t