Facelets + OGNL?

I've migrated an older JSF app to Jdev 11 and run into a few problems with facelets, upgrading ADF Faces, etc.
Most recently, all calls to Backing Bean methods fail because they are not requesting objects through standard getters/setters. On page load, some of these calls return strings, sets, even through taking parameters. I believe this was originally achieved using OGNL support.
Is this correct?
How can I get these calls to work again?
Thanks for your time.

Thanks John. I understand this may be a problem, so... assuming I'm prepared to migrate it to a technology that works well and will be around for many years, what should I do from here?
It uses ADF Faces, with a Hibernate controller. Should I redesign it from the ground up with JSF?
If possible it would be nice to reuse most of the xhtml code that I have.
Two end questions:
1. What technology to use for application longevity + ease of migration? straight JSF, Facelets, Struts etc.
2. What kind of coding strategy can I use to accomplish calls like the one above? It calls a function to check a collection of permissions for a particular entity.

Similar Messages

Facelet to crare web app, instead of using JSP; JSF1.2 spec in WebSphere6.1

Novice to JSF and Facelet. But, I had been using Struts since its inception.
I am required to use IBM's WebSphere Application Server 6.1 that comes with Servlet 2.4 and JSP 2.0. WebSphere 6.1 App Server limits me to using JSF 1.1. This is because, JSF 1.2 requires Servlet 2.5 and JSP 2.1, that is a part of WebSphere App Server 7.0; not a part of WebSphere 6.1.
Somebody suggested that it will be possible to use JSF 1.2 in WebSphere 6.1, if I were using Facelet, instead of JSP.
I am not eager to use JSF 1.1 and may have to forego JSF; unless and until I can use JSF 1.2.
The hold-up is that I cannot use JSF 1.2 spec in WebSphere 6.1. Is there is any way to use JSF 1.2 in WebSphere 6.1? Can I create an entire application using Facelet (instead of JSP) that will let me use JSF 1.2 spec in WebSphere 6.1? If so, how?
Here are my questions, especially because I am not very familiar with JSF and Facelet technology:
1. Can I use JSF 1.2 specification in WebSphere 6.1, if I were using facelet (as opposed to JSP) as my view technology?
2. Will it be possible to create an entire web app with facelt, instead o fusing any JSP at all? If so, how? Does it mean that all the GUI screens will only use facelet and no JSP at all?
3. Please explain how I can write a complex web app with 100s of screens using only facelet, instead of using JSP.
4. Please provide pointer on how JSF and facelet differ, or what are their demarcations boundaries.
Any comment and pointer will be greatly appreciated.

