ADF Faces (Trinidad?) & Facelets Support

This is long, but help and advice is very much needed.
My programming team is facing a migration from UIX to JSF (ADF Faces) for future applications and we have hit a road block in regards to a template structure that is easy to use and maintain. We had gone through official Oracle training with JSF, however the trainer's answer to templates was to "create a template and copy and paste for every new file". For our team this is unacceptable so I've been charged with figuring out how to simply templates for our team. Not only do we need to make this easy for our application developers but we need to keep it simple for web developers to create "simple" survey-like applications.
From what I've come across the answers seems to be either Facelets or Regions.
Working with Regions seem to be over-complicated, requiring too much replication (basically back to copy/pasting an entire template) or passing the panelPage's content as a java object (bad for our web developers). I presented the combinations to my team and supervisor and it was agreed that Regions are impractical for our development practices.
So it seems the answer is with Facelets. The problems I have with this is that:
1. JDeveloper doesn't appear to natively handle Facelets, or include the libraries.
2. From what I've learned, the ADF Faces library that comes with JDeveloper doesn't have Facelets support either.
3. Looking into Trinidad, Facelets support exists but there is a lack of the Oracle skin.
Facelets support is really what my team needs, as it's the closest thing to the old UIX templates I've seen so far.
I've followed instructions/examples on several posts here, but I've yet to come across an example that works. I've Googled countless pages and examples, but when it comes down to ADF Faces and Facelets, it seems I'm at a dead end.
So, can anyone help me with this?
Thanks in advance,
Rick
PS:
Using JDeveloper 10.1.3.2.0.4066 with stock ADF Faces
External libraries used:
Facelets 1.1.11
Trinidad 1.0.1-incubating

It just so happens that not long after I posted, I catch the "adf-facelets.jar" on the facelets site.
dvohra, I had seen the links you've pasted however none of them described the actual process to get it to work, it's all been segmented copy/paste instructions. This doesn't really help someone who is struggling.
So... I'll paste what my solution was, hopefully this will help others:
1. Download and install the Facelets 1.1.11 library
https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=3635&expandFolder=3635&folderID=0
2. Download and install the ADF Facelets library
https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=3990&expandFolder=3990&folderID=0
3. In web.xml add the following:
<context-param>
<param-name>oracle.adf.view.faces.ALTERNATE_VIEW_HANDLER</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
4. Make sure your project's libraries have loaded your Facelets and ADF Facelets, as well as ADF Faces Runtime.
5. Begin using UI Components as desired.
Example: http://eugeneciurana.com/pastebin/pastebin.php?show=1308
Extra notices:
I had to comment out the following in my faces-config.xml as it conflicted with the web.xml setting:
<view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
This is what worked for me, I hope this helps others out there.
Thanks,
Rick

