ADF FACES : Document structure guidelines ?

Does a paper exists that presents the adf faces globally document structure and the possible and recommended adf faces components hierarchy.
I have seen some time ago something like that for UIX (forget where) ... is it the same one ? does this paper exists in otn ?

I'm looking for a description of the pages structure we may use in adf faces. The tree of element we can use and inside each nodes which other element we can use. Something that will help to design a standard page structure in a whole. Actually we only have elements description and it is difficult to see these elements at a whole and what are the possible combinations of elements and what are the forbidden combination of elements.
I remember i have seen some years ago in a uix document a part where the structure was graphically designed and explained. It was very helpful to understand the structure. I don't remember if this was in a white paper or a reference document.
Hope you understand what i mean
Thanks

Similar Messages

ADF faces use cases

Hi
I recently encountered this uses case wherein i had to delay the validation until commit time as outlined here
http://jobinesh.blogspot.com/2009/08/how-to-skip-validation.html
I am just wundering is there a ADF faces document that outlines such use cases and the ways to tackle them.
regards

Hrishy,
Well, there is the documentation, particularly the Fusion Developer's Guide. There's lots of blogs and articles on OTN. There's some books just out. If you have a specific question, perhaps someone can direct you with a more specific answer.
Best,
John

Can't locate ADF Faces Core tag document

I found a good ADF Faces core tag document (10g), using this URL, http://www.oracle.com/technology/products/jdev/htdocs/partners/a
ddins/exchange/jsf/doc/tagdoc/core/imageIndex.html. This reference has images for each tag component. but somehow the URL is not working anymore. Can anyone tell me why this URL is not working any more and how/where can I download the same refrence to local machine? This is for 10g.
Thanks
Jade

Unfortunately, with the recent big change to OTN, there are a lot of links whose content has moved and the links don't work.
http://webcache.googleusercontent.com/search?q=cache:bz4GyBiDfFIJ:www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/doc/tagdoc/core/imageIndex.html+http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/doc/tagdoc/core/imageIndex.html&cd=1&hl=en&ct=clnk&gl=uk is Google's cache of that site.
John

JDeveloper 11.1.2.3, ADF Faces, JQuery Integration via ADF Library

I cannot seem to get a consuming application to execute jquery's ready() function defined within a adflib application. Here is my setup
directory structure of where my javascript files are:
CommonApp
-ViewController
--public_html
---resources
----js
-----jquery-1.6.2.min.js
-----acme.js
The above structure created by default by jdev when creating a new javascript file. Now the test code (also within CommonApp) which works looks like the following:
test.jsf
<?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">
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
    <af:document title="test.jsf" id="d1">
        <af:group id="g1">
            <af:resource type="javascript" source="/resources/js/jquery-1.6.2.min.js"/>
            <af:resource type="javascript" source="/resources/js/acme.js"/>
        </af:group>
        <af:form id="f1">
         </af:form>
    </af:document>
</f:view>Contents of acme.js
$(document).ready(function () {
    // do jQuery
    alert('jquery ready called')
});OK so far so good, test.jsf runs and an alert dialog pops up. Moving on... CommonApp is deployed as an ADF Library and consumed by a ChildApp.
There is a single .jsf file within the ChildApp and the code is exactly identical to the above test.jsf. Upon runtime there is no alert dialog! What am I missing?

A bit more fiddling around:
I have added the following code to acme.js
function test() {
    alert('test');
}redeployed the adflib
Within my ChildApp I have added the following code to test.jsf:
<?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">
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
    <af:document title="test.jsf" id="d1">
        <af:group id="g1">
            <af:resource type="javascript" source="/resources/js/jquery-1.6.2.min.js"/>
            <af:resource type="javascript" source="/resources/js/acme.js"/>
        </af:group>
        <af:form id="f1">
            <af:commandButton text="commandButton 1" id="cb1">
                <af:clientListener method="test" type="click"/>
            </af:commandButton>
        </af:form>
    </af:document>When the code is ran, I clicked the button and the alert dialog is invoked.
</f:view>

ADF Faces & BC: Best pratices for project layout