Don't doublepost. It's rude. Stick to one topic. Continue here: [http://forums.sun.com/thread.jspa?threadID=5335001].

Facelets and jsf-extensions problem.

I'm fairly certain I've run into a problem between facelets and jsf-extensions. I'm working with JSF 1.2 RI, Woodstock, Facelets 1.1.13, on Tomcat 6.
When trying to get Woodstock autoValidation to work I get a javascript error the "I has no properties". The error occurs in the com_sun_faces_ajax.js file in the jsf-extensions-dynamic-faces-0.1.jar (I've used both the RC4 and a build today ,10/18/07 from source with the same results). Here is the code snippet where it happens (with my comment).
var I = G.getElementsByTagName("components")[0];
var C = I.getElementsByTagName("render");
for(var F = 0; F < C.length; F++) {
In the second line there it looks like the variable I is null, but based on the post response below I don't know why.
The response from the post looks like this:
<partial-response><components><render id="PayableForm:vendorGci"><markup><![CDATA[{"valid":true,"id":"PayableForm:vendorGci"}]]></markup></render></components>
However the server side code (validation method) never gets executed. I'm willing to do some digging and debug work, but I'd need to be pointed in the right direction.
The following is more potentially useful code snippets.
Here is the textField code:
<w:form id="PayableForm">
<w:textField style="display:none;" />
<w:message for="vendorGci" />
<w:label id="vendorGciLabel" for="vendorGci" text="Vendor: " />
<w:textField id="vendorGci" autoValidate="true"
text="${vendorBean.searchGci}" maxlength="8" required="true"
validatorExpression="#{ vendorBean.validateVendor}" />
Here is the javascript in the page (the init function is called from the body: onLoad="setTimeout('init();', 0);" , this does happen):
<w:script type="text/javascript">
function VendorListener(){
function VendorNotify(props){
alert("VendorNotify called!"); <--------------- I never see this alert message
if ( props.id != "PayableForm:vendorGci") { return; }
var field = document.getElementById("PayableForm:vendorGciLabel");
field.setProps({
valid: props.valid
VendorListener.prototype.notify = VendorNotify;
function initAccountRows(){
var table = document.getElementById("PayableForm:vendorAccountTable");
table.initAllRows();
function init(){
initAccountRows();
var listener = new VendorListener();
dojo.subscribe(
webui.suntheme.widget.textField.event.validation.endTopic ,
listener, listener.notify);
Here is the validator method. It currently doesn't do anything, just trying to get something to work. I never see the output, and I never hit the breakpoint in the method.
public void validateVendor(FacesContext context, UIComponent comp, Object value){
System.out.println("**********************************");
System.out.println("validateVendor called");
System.out.println(value);
System.out.println("**********************************");
}

Actually I don't need a global variable. I need to refer in my included template the actual backing bean used in the current page. As all my backing bean extends a abstract class I could bind my component to a property of the current backing bean, no matters which one. Just like a polymorphic call but without the parameter. Let's imagine I could get this object of the facesContext object I would be able to do:
<rich:datascroller renderIfSinglePage="false" align="right" for="listagem" maxPages="12" fastStep="10"
pageIndexVar="pageIndex" pagesVar="pages" stepControls="show" fastControls="hide" boundaryControls="show"
inactiveStyleClass="paginacaoInativa" selectedStyleClass="paginacaoSelecionada"
styleClass="paginacao" tableStyleClass="paginacaoTabela"
binding="#{facesContext.currentBackingbean.formDataScroller}" id="paginacao">
Instead of pass the backing bean to the ui:param of this template... Dou you get the point?

Custom Tags Using Facelets

I am trying to simplify a lot of pages by using Facelets and custom taglibs that are just .xhtml pages with other Standard JSF components inside them. My problem is not really related to that, but it gives a bit of background info: What I am trying to do is simplify the naming of binding and value attributes by trying to concatenate Strings to form a reference to a managed bean/property.
I am trying to do something like this:
<c:set var="componentVal" value="'#{formBinding}.#{formName}.#{componentName}'" />
<c:set var="componentBind" value="'#{beanBinding}.#{formName}.#{componentName}'" />
<h:inputText id="#{id}" value="#{componentVal}" binding="#{componentBind}" size="#{size}" />This comes after iterations of trying to just concatenate the bound variables (formBinding, formName, and componentName are defined earlier). Is this possible in JSF or am I barking up the wrong tree? I am trying to use this solution because we have one session-bound managed bean with different components for different tabs on the screen, and are accessed via a map, which makes the names quite long, and they only give us 17" monitors here, so, aside from making it cleaner, I will actually get to see what I am doing without scrolling all over the place.
Thanks for any and all help/advice.

I guess I could try some createobject code to see if it works on godaddy
Would you be able to post some example code?
Sure. Here is a simple test. If by some miracle that actually runs without error, you can find a .NET example in the documentation
<cfset str = createObject("java", "java.lang.String").init("Test this")>
<cfoutput>#str#</cfoutput>
Also, find out what version of CF you are using. If it is CF8+ you are in business.
<cfoutput>
version #server.coldFUsion.ProductVersion#
</cfoutput>

Error 500--Internal Server Error when running Facelet in Local Server

Hi Experts,
I have installed M2E plugin for eclipse and working on a Maven project in OEPE 12c.
Running the facelet on the remote server , the results are returned, wheras running the facelet in the local server , the below error occurs
Error 500--Internal Server Error
com.sun.faces.context.FacesFileNotFoundException: /showModule.xhtml Not Found in ExternalContext as a Resource
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:232)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:273)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.getMetadataFacelet(DefaultFaceletFactory.java:209)
at com.sun.faces.application.view.ViewMetadataImpl.createMetadataView(ViewMetadataImpl.java:114)
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:233)
Could anybody share some pointers?
Thanks,
Vijaya

I created the showModule.xhtml in the web.view.module\src\main\resources folder and test the application and Now I'm getting the error in both deployment ways.
a) Local deployment: Same result
Error 500--Internal Server Error
com.sun.faces.context.FacesFileNotFoundException: /showModule.xhtml Not Found in ExternalContext as a Resource
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:232)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:273)
b) Remote server:
Error 500--Internal Server Error
com.sun.faces.context.FacesFileNotFoundException: /showModule.xhtml Not Found in ExternalContext as a Resource
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:232)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:273)
Please check the below screenshots for the mappings captured in the properties window.
http://imageshack.us/photo/my-images/5/srwebviewmodule.png/
http://imageshack.us/photo/my-images/811/eclipseexplorer.png/
http://imageshack.us/photo/my-images/521/cdiandrichfacesear.png/
http://imageshack.us/photo/my-images/90/cdiandrichfaces.png/
Thanks,
Vijaya

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