Similar Messages

  • ADF Faces is not supported on IE running in compatibility mode

    hi
    In the blog post "Running ADF Faces applications with IE 9 in IE 8 compatibility mode "
    at https://blogs.oracle.com/jdevotnharvest/entry/running_adf_faces_applications_with_ie_9_in_ie_8_compatibility_mode
    Frank Nimphius explains about headers to make IE browsers behave like a previous version (in compatibility mode), but ends with this support information:
    Very Important(!)
    ADF Faces is not supported on IE running in compatibility mode. If using ADF Faces on IE in production, make sure IE is configured to run in native mode. Compatibility mode may only be used during development if your IE version is not certified with the JDeveloper version you work with. In production then you need to make sure the IE version matches the JDeveloper certification matrix.Reviewing the Release 1 "Certification and Support Matrix "
    at http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html#Browsers
    it currently says
    "For Internet Explorer 8 and 9, only Native mode is supported. View Compatibility mode should be disabled. "
    But there currently are no hits when searching for "compatibility" in the Release 2 "Certification and Support Matrix "
    at http://www.oracle.com/technetwork/developer-tools/jdev/jdev11gr2-cert-405181.html#Browsers
    - (q1) ADF Faces is not supported on IE running in compatibility mode, how much of that applies to JDeveloper Release 2 and where has it been documented?
    many thanks
    Jan Vervecken

    Thanks for your reply Frank.
    Frank Nimphius wrote:
    its bug 13906617 "ADD ADF FACES NOT SUPPORTED ON IE COMPATIBILITY MODE TO THE DOCUMENTATION"
    I was unable to find bug 13906617 on My Oracle Support. Has bug 13906617 been published?
    thanks
    Jan

  • ADF Faces RC browser support and browser market share

    hi
    Given the current browser support in JDeveloper 11g (ADF (Faces RC)), for IE 7.0 (not IE 6), FF 2.0, FF 3.0, ...
    http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/OJDIG.htm#BDCJBGBC
    http://www.oracle.com/technology/products/jdev/htdocs/jdeveloper11gfaq.html#P0
    (Why Oracle has chosen to do so has been discussed before, in threads ADF 11g: Browser support for Internet Explorer 6, Browser certificaion clarification JDev 11gr1, ...)
    Given some information available online about browser market share ...
    http://marketshare.hitslink.com/browser-market-share.aspx?qprid=3
    http://www.w3schools.com/browsers/browsers_stats.asp
    http://www.w3counter.com/globalstats.php
    http://www.thecounter.com/stats/
    ... it looks like about 20 to 30 percent is still Internet Explorer 6 (which is not supported by ADF Faces Rich Client components).
    Which role should this play in a decision to choose for ADF Faces Rich Client components to build an internet application today?
    Maybe some can share their experience in making such choice.
    many thanks
    Jan Vervecken

    Hi Jan,
    (e1) That's a really good example, but the deciding point is different than browser version imho.
    In that example, the hospital control its technological infrastructure so I would say it's safe to ask the users to upgrade as the hospital team is actually going to do it. In this case it depends if the hospital itself is willing to upgrade its apps, not the users. However, the patients are a special kind of users of which at least a small amount will be physically disabled to some point so you'll have to evaluate the accessibility potential of ADF Faces RC and, as most rich libraries, it's not that awesome. So, in that example, I think you would have to use pure Trinidad instead as its accessibility support is a bit better or at least reduce the usage of rich features in RC (like no drag-drop since it's a nightmare for both blind and mobility reduced users).
    (e2) imho, no it wouldn't be safe to use RC if the target date is within 1 year since you don't control the user base in that example and not supporting a browser might cut your customer base and thus reduce your revenue.
    Regards,
    ~ Simon

  • 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

  • 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 with Facelets (Menubar)

    Hello experts,
    i using ADF Faces with the jDeveloper (11.1.2) and currently i have a little problem. The menu bar is not usable when i using facelets. It seems to me that the component isn't working.
    This is my little testproject:
    http://www.axxg.de/Facelets.rar
    Thanks for your help
    Alexander

    Alexandar,
    You could have just explained your problem rather than making us download something.
    You have a few issues:
    1). You are using Facelets templating to include your content and header - however, content and header are full pages, not fragments - thus you have multiple f:view tags and af:document tags (this is why you have problems with the menu not dropping down). Have a look at ADF templates in the documentation if you'd like to see how ADF templating works.
    2) Your menus aren't set to do anything. <af:commandMenuItem text="open" id="cmi1"/> - there is no action/action listener associated with your menu item, so indeed it does nothing - this is what you will see when you fix problem #1
    John

  • ADF Faces and Facelets.

    How to use Facelets with ADF Faces I'm getting the ADF Components displayed, but the alignments are not working.And also , the JDeveloper is not recognising the <ui:insert> and <ui;composition> saying, No grammer available.
    Further , In the source for the HTML page rendered we could see the Facelets tags. these are not being converted to HTML.
    So where lies the problem?
    I added all the jar files neeed, added all web.xml entries; but could not get the correct out put.
    Can any one help me?
    Thanking you,
    Samba.

    Hi Samba,
    If you get any headway, please post it here. I am in the same boat!
    Are there other people out there using facelets with ADF? I would really appreciate any insight. Thanks!

  • ADF Faces af:table support java.util.Set

    I was using a java.util.Set in my model classes, as implementation of the Collection interface. And wanted to show the Set using a <af:table> after a while I discoverded that the documentation did not mention support of java.util.Set, only List.
    Now I have to convert my collection to List in the backing beans of my view.
    Is there a better approch than converting every Set in the view using
    new Arraylist(set)?
    And what is the reason of the missing Set support (or General Colelction support)?
    Thank you

    Deepak, I don't think you know what you're writing about.
    No, we do not support java.util.Set in <af:table>. For that matter, neither does <h:dataTable>.
    The "why" of it is that we require indexed access into the table for operations like "Display rows 526-550". java.util.Set does not offer indexed access.
    By the way, one corollary - do not use java.util.LinkedList with tables (ADF Faces or the JSF data table). If the list is small, then it won't be a problem, but with a large list, you'll get brutal performance.

  • ER's for Facelet Support, or "why facelets is a 2nd class citizen in JDev"

    Hello all,
    After an [url http://forums.oracle.com/forums/thread.jspa?threadID=873997]interesting journey getting Facelets, Trinidad, and JDeveloper 11g to play nicely together, I thought I'd post some thoughts on the sort of things that (IMHO) JDeveloper 11 needs in order to offer real, true Facelets support. I'll offer my list below, which will include observations as well as suggestions:
    1). If we are going to use true .xhtml files, JDeveloper 11g doesn't support drag-and-drop from the data control pallette on to the .xhtml page (I do have a workaround that I'll detail below, but that has its own issues).
    2). It's literally impossible to mix JSP and Facelets in a single project. As soon as you configure your project for JSP (by adding taglibs, for instance), you can no longer create a Facelets page from the "New" gallery, as JDeveloper will tell you "Cannot add a facelets page to a project configured for JSP." It works both ways, too - if you add a Facelets file to your project, no longer can you create a JSP.
    3). Even if I manually try to get data bindings (page definitions) working with .xhtml files, it doesn't seem to work (I did this by creating a jspx file and page definition and copying files / changing the data binding registry).
    4). Because ADF Faces is so intertwined with Trinidad, it would be nice if faces-config.xml and web.xml would be properly configured automatically (as an option) for Trinidad. If I manually configure faces-config.xml by ensuring the view handler is not defined there, define an alternate view handler in web.xml, and then add a new Facelets page to my project, JDeveloper undoes all my work and puts the view handler back in faces-config.xml, causing major problems.
    5). To work-around the poor support for drag-and-drop from data controls onto .xhtml files, I have just decided to use .jspx as my default suffix for Facelets files. I create them via picking "JSF Page" from the new gallery, and then I manually mess around with the source so that it's not really a JSPX anymore. However, if I do this, I don't have any tag completion support for the Facelets tags. If I download the TLD from [url https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=4190&expandFolder=4190&folderID=0]here, JDeveloper complains about not having a tag handler class.
    6). Two words: WYSIWYG Editing. There isn't any for Facelets pages. I have ADF Template envy. As soon as you configure web.xml and faces-config.xml for Facelets, all WYSIWYG is broken. Now, I know "real" coders don't use WYSIWYG, but it's sure darn nice to switch from source view and take a quick peek at the layout. For new-to-JSF/new-to-Trinidad/new-to-ADF Faces developers, it's almost a hard-and-fast necessity.
    7). Would be nice to have page definition inheritance working like for ADF Templates too.
    8). Drag-and-dropped things from the data control tend to include f:validator tags. No problems there, but the tags don't include an validatorId. Facelets needs them. I work around this manually by adding validatorId="" to each of the tags. I know there is a velocity template somewhere that JDeveloper uses for this drag-and-drop, but I cannot find them - does anyone know where they are?
    9). If, in a project with no ADF Faces - only Trinidad, if I drag-and-drop from the data control on to an ui:define tag in the structure window, I get all kinds of ADF Faces options for the drop, nothing for trinidad.
    10). Facelets < 1.1.15 has a tiny bug with the ui:debug tag (you cannot expand the component tree). It would be nice to update the one included with JDev (1.1.12) - I have done this and it appears to work fine.
    From a productivity point of view - #6, together with drag-and-drop support on to true .xhtml files (not .xhtml files with a .jspx extension) would elevate the game leaps-and-bounds.
    I'm interested in any of the following:
    a). Some wonderful news from Oracle that they already know all of these limitations and they are fixed in a patch release which was just uploaded to OTN 5 minutes ago ;)
    b). Insight on better ways of working with ADF BC / ADF Bindings / Trinidad / Facelets in JDeveloper 11
    c). Feedback and experiences from other people using Facelets in JDeveloper, particularly with ADF Data Binding.
    Depending upon the level of interest, perhaps we can migrate the discussion over to the [url http://groups.google.com/group/adf-methodology]ADF Enterprise Methodology group and produce a Wiki page out of it.
    Best regards,
    John

    Nice post John,
    Here are some of my comments on those issues:
    +1). If we are going to use true .xhtml files, JDeveloper 11g doesn't support drag-and-drop from the data control palette on to the .xhtml page (I do have a workaround that I'll detail below, but that has its own issues).+
    +3). Even if I manually try to get data bindings (page definitions) working with .xhtml files, it doesn't seem to work (I did this by creating a jspx file and page definition and copying files / changing the data binding registry).+
    I tried that a while back too because Facelets is so much more powerful than anything else to achieve high performance and powerful templating in JSF, but it's completely unsupported. I tried all possible combination of servlet-mapping aand servlet-filter-mapping. AFAIK there's no way to do it yet and Oracle will most likely delay the support of Facelets + Databindings until JSF 2.0 where there won't be much choice. If you got them working somehow in 11g, I would be very very interested in getting a small demo project.
    +2). It's literally impossible to mix JSP and Facelets in a single project. As soon as you configure your project for JSP (by adding taglibs, for instance), you can no longer create a Facelets page from the "New" gallery, as JDeveloper will tell you "Cannot add a facelets page to a project configured for JSP." It works both ways, too - if you add a Facelets file to your project, no longer can you create a JSP.+
    I can understand that one, I'm sure it comes from a a very good intention from Oracle as Facelets actually replace the JSP engine, meaning the pages don't get parsed by JSP, thus tag classes don't get called. So I assume that limitation was to prevent people from thinking that Facelets integrates with JSP while it's not at all. However, I can understand that some applications might want to leverage both technologies at the same time
    Regards,
    ~ Simon

  • [SOLVED] adf faces demo doesn't work with jdev 10.3.1.2

    Has anybody tried to run the ‘Introduction to adf faces/trinidad using jdev’ demo at
    http://www.oracle.com/technology/obe/obe1013jdev/10131/trinidad/adf_faces_trinidad.htm
    with jdev 10.1.3.2 studio?
    I am trying it and I am getting this error
    500 Internal Server Error
    java.lang.NoSuchMethodError: oracle.adf.view.faces.context.AdfFacesContextFactory.createContext(Loracle/adf/view/faces/webapp/wrapper/ContextWrapper;Loracle/adf/view/faces/webapp/wrapper/RequestWrapper;)Loracle/adf/view/faces/context/AdfFacesContext;
         at oracle.adfinternal.view.faces.webapp.AdfFacesFilterHelperImpl.startFilter(AdfFacesFilterHelperImpl.java:112)
         at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:111)
         at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:105)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
         at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.1) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
         at java.lang.Thread.run(Thread.java:595)
    Message was edited by:
    mauro avon

    We don't automatically migrate the adf-faces-api.jar since in a 10.1.3.x ADF Faces application this JAR is not part of your project's WEB-INF/lib directory.
    The issue must be specific to migrating this Apache Trinidad example.

  • ADF Faces - New components

    Hi,
    Oracle corporations has plans to incorporate new components?
    If answer is if, As and when?
    Thanks.

    Hi! Frank,
    If new Components will be added to Trinidad, then will we, the Oracle ADF faces users, be left untouched by the additions?
    if so , should we migrate to OpenSource ADF Faces/Trinidad ?
    Or will the Components addded to Trinidad , will also reflect in Oracle ADF Faces version.
    I request you to Please Clarify this,
    Thanking you,
    Samba.

  • ADF Faces - WAS 6 - AS/400

    Hi! eveyone, im new in this forum, also im a junior programmer, I had the opportunity to work with JDeveloper and ADF Faces components, so thinking to use the same tecnology but my boss told me that the servers are AS/400 and has WAS 6, so my question is, can i use ADF Faces framework under these specification?
    Thanks and have a nice day.

    THX! buy I tried to putting my .war file on WAS 6 and had problems with some libraries, but I really do not know if that failed were the ADF Faces because my file also included a connection to MySql and some jars for jasper reports, now my new question is , WAS 5.1 is too old for the ADF Framework or the only option is to use WAS 7, and how free is the framework ADF Faces Trinidad and IDE JDeveloper, I would like to know why I do not want to cause license problems in my work.
    Thanks have a good day.

  • Facelets support in ADF Rich Client

    I have tried to use ADF Rich Client with Facelets
    but it looks like the tag library schema is not recongined, and the ADF RC tag schema definition in html root tag and all ADF RC tags are copied into output.
    any comments or info from any one?

    hi,
    to add my 2 cents
    by the way do you know when will be a code drop of ADF RC available in Apache ?
    I assume this to happen some time after ADF Faces RC goes production
    1) legacy(!?) pages in one of projects we have hundreds of pages developed in facelets and it is a little hard to convert them all.
    We don't support JSF 1.1 content (and Trinidad content) to be on the same page as ADF Faces RC. So if you like to continue using your current stack then the option to go with in Trinidad in JDeveloper 11, not ADF Faces RC
    3) Templating
    ADF Rich Faces Templating mechanism is an strong one, but a little different with Facelets, for example in Facelets templates can be used inside each other but in ADF RC as far I I know they can not.
    The runtime does support template nesting, the designtime does. However, as Shay mentioned using daclarative components might be a nice addition to reuse.
    4) composition component
    in facelets it is easy make a new composite component by mixing existing components
    for example add an export to PDF and Excel button to a table.
    looks like the current ADF Templating mechanism can be used to solve this issue.
    Declarative components do.
    Frabj

  • JDeveloper 11.1.2.3, ADF Faces: declarative component does not support af:clientListener?

    I am trying to create a declarative component with the following code:
    <?xml version='1.0' encoding='UTF-8'?>
    <af:componentDef xmlns:af="http://xmlns.oracle.com/adf/faces/rich" var="attrs" componentVar="comp" definition="private"
                     xmlns:afc="http://xmlns.oracle.com/adf/faces/rich/component">
        <af:xmlContent>
            <afc:component>
                <afc:display-name>DoubleClickTableDialogClientServerListener</afc:display-name>
                <afc:component-extension>
                    <afc:component-tag-namespace>org.mskcc.crdb.common.declarativecomponent</afc:component-tag-namespace>
                    <afc:component-taglib-uri>http://www.mskcc.org</afc:component-taglib-uri>
                </afc:component-extension>
            </afc:component>
                <af:clientAttribute name="serverListenerType" value="TableDoubleClickEvent"/>
                <af:clientListener method="handleTableDoubleClick" type="dblClick"/>
                <af:serverListener type="TableDoubleClickEvent"
                                   method="#{EditAddDialogTemplateBean.handleTableDoubleClick}"/>
        </af:xmlContent>
    </af:componentDef>
    At runtime I recieve the following error:
    javax.faces.view.facelets.FaceletException: ADF_FACES-60023:Component: DoubleClickTableDialogClientServerListenerComponent[oracle.adf.view.rich.component.fragment.UIXInclude$ContextualFacesBeanWrapper@7170a7, id=dctdcsl1] does not support client listeners.
      at oracle.adfinternal.view.faces.facelets.rich.BaseClientListenerHandler.apply(BaseClientListenerHandler.java:53)
    This component was intended to be dropped off within an af:table component. I would like to hear suggestions on workarounds, one other way I thought about was to create a code template for the three tags, however, the con to this approach is each developer would need to configure this template within jdeveloper. Ideas are appreciated.
    Also a side question, how can I embed code properly with the new forum? [code] tag does not seem to work now.

    Wes, can't help with the real question, but can tell you how to format code
    Change to the advanced editor (top right over the editor field), then you get more options. The one you are looking for is behind the blue '>>'. Here you select the language you want to insert and you get nice code formatting and color.
    Timo

  • ADF faces - Facelets

    It's possible to integrate the template features of Facelets with pages containing ADF components?
    There's a HowTo anywhere?
    Thank's.
    Message was edited by:
    [email protected]

    In web.xml specify:
    <?xml version = '1.0' encoding = 'ISO-8859-1'?>
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
    Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <context-param>
    <param-name>oracle.adf.view.faces.ALTERNATE_VIEW_HANDLER</param-name>
    <param-value>com.sun.facelets.FaceletViewHandler</param-value>
    </context-param>
    <context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
    <!--param-value>server</param-value-->
    </context-param>
    <context-param>
    <param-name>facelets.REFRESH_PERIOD</param-name>
    <param-value>2</param-value>
    </context-param>
    <context-param>
    <param-name>facelets.DEVELOPMENT</param-name>
    <param-value>true</param-value>
    </context-param>
    <context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.xhtml</param-value>
    </context-param>
    <context-param>
    <param-name>facelets.VIEW_MAPPINGS</param-name>
    <param-value>*.xhtml</param-value>
    </context-param>
    <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>faces</servlet-name>
    </filter-mapping>
    <!-- Faces Servlet -->
    <servlet>
    <servlet-name>faces</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <!-- resource loader servlet -->
    <servlet>
    <servlet-name>resources</servlet-name>
    <servlet-class>oracle.adf.view.faces.webapp.ResourceServlet
    </servlet-class>
    </servlet>
    <!-- Faces Servlet Mappings -->
    <servlet-mapping>
    <servlet-name>faces</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>resources</servlet-name>
    <url-pattern>/adf/*</url-pattern>
    </servlet-mapping>
    <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
    </web-app>
    Refer
    Facelets support
    https://facelets.dev.java.net/servlets/SearchList?list=users&searchText=adf+faces&defaultField=subject&Search=Search

Maybe you are looking for