Season greetings my fellow JDevelopers!
Our software group has been working with ADF for around 5 years and through the years we have accumulated a good amount of knowledge working with JDeveloper and ADF. Much of our current application structure has been resurrected in the early days of JDeveloper 10 where there were more samples codes floating around then there were "best pratice" documentation. I understand this is a subjective topic and varies site to site, but I believe there is a set of common practices our group has started to identify as critical to streamlining a development process(reusable decorated ui components, modular common biz logic, team development with svn, continuous integration/build, etc..). One of our development goals is to minimize dependency between each engineer as everyone is responsible for both client and middle layer implementation without losing coding consistency. After speaking with a couple of the aces at the last openworld, I understand much of our anticipated architectural requirements are met with JDeveloper 11(with the introduction of templates, declarative components, bounded task flows, etc..) but due to time constraints on upcoming deliverables we are still about an year away before moving on with that new release. The following is a little bit about our group/application.
JDeveloper version: 10.1.3.4
Number of developers: 7
Developer responsibilties: Build both faces & bc code
We have two applications currently in our production environments.
1.A flavor of Steve Muench's dynamic jdbc credentials login module
2.Core ADF Faces & BC application
In our Core ADF Faces application, we have the following structure:
OurApplication
     -OurApplicationLib (Common framework files)
     -OurApplicationModel (BC project)
          -src/org/ourapp/module1
          -src/org/ourapp/module2
     -OurApplicationView (Faces project)
          public_html/ourapp/module1
          public_html/ourapp/module2
          src/org/ourapp/backing/module1
          src/org/ourapp/backing/module2
          src/org/ourapp/pageDefs/
Total Number of Application Modules: 15 (Including one RootApplicationModule which references module specific AMs)
Total Number View Objects: 171
Total Number of Entities: 58
Total Number of BC Files: 1734
Total Number of JSPs: 246
Total Number of pageDefs: 236
Total Number of navigation cases in faces-config.xml: 127
Total Number of application files: 4183
Total application size: 180megs
Are there any other ways to divide up this application? Ie: module specific projects with seperate faces-config files/databindings? If so, how can these files be "hooked" together? A couple of the aces has recommended that we should separate all the entity files into its own project which make sense. Also, we are looking into the maven builds which should remove those pesky model.jpr files that constantly gets “touched”. I would to love hear how other groups are organizing their application and anything else they would like to share as an ADF best pratice.
Cheers,
Wes