Facelets - any ideas on how to output XML (text/xml)?

Hello there,
Instead of putting out an xhtml file I plainly wish to output an XML file.
First of all, is it possible or even necessary to develop a special extension aside from the .xhtml for these types of files. If so then is there a common standard being used such as *.xxml or should I just make something up.
Secondly, I simply want my client to receive the page with the content-type header of "text/xml".
Please keep in mind, I'm looking for a very simple example or suggestion(s)/references.
thanks in advance.

According to the latter there is an answer in the Facelets FAQ:
http://wiki.java.net/bin/view/Projects/FaceletsFAQ#How_do_I_change_the_response_con
And according to the file extension question, I don't think there is any standard, why don't you use .xml extension?

Working with taglibs in jdev 10.1.3.4 (to be used for facelets)

Short question:
How do I get the jdeveloper to accept this declaration: <%@taglib uri="http://java.sun.com/jsf/facelets" prefix="ui"%> and its elements, such as <ui:include> ?
Full story:
I've been trying to get facelets to work in a project I'm working on. A part of this project, which I have no control over, is automatic javascript insertion via xslt, which makes it impossible for me to use xml style documents. (due to '<'>' being used for comparison, rather than tag opening/closing. Having said that, here's my problem:
I want to use jsf / facelets to create a template page, that will be used in about 30 other pages. If I was able to use an xml-style jsp docuement, I could add an xmlns:ui, and faces support would work. However, since the above is true, I have to define the taglib in jsp style, to be able to use facelets. This would look something like:
<blockquote>
<%@taglib uri="http://java.sun.com/jsf/facelets" prefix="ui"%>
</blockquote>
Upon doing this, jdeveloper tells me that
<blockquote>
Error(7): "http://java.sun.com/jsf/facelets" is not a registered TLD namespace
</blockquote>
and for any uses thereof:
<blockquote>
Error(33): ui:include is not a registered tag in that namespace.
</blockquote>
After I add the jsf-facelets.jar library (tried versions 1.0.1.14, 1.1.11, 1.1.14), nothing changes.
I understand that Jdeveloper wants to validate the taglibs I define, but there is no tld in the jsf distribution and there also should be no need for this (in xml-style syntax, it works fine without validation).
If there's any way I can skip this validation or make jdeveloper believe the library is valid, I'm done. However, I have not been able to find such a function.
Some guy from exadel has uploaded a tld for facelets to the facelets project (it's under contrib, here ). This tld has been referenced in most threads that deal with the problem (jsf in jdeveloper). The tld can't however provide a structural solution, since it's not complete. The <tag-class> and <tei-class> tags within the tld are empty. Reason enough for jdeveloper to halt on it.
Adding the library to jdeveloper would be done thus: go to tools, go to 'manage libraries', go to 'tag libraries' click 'user' and select 'new'. Browse your way trough your filesystem and locate the tld file. Add a reference to the jsf-facelets and a reference to the el-api and el-impl jars and click ok. Then go to project properties and under tag lib libraries, add this library.
Jdeveloper responds to this with the following error:
<blockquote>
Error(33): Unable to instantiate tag: ui:include (class: null) Make sure that the tag class is available and that the tag library containing the class is not excluded from this application.
</blockquote>
Right. To be able to instantiate the tag, jdeveloper seems to not only need the description of the tag, but also the connection to the real thing. I've been exploring the jsf-facelets jar and came to the conclusion that the tags in the tld correspond to the classes in the 'com.sun.facelets.tag.ui.' package, so for ui:include, that would be 'com.sun.facelets.tag.ui.IncludeHandler'.This class, described here here, seems indeed to have the same attributes as our ui:include tag. Tag tei-tag (tag extra information), is, afaik, not mandatory, so I'll leave it empty. Rebuild in developer gave me lots of errors when I did it the first time (which I solved by filling in the other tag-classes), but when recreating it for this topic, I had no problems of that sort. The error I'm stuck with is:
<blockquote>
Error(33): src is not a property of com.sun.facelets.tag.ui.IncludeHandler
</blockquote>
I'm baffled by this statement. The tld says this property exists, the ui:include documentation agrees with me and the file I'm linking to has a src TagAttribute (for which I'm having trouble finding the setter, but it worked in the xml-style version). Using this tld Jdeveloper grants content assistance, which suggests to me that I should use the src tag. It is mandatory.
I tried to fill in the <tei-class>'es, but the facelets jar contains no class (that extends from) tagExtraInfo, as far as I could see. Using the one from jsf (facelets are, in a manner, jsf tags, being just a viewHandler for jsf), didn't change anything.
At this point, I'm stumped. I hope there is either
- a way to disable the tld resolution feature
- a way to make a change in the tld I have now and make jdeveloper parse this tld
- a way to create some dummy tld that jdeveloper will accept
<blockquote>
Error(33): src is not a property of com.sun.facelets.tag.ui.IncludeHandler
</blockquote>
How can I get rid of this error? Thanks for any suggestions!
edit: fixed some typos and messed-up links on 04-Nov-2008 04:35
Edited by: user2103934 on 04-Nov-2008 06:07

Opon further expirimentation, I've discovered that the facelets view handler can not handle the <%@ taglib > declaration, returning me an
com.sun.facelets.FaceletException: Error Parsing /mapviewer.jsp: Error Traced[line: 3] <Line 3, Column 2>: XML-20201: (Fatal Error) Expected name intead of %.
With the facelets handler off, the non-xml facelet declaration is handled fine, but is no help.
Which means I'm bound to use the xml style for facelets, which means I'm going to have to catch the inserted javascript in some manner.
In any case, the original question in this topic is not the problem anymore, so I closed it here and awarded 5 points for a helpful answer.
Edited by: rjonkman on 05-Nov-2008 07:17

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

Loading Facelets via ResourceHandler

Hi there,
can anyone tell me what's the main difference between JSF 2.0/2.1 and JSF 2.2 regarding to "Loading Facelets via ResourceHandler".
I searched many articles and discussions and regarding to Flows and reosource library contracts there are some thinks that are not really clear to me and might be still in discussion
In my opinion facelets and resources are loaded the same way now. The loading mechanism is unified now. But what does this mean.
Are Resources within the Facelets or Views are loaded relative to their path now ?
E.g. a view located in /x/y/z/view.xhtml will load its resources from /x/y/z/css/style.css when using <link type="text/css" href=css/style.css"/> and not from the resources folder ?!
It would be very helpful for me if anyone could provide a simple example or a link where i can the right information, because it's one of the 6 big ticket features ed burns is mentioning in every article and presentation i saw, but the background is not completly clear for me :-/
Thanks in advance!
Kind regards,
Jannis
Edited by: 988043 on Feb 14, 2013 1:49 AM

Tank you Eddy, but it seems it does not work.
The error message received from DTW is:
- <BOM>
- <BOM>
- <BO>
- <AdmInfo>
<Object>66</Object>
<Version>2</Version>
</AdmInfo>
- <ProductTrees>
- <row>
<TreeCode>A00001</TreeCode>
<Quantity>1</Quantity>
<TreeType>iProductionTree</TreeType>
</row>
</ProductTrees>
- <ProductTrees_Lines>
- <row>
<Currency>USD</Currency>
<IssueMethod>im_Backflush</IssueMethod>
<ItemCode>A00006</ItemCode>
<Price>160</Price>
<PriceList>1</PriceList>
<Quantity>3</Quantity>
<Warehouse>01</Warehouse>
</row>
- <row>
<Currency>USD</Currency>
<IssueMethod>im_Backflush</IssueMethod>
<ItemCode>S10002</ItemCode>
<Price>160</Price>
<PriceList>1</PriceList>
<Quantity>3</Quantity>
<Warehouse>01</Warehouse>
</row>
</ProductTrees_Lines>
</BO>
</BOM>
<ErrorMessage>A00001 - Errore definito dall'applicazione o dall'oggetto</ErrorMessage>
</BOM>

Error messages in included facelets file?

I have a jsp page that includes a .xhtml facelets page. The facelets page has a form, when the form is submitted I look for errors and if I find any I return the user back to the containing jsp page. At which point none of the error messages I have set display! Any ideas why that is? If I run it outside of the jsp file and return the user back to the .xhtml page it works fine. Sadly I need to have it work as a jsp include in order to interoperate with the rest of our sites technology. Any thoughts?

Hi "Basis Learner",
1. Oracle 8.1.7 is out of date! It's not maintained anymore.
2. You don't need SQL to tell how many enqueue resources have been used here. The message is clear: 8000. The current maximum. Not a single one more and no less.
3. Well how many more you'll need is hard to tell. But oviously more. Try with plus 50% -> 12000.
Since the process that died here had been a paralle query server process, it may also be the case, that you've configured too many parallel servers. As they run at the same time (parallel) they'll make use of enqueues at the very same time...
4. Of course there are notes:
398927 - ORA error as the dimensions of the parameters are too small
745639 - FAQ: Oracle enqueues
632427 - Oracle 8.1.7* database parameterization for BW
Hope that helps.
KR Lars

How to include javascript resources in Facelet tag library

I've been trying out Duncans watermark behavior tag (https://blogs.oracle.com/groundside/entry/placeholder_watermarks_with_adf_11). Indeed a great article and the example work perfectly when the tag library is included within the project and when the javascript resource (common.js) file is added to the document using af:resource tag.
I would like to create a deployable tag library, including a setWatermarkBehavior tag, for reuse in various apps. I'm able to create and deploy the tag library as a ADF library and include it for use in an application. But on runtime, the pages are not able to find the "addWatermarkBehavior" method, which I hoped automatically got loaded from the javascript file defined in the tag library jar. In the tag library file, I've added a "adf-js-features.xml" in META-INF. This file and the .js file is included in the ADF library jar. "adf-js-features.xml" looks like this:
<adf-js-features xmlns="http://xmlns.oracle.com/adf/faces/feature">
<features xmlns="http://xmlns.oracle.com/adf/faces/feature">
<feature>
<feature-name>adfExtTaglib</feature-name>
<feature-class>com/cgi/adf/ext/taglib/js/adfExtTaglib.js</feature-class>
</feature>
</features>
</adf-js-features>
I'm not sure, what value should be used for "feature-name" - I've tried many different "meaningful" names. I presume, that the ADF framework, should automatically discover all "adf-js-features" files and automatically load js-file on pages, which are using tags from the particular tag library. But apparently I'm missing something. In the facelets page used for testing, I have these few components.
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
xmlns:adfext="http://xmlns.cgi.com/adf/ext">
<af:document title="testAdfExtTaglib" id="d1">

<af:form id="f1">
<af:inputText label="Label 1" id="it1">
<adfext:setWatermarkBehavior value="CHR-Nr"/>
</af:inputText>
</af:form>
</af:document>
</f:view>
Doing some debugging, I can confirm that the "getScript" method of the setWatermarkBehavior class is called. I can also find the javascript produced by the "getScript" method in the DOM. But I cannot find anywhere in the DOM, where the javascript file from the tag library is loaded.
Please, help me out?
Edited by: wmjaboj on 2012-09-23 23:58

The Javascript source URI has the value "RES_NOT_FOUND".
If I try to access it using ".../faces/javax.faces.resource/javascript.js?ln=js" I get a blank page (contains a Html and Body only).
If I try to access it using ".../faces/resources/js/javascript.js" I can download the javascript file from the taglib.
If I manually copy the javascript.js file from the taglib into the enclosing project and save it in "resource/js", then the javascript source URI is resolved correctly to ".../faces/javax.faces.resource/javascript.js?ln=js" and I can downloaded it, but then it is the local copy and not the one from the taglib jar.
Do I need some specific configuration in web.xml or other deployment descriptors, to be able to use "javax.faces.resource"?
The only configurations whoch smells like "javax.faces.resource" is this context param: javax.faces.FACELETS_RESOURCE_RESOLVER=oracle.adfinternal.view.faces.facelets.rich.AdfFaceletsResourceResolver
In web.xml various "resource" servlets is defined (I'm not sure whether I need them, JDeveloper has created them automatically):
a) resources = org.apache.myfaces.trinidad.webapp.ResourceServlet, maps to: /adf/*, /afr/*, /bi/*
b) adflibResources = oracle.adf.library.webapp.ResourceServlet, maps to: /adflib/*
I appreciate your help.

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

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

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

Integrating a legacy custom tag with facelets webapp

Hi
I have an external custom tag ( a handler that had extended javax.servlet.jsp.tagext.TagSupport ). I am trying to use that custom tag in my .xhtml file(mine is facelets webapp). Please see the xhtml content below
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:tGrid="http://java.pershing.com/tGrid">
<tGrid:gridFields viewname="view1" isDefault="true" fields="Symbol,Quantity,Security Description,Account Type"/>
</html>
The problem here, the tag handler class is not getting invoked, i do not get the HTML content from it.
I understand like we need to add 'taglib.xml' file as below, and register as config files in servlet context param.
<tag>
<tag-name>gridFields </tag-name>
<handler-class>
xyz.Grid
</handler-class>
</tag>
I have collected the attributes and kept as TagAttribute in Grid handler class..
But how could i invoke the custom handler class that had implemented TagSupport and start its own life cycle.
Please help me out.
Thanks
-vijay

Okay. so we cannot use any legacy custom tags and we need to duplicate the code into a new facelets handler class and add into tablig.xml file. is my understanding correct.?
By the way, JSTL tags like <c:out> <c:if> are being identified by facelets view handler. How this cud have been supported by it?
Thanks
-vijay

Facelets + OGNL?

Similar Messages

Maybe you are looking for