After discussions over the summer/autumn by members of the ADF Methodology Group I have published an ADF Coding Standards wiki page that people may find useful:
[http://wiki.oracle.com/page/ADF+Coding+Standards]
It's aimed at ADF 11g and is intended to be a living document - if you have comments or suggestions please post them to the ADF Methodology google group ( [http://groups.google.com/group/adf-methodology?hl=en] ).

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>
          
          <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
          
          <locale-config>
               <default-locale>en</default-locale>
               <supported-locale>en</supported-locale>
          </locale-config>
          
          <message-bundle>messages</message-bundle>
          
          <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>
         
         <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>
          
          <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>
             
             <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>
     
     <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>
         
               <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>
     
     <filter-mapping>
          <filter-name>MyFacesExtensionsFilter</filter-name>
         <servlet-name>FacesServlet</servlet-name>
     </filter-mapping>
     
     <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>
     
     <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>
     
     <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>
     
     <filter>
          <filter-name>SessionTimeout Filter</filter-name>
          <filter-class>com.unyric.cias.cm.web.filter.SessionTimeoutFilter</filter-class>
          <init-param>
               
               <param-name>redirectUrl</param-name>
               <param-value>timeOut.jsp</param-value>
          </init-param>
          <init-param>
               <param-name>sessionTimeout</param-name>
               
               <param-value>20</param-value>
          </init-param>
     </filter>
     <filter-mapping>
          <filter-name>SessionTimeout Filter</filter-name>
          <url-pattern>/secure/*</url-pattern>
     </filter-mapping>
     
     <session-config>
          <session-timeout>99</session-timeout>
     </session-config>
     
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>FacesServlet security</web-resource-name>
               <url-pattern>*.do</url-pattern>
               
          </web-resource-collection>
          <web-resource-collection>
               <web-resource-name>View security</web-resource-name>
               <url-pattern>/secure/*</url-pattern>
               
          </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>
          
          
             <role-name>case</role-name>
     </security-role>
     <welcome-file-list>
          <welcome-file>index.jsp</welcome-file>
     </welcome-file-list>
     
     <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>
     
     <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

Jdeveloper 10.1.3.3.0.4157 ADF faces Do not render in visual editor

The ADF Faces Components do not display in the visual editor
The code window shows all these features present and properly coded
These components are from the ADF Faces Core page of the Component Pallete
I tried quitting and re-starting jdeveloper , to no avail
I placed an af:panelPage on h:form and typed in a title-(blank visual editor)
I placed an ObjectImage and placed it on the branding facet
I bound a logo.image to this component - (still blank visual editor)
All of this insertions into the form are recorded in the code window
but do not appear in the Visual Designer.
Using jdeveloper10.1.2.2.0.4157
JDK 1.5.0_15
windows xp professional
The example project is from the Book:
Oracle JDeveloper 10g for Forms & PL/SQL Developers

Thank you for your reply.
On jdevelper startup I get the following message:
ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
For no Reason at all,(except for starting and shutting down jdeveloper)
I am now getting a view: An Outline with tags in order , but not a simulation
of a web page???But a correct development structure with tags/values identified.
there are many libraries in the properties page , I'm a newbie so wouldn't
know if any of these would help?

EJB 3.0 / Data control binding / ADF Faces

We have a great and very useful tool to generate rich client web application. Generate web component from a data structure is easy but manage the full life cycle is a little bit more complex. This complexity is dramatically increased when tool/platform are offering many models to solve the problem.
In JDev we have three major choices:
1) adf business components
2) top link pojo
3) ejb3.0
From the client side and in my point of view (at my current understanding) the first and second choice are the easiest way to manage the persistence because they are what i say "bidirectional", that mean i will use the same data structure to persist and synchronize the database. I may only calll a method from the object to put my changes from the midle-tier into the database.
EJB 3.0 seem to be more cormplex due essentially to the presence of the session bean that acts like conversational api. I like this architecture because it is the most flexible but from my client i have to manage these api's instead of one data structure. This mean for me to catch/detect every updates, new insert or deletes in my business object and to write the corresponding code to apply to correct entity bean methods from my session bean.
Why not manage this logic in the data control framework by declaring which methods are to use as finder to get the data and which methods are to used to manage the persistence (persist, merge, remove) at object level.

Exactly what i mean
Actually Data Control architecture seem to be business object oriented with native method called from the same object to retrieve (the most part done)/synchronize the data with the database.
This is fine than your architectue don't provide a service layer like session facade.
With session facade you will access different business method to retrieve data and synchronize you data with the database not different method from the same object like application module do in adf bc.
I see two solution, the best is that you extend the data control framework to offer standard crud operation and a tools to map these with one or many methods in the same (has to be the same?this is a question of architecture, i think it has to be the same but the framework may have to permit to use an another one for flexibility) session bean. This may be the same from adf bc or top link but the method may be selected automatically by the tool (wizard).
The second solution is to build specialized sesssion bean with mandatory standardized methods and map this directly in the framework. The advantage i see is that the updates may be collected only once by the session bean by passing a specialized object manipulated by a specialized method.
In fact the best solution is something that combines mapping in the data control and a specialized set of methods in the session bean to execute a transaction in a whole at the server level.
What is to be decided if the framework (data control part) has to maintain a status for attribute (or set of attribute that correspond to a data control node) that are new inserted, updated or deleted and to synchronize only the changes.
I'm very surprising that something like that it is not already in the framework ?
How do I have to take care of changes made in a data control node object when i have used it to generate an adf faces by example in master / detail pages with an edit form like in otn examples. I see that the detail list in the detail table is updated so the data control is updated correctly by the edit form when i submit the changes but how to finally get this changes and synchronize with the database ?
ps i reply previously by mistake by email sorry ... not that the email is not exactly the same as the post here
Michel

Creation of object with sub-objects in ADF Faces

I am trying to create an object that has associated sub-objects (header/detail) using ADF Faces. The user enters the header information in an ADF Form, then he creates detail data. Example: If the object is a PO, user creates the PO header info and, in an ADF table, he creates the PO lines.
The problem is I am not able to figure how to bind the ADF table to the object that is being created. In a normal master-detail form, you drag the associated list from the Data Control palette and JDev automatically creates an accessor iterator that "feeds off" the master iterator. But, in this case, the associated list does not appear in the data control palette. Nor am I certain that is the right thing to do, anyway.
Help! This seems like it would be a common pattern.
Ara

Sorry. Here is some more information:
1. The project is for tracking duplication jobs requests.
2. Data Model--DocumentTicket and JobDocument objects are EJB 3.0 JPA objects. DocumentTicket has a getter (getJobDocuments) to retrieve a List<JobDocument> of related job documents. JobTicketManager is the session bean that encapsulates most business methods.
3. I am using ADF Faces bindings to "publish" the data model to the GUI.
4. In the GUI, I dragged/dropped the DocumentTicket constructor from the data control palette to create the document ticket. This created the appropriate method action bindings, as well as the DocumentTicketIter iterator to iterate over the constructor result.
5. Of course, the user also needs to specify the related job documents. In the GUI, I would like to have an ADF table that displays the current job documents, and a button labeled "Add Document" that is wired to a pop-up dialog. The idea is that the user clicks on the "Add Document" button, enters the information about the new JobDocument object. The object is then created and the table is updated with a new row. The table is also used to manipulate the list of job documents (chiefly, it allows the user to change their listed order).
Step 5 is where I am having trouble. I can see how to create the pop-up dialog, how to wire it to the JobDocument constructor, how to update the data model. The problem is: I do not know to which object I should wire the JobDocument table. Logically, I should be able to wire it to the jobDocumentList property. However, that is not displayed in the data control palette under the constructor results (it is displayed elsewhere; for example, under the result of the findAllDocumentTickets method).
I suppose I could create a separate finder method in the session bean, but then how do I connect it to the object being constructed (i.e., to the JobDocumentIter iterator)?
Either I am missing something here or I am hitting some limitation of the ADF binding framework.
Ara

ADF Faces - issue with Portal and af table

I wonder if anybody could help me with a problem we are experiencing with running our ADF Faces app inside a portal (NOT Oracle Portal). We are using the af table tag with the rows attribute set as follows:
<af:table emptyText="No items found"
rows="10" banding="row"
bandingInterval="1"
binding="#{backing_ModuleSearchReg.table1}"
id="table1"
var="row">
What this does is if we have more than 10 rows to display it will display
a table header that has a label 'Previous 1-10 of nnn' Next 10. However, when you click on 'Next 10' it produces a Javascript error.
When we run the app outside of the portal we do not get this problem.
I believe this is related to known issues with JSF and Javascript inside a 'framed' web page. But if anybody help me with this or point me to a resource that can help it would be very much appreciated.
Many Thanks in advance.
Chris

Hi,
I remember a similar issue with inner frames that should be fixed in JDeveloper 10.1.3.3. The problem was that the ADF Faces JavaScript did not get the correct document root.
Frank

Naming reference to an applet component in an ADF faces?

Hi,
There might be two possible way to retrieve an applet in a adf page.
One is using UIComponent.findComponent("namePath") of ADF faces. The other is use javascript with document.appletName. The applet tag has a name attribute which enables javascript to get it using document.appletName in html.
But normally if I embed an applet in an adf page, I wrap around it the <f:verbatim> tag which does not have "name" or "id" attribute. Therefore the path name to the applet will be interrupted.
Have any one try this before? should <f:verbatim> tag be ignored when the adf page rendered into html and javascript?
Thanks a lot.

Youpi!!! I found how to made it!!!
First, I finally have to make the property objReference in my
class GlowObjectReferencer as an Object in order to work.
Than, I have to pass myHB as the Object (which, if I
understand properly, will put a reference of the current Object
into the new class Object).
var _objReference:GlowObjectReferencer = new
GlowObjectReferencer (myHB, false);
And when I run my functions to manage the Glow FX
(setAllCategoryGlowOut and setCategoryGlowIn), it is now working
fine!!!
I am so happy now! I knew it was possible but in my mind, it
was just not logic to store an Object in the class but it seems
that it is what I need to do! But just to make sure: what I pass to
the class GlowObjectReferencer as the first property is only the
reference to myHB? Not a copy of myHB; right?
Again, thank Tracy because you force me to find the way to do
it!!! ;-))

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

ADF Faces - indenting text in table column.

Is there a way to indent text in an ADF Faces coreColumn component? I'm trying to represent a recursive tree structure in a CoreTable. I've tried inserting object spacers depending on the depth of each node in the tree, but Faces then wraps the text after the spacers, even when I specify no wrap for the column.
Better yet, is there a way I could do this with a tree component? I've tried separating the different levels into different collections with separate custom methods, but I don't know how to specify the master/detail relationships between them.
Any suggestions gratefully received.
Brian Spear.

Thanks, Frank. I don't think a tree table is the answer; it has the same requirements as the tree (or so I understand) with regards to populating each level from a different collection, and foreign key relationships. Not suitable for recursive relationships. Furthermore it only shows a small part of the tree at a time. I've got as far as returning a list of nodes within a structure, and I can display the structure, with icons for expanding and collapsing the nodes. All I need now is a way to indent the levels so the structure is more visible. The best I've managed so far is by inserting ". . ." in the text itself on each lower level, to make the left-justified text look indented. Obviously, I'd like a better way, that can be implemented in the view layer.
Is there maybe a way of nesting objects within an outputText component so that it doesn't wrap? Must look into that.
Thanks again.
Brian Spear.

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 FACES : Document structure guidelines ?

Similar Messages

Maybe you are looking for