JSF page rendered propert

Hi all,
How to make reference either AmImpl method or VORowImpl method to the JSF page rendered property??
thanks
santosh

You can NOT directly use the method reference in the page.
Instead do the following
- Add the exposed method to the PageDef
- Have a boolean property in the managed bean that returns the value by invoking the method
- For any UI component's rendered property, use EL expression based on boolean property in the managed bean.
Thanks,
Navaneeth

Similar Messages

NoClassDefFoundError running jsf page rendering datacontrol return value

Hi all,
For a fusion web application, I have created a java file and converted it to a data control .The file has the code to establish the connection to an external SES endpoint and fetching the results.Dragged the return value to a jsf page part of a bounded task flow. The project has the Oracle SOAP jar in the classpath.Still when I run the jsf page ,I get the java.lang.NoClassDefFoundError: oracle/soap/transport/http/OracleSOAPHTTPConnection exception in the console.Any ideas.
Thanks
Regards
Deepak

I guess I wondering whether issue lies with
1. a "com.sun.faces.util.DebugUtil" that doesn't perform correctly...
OR,
2. a "rule" that says the component tree will not support multiple panelGrids on the same page.
[For whatever reason, in the above example, "DebugUtil" does not appear to "see" the "id's" of the last panelGrid (i.e., id="panelGrid3"), component or its nested component (i.e., id="panelGroup3" )]
NOTE: I have neither been successful in referencing "panelGrid3" and "panelGroup3" using "FacesContext.getCurrentInstance().findComponet("panelGrid3") and "FacesContext.getCurrentInstance().findComponet("panelGroup3"), respectively.
Could someone let me know? (My apologies if the answer is obvious ... I admit I am relatively new to JSF.)
Thanks again!!!

ADF-JSF Page rendering Twice

Hi,
I have a JSF page with 5 command links, Each link takes me to a different page(.jspx), based on the "action" attribute of the command link.
For some reason on clicking on one Link, the contents of the Page are being displayed Twice.
Can anyone help, why is it so and how can i avoid the diaplying of the contents Twice.
Thanks
Vishnu

Hi,
its not clear what you mean with "content appears twice". How likely is it that the problem is within your code as you don't mention what you did. If possible, provide a step by step reproducable testcase
Frank

JSF page rendering

In my application, i am rendering the jsff pages by using ADF regions. I am on page A(a jsff page), from where i go to page B(another jsff page). when the page B is loaded first time all the getters and setters for components(buttons,input box, buttons etc) are been called in the managed bean. On page B i have a back button which send control back to page A.
when the page B is loaded for the 2nd time, i can not see any of the getters and setters been called in managed bean.
Can someone help me on this?

I added the mentioned lines of code in my adfc-config.xml.
Still the getters and setters are not being called while the page is being loaded.
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<adf-config xmlns="http://xmlns.oracle.com/adf/config">
    <adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
      <caching-rules xmlns="http://xmlns.oracle.com/adf/faces/rich/acf">
        <caching-rule id="cache-rule1">
          <cache>false</cache>
          <agent-caching>false</agent-caching>
        </caching-rule>
      </caching-rules>
    </adf-faces-config>
</adf-config>
<task-flow-definition id="accountSummaryTaskflow">
<Rest of the taskflows>
</adfc-config>
please guide whats wrong here

New View Columns are Blank on Rendered JSF Page

In an existing application, I am trying to add a few columns to an ADF Read-Only Table on an existing jsf page. In the model project, I added the columns to the read-only view object by changing the SQL statement. I then tested the business layer changes in the BC tester and the view works as I expected it to. I opened the affected jsf page in the ViewController, and tried to add the columns by copying the last column in the table repeatedly and just changing the sortable and headerText properties of the af:column objects and the text property of the af:outputText objects to values representing the new columns. Upon testing the page, the new columns appeared in the table but they where empty. No headers, no data. I then tried deleting the entire table and creating a new one by dragging the view back onto the page and selecting Create -> Tables -> ADF Read-only Table.... In the dialog I selected all the fields of interest and the new table appeared on the design view of the page. Running this version of the page gave me the same results as manually adding rows.
What am I doing wrong? Is there something I need to do to the pagedef file? Is there another file that is "out of sync" with my jspx and pageDef files? I have been away from ADF for several months and I thought I covered all my bases.
Thanks,
Jeff

Jeff,
Your first scenario should work. What you need to do after copying the columns and changing all of the properties - go into the page definition, find the binding for the iterator upon which the table is based, double-click it, then you need to use the shuttle to add the new VO fields.
Should work like that.
John

JSF page not rendered in Design View (JDev 11.1.2.1.0)

Hi!
Recently strange behavior in JDeveloper 11.1.2.1.0) begins: JSF pages in some projects are not rendered anymore. We enabled "Show Design time Messages in log" in JDev Tools/Preferences/JSP and HTML Visual editor and message
WARNING: A problem was encountered executing the page. Using fallback rendering is shown in log. This is visible on this snapshot:
[http://dl.dropbox.com/u/14304804/design_view_problem.jpg|http://dl.dropbox.com/u/14304804/design_view_problem.jpg]
What is common to all of the projects with this issue is that we run "Remove ADF Security Configuration" which was enabled before and we implemented our custom security using phase-listener.
Any idea what is wrong here?
Regards,
Sašo
Edited by: Sašo C. on May 21, 2012 2:24 PM

It's a limitation, if you will, of the way JDeveloper works. It essentially runs your JSF page in order to get the rendering. At design time, the phase listener is obviously messing things up since you're not in a proper secured environment - hence the workaround to bypass your phase listener at design time.

Jsf page not rendering in Jdeveloper

Hello. I am using jdeveloper 11.1.2.2. I was working on an application this evening, and added a new jsff page. When I opened the page, I got the "waiting for designer to render" then it stopped, and all I see is white.
I am able to add components to the page via the structure window, but I cannot see what the form looks like in the design view. The the problem started hitting the other jspx form I have in the application.
I read somewhere about someone having the same problem and I tried renaming the windowinglayout.xml, and re-opened jdeveloper, but it did not solve the problem.
This has happened before. I wiped out the system directory, and that works, but wiping out the system directory is painful. Are there any intelligent solutions?
Thank you,
Stuart

I tried renaming the system directory, opening jdeveloper, opening the jsf page -- it rendered. So I then went to the system directory and found the windowinglayout.xml and backed it up.
then I deleted out the new system directory, and the renamed back the old system directory. Found the windowinglayout.xml and replaced it with the good file.
Opened Jdeveloper and the jsf page. Did some work and soon the render failed again.
I am not sure if this is relevant...but the log shows this:
Oct 16, 2012 9:47:44 PM oracle.security.jps.util.JpsUtil disableAudit
INFO: JpsUtil: isAuditDisabled set to true
Oct 16, 2012 9:47:56 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra 2.0.9 (SNAPSHOT 20120202) for context ''
Oct 16, 2012 9:47:58 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFO: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
Oct 16, 2012 9:47:59 PM org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl _checkTimestamp
WARNING: Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION property in WEB-INF/web.xml
Oct 16, 2012 9:47:59 PM oracle.adfinternal.view.faces.lifecycle.LifecycleImpl _initializeTrinidadFrameBustingAppMapValue
WARNING: The framebusting context param 'oracle.adf.view.rich.security.FRAME_BUSTING' has been deprecated. Please change your web.xml to use 'org.apache.myfaces.trinidad.security.FRAME_BUSTING' instead. The legal values are 'always', 'never', and 'differentOrigin'. If you were setting the value of 'oracle.adf.view.rich.security.FRAME_BUSTING' to 'differentDomain', then please note that you should set 'org.apache.myfaces.trinidad.security.FRAME_BUSTING' to 'differentOrigin'.
Oct 16, 2012 9:48:01 PM org.apache.myfaces.trinidad.component.UIXEditableValue _isBeanValidationAvailable
WARNING: A Bean Validation provider is not present, therefore bean validation is disabled
Oct 16, 2012 9:48:20 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Oct 16, 2012 9:48:20 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Oct 16, 2012 9:50:11 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra 2.0.9 (SNAPSHOT 20120202) for context ''
Oct 16, 2012 9:50:12 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFO: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
Oct 16, 2012 9:50:14 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Oct 16, 2012 9:50:14 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Oct 16, 2012 9:50:15 PM org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl _checkTimestamp
WARNING: Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION property in WEB-INF/web.xml
Oct 16, 2012 9:50:15 PM oracle.adfinternal.view.faces.lifecycle.LifecycleImpl _initializeTrinidadFrameBustingAppMapValue
WARNING: The framebusting context param 'oracle.adf.view.rich.security.FRAME_BUSTING' has been deprecated. Since there is a non-null value for the context param 'org.apache.myfaces.trinidad.security.FRAME_BUSTING' the value of 'oracle.adf.view.rich.security.FRAME_BUSTING' will be ignored. Please remove 'oracle.adf.view.rich.security.FRAME_BUSTING' from the web.xml.
Oct 16, 2012 9:50:18 PM org.apache.myfaces.trinidad.component.UIXEditableValue _isBeanValidationAvailable
WARNING: A Bean Validation provider is not present, therefore bean validation is disabled

Forbiding rendering html and body elements within jsf page

Hi, I have noticed rendered JSF page always starts and ends with elements
<html> <body>
my content
</body> </html>
but I need page that contains only "my content" for inserting into live html document
It can be this automatic elements rendering disabled??

f:subview instead of f:view did no changes. output is also closed with standards elements:
<html><head><title></title></head><body>CONTENT</body></html>
but I need in output only "CONTENT" without "body" and so

Getting style missing errors while rendering ADF trees in JSF page

I am getting the following message while rendering a JSF page with af:tree. Based on other posts on this forum, I verified servlet-mapping in web.xml and it is already set to /faces/*.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Here is my JSF code snippet.
<f:view><af:document title="DeviceTree2.jsf" id="d1">
<af:messages id="m1"/>
<af:form id="f1">
<af:tree value="#{bindings.Device1.treeModel}" var="node" selectionListener="#{bindings.Device1.treeModel.makeCurrent}" rowSelection="single" id="t1">
<f:facet name="nodeStamp"><af:outputText value="#{node}" id="ot1"/>
</f:facet>
</af:tree>
</af:form>
</af:document>
</f:view>
Surely I am missing something here but not sure on the real issue.
Would appreciate if someone can help on this.

I am getting the following error. Browser shows the JSF XML code listed in my original issue statement followed by this error.
"This XML file does not appear to have any style information associated with it. The document tree is shown below."

Controlling page setup properties from JSF page

Hi there :)
How to control print properties like size,margins on left,right,top,bottom,header,footer etc in page setup through jsf page?
Thanks in advance.
Cheers.

Not.

How to get rendered JSF page (send it as HTML email)

Hello,
I would like to send notification email in my application. Could you please help me to find a way how to get HTML result of JSF page as string-file-stream. Simply anything I could handle and use it as email body or attachment.
My use case: User click to button (raise a action) which change something in DB and confirmation.xhtml(.jsf) is shown to him to confirm that this action was succesful. And I would like to send notification email to all other users with this page (simplified version).
I need a something like String getJsfPage(String url) but I could not find anything in JSF API.
Thanks for any clue.

quote gimbal2: +...now write the code to generate the email body...+
Thanks for reply...
Is that mean that I could not use already written code (confirmation.xhtml)? The beuty on JSF is that JSF parser take care about CSS styles, EL, templating (ui: ...), ... When anybody (administrators) wants to change how this email looks - just change this XHTML file.
How should I write email body? I thought about several way but nothing what looks good:
- I really dont want to use StringBuilder do build HTML.
- I dont want to write my own parser of .xhtml template (confirmation.xhtml).
- Write HTML (xml) template and parse it with XSLT transformation seems to me acceptable but complicated. Needs a special library to perform XSLT, complicated template service (future changes)
- JSP page, more-or-less the same problems like JSF page
The sad is that this email (html) body is quite small but highly dynamic (css, language of texts, logos...).

JSF: partial page rendering is causing memory leak leading to outofmemory

JDeveloper 10.1.3.2.0
JDK: 1.6.0_06
Operating System: Windows XP.
I test my application for memory leaks. For that purpose, I use jconsole to monitor java heap space. I have an edit page that has two dependent list components. One displays all countries and the other displays cities of the selected country.
I noticed java heap space keeps growing as I change country from country list.
I run garbage collection and memory usage does not go down. If I keep changing the province for 5 minutes, then I hit a java heap space outofmemory exception.
To narrow down the problem, I removed the second city component and the problem still exists.
To narrow it down further, I removed autosubmit attribute from the country component and then memory usage stopped increasing as I change country.
country/city partial page rendering is just an example. I am able to reproduce the same problem on every page where i use partial page rendering. My conclusion is PPR is causing memory leak or at least the autosubmit attribute.
This is really bad. Anyone out there experienced same issue. Any help/advice is highly appreciated !!
Thanks
<af:panelLabelAndMessage
inlineStyle="font-weight:bold;"
label="Country:"
tip=" "
showRequired="true"
for="CountryId">
<af:selectOneChoice id="CountryId"
               valuePassThru="true"
               value="#{bindings.CountryId.inputValue}"
               autoSubmit="true"
               inlineStyle="width:221px"
               simple="true">
     <af:forEach var="item"
          items="#{bindings.CountriesListIterator.allRowsInRange}">
     <af:selectItem value="#{item.countryId}"
               label="#{item.countryName}"/>
     </af:forEach>
</af:selectOneChoice>
</af:panelLabelAndMessage>
<af:panelLabelAndMessage
inlineStyle="font-weight:bold;"
label="City:"
tip=" "
showRequired="true"
for="CityId">
<af:selectOneChoice id="CityId"
               valuePassThru="true"
               value="#{bindings.CityId.inputValue}"
               partialTriggers="CountryId"
               autoSubmit="true"
               inlineStyle="width:221px"
               unselectedLabel="--Select City--"
               simple="true">
     <f:selectItems value="#{backing_CountryCityBean.citiesSelectItems}"/>
</af:selectOneChoice>
</af:panelLabelAndMessage>

Samsam,
I haven't seen this problem myself, no.
To clarify - are you seeing this behaviour when running your app in JDeveloper, or when running in an application server? If in JDeveloper, a copuple of suggestions:
* (may not matter, but...) It's not supported to run JDev 10g with JDK 6
* have you tried the [url http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk11.html]memory profiler
Best,
John

Conditional rendering of JSF page depending on Navigation case

Hi
Can we conditionally render the JSF page depending the navigation case, which brought us in that page..
Lets say that a page A does both Edit and create operations , we have two navigation cases "edit" and "create" directing to this page from main page. can we modify the components in the page depending on the navigation case.
Thanks in advance
Pradeep

Hi Grant,
your reply was helpful. i got into another scenario :-) where i need to know the navigation case which brought us into the page.
I have a page flow in adf which can be called by client applications both as a popup or a regular window. the ADF's dialog framework more or less solves my requirement. But to return values from dialog, i have to use "returnFromDialog" method on click of button in the popup window. as i am reusing the page i would write a conditional statement to show diff behaviour when launched as a popup.
my problem is that i do not want client application to set any parameter in the managed bean (this would get client apps into the implementation issues, causing unnecessary complexity). This again brings me back to the same question ability to KNOW (get handle of) the "navigation case".
Pradeep

JSF Page Load

Is there such thing as a JSF Init Page Load? the same thing that .net has with Page_Load? How do i init the code behind bean?

@sdechgan
I had the same problem. What you can do is the following:
in your Bean you need all your request parameters as properties with getter and setter.
additionally add a boolan prepare property. Set this to false at the beans constructor : this.prepare = false;
in your faces config define your bean this way :
<managed-bean>
        <managed-bean-name>myBean</managed-bean-name>
        <managed-bean-class>org.you.package.beans.myBean</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
             <property-name>requestParam01</property-name>
             <value>#{param.requestParam01}</value>
         </managed-property>
         <managed-property>
             <property-name>requestParam02</property-name>
             <value>#{param.requestParam02}</value>
         </managed-property>
         <managed-property>
             <property-name>prepare</property-name>
             <value>true</value>
         </managed-property>
    </managed-bean>in your view add such a single line at the beginning ( right under <f:view... > )
<h:panelGroup rendered="#{myBean.prepare}" />now, tomcat will execute myBean.getPrepare( )
this method should look like this :
public boolean getPrepare()
          if (prepare)
               //do what you want with your request params. they are already set at this point !
          prepare = false;
         return prepare;
     }after loading the view once, the getPrepare Method is executed and the prepare property is set to false.
I need that, because getPrepare is loaded at any ajax page reload, too. ( I'm using icefaces )
access your jsf page with : http:localhost:8080/whatever/myPage.iface?requestParam01=hello&requestParam02=World

The affect of failed validation on the page rendering phase

This is divided in two parts. In the first one I describe the behavior and in the second I show work around and make a suggestion.
The need that started this was that the value an item needed to be recalculated each time de page was shown. This page could be called from buttons and from branches on other pages. So the logical place to put this calculation is in Computation of the Page Rendering phase. But, when a validation failed the value wasn't shown on the browser and I later discovered it was not calculated at all. I tried moving the calculation in a Process of the Page Rendering phase, but to that didn't worked either. So I needed to have a beter understanding of happens when a validation fails, ence this test.
The test was done on version 3.1.2 of APEX.
For this test, here is what I programmed (if no values is specified, than the property has the default value):
1. I created a blank page
-- In the Page Rendering part --
2. I created a region with the following properties
Identification
- Title: Alpha
- Type: PL/SQL (Anonymous block)
Source
- Region Source: wwv_flow.debug('> RENDER REGION Alpha SOURCE');
Conditional Display
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER REGION Alpha CONDITION'); RETURN TRUE;
Caching
- Caching: Cahed
- Cache Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER REGION Alpha CACHE CONDITION'); RETURN TRUE;
3. I created an item with the following properties
Name
- Name: P1_X
- Display As: Textfield
Displayed
- Region: Alpha
Source
- Source Used: Always, replacing any existing value in session state
- Source Type: PL/SQL Function body
- Source value or expression: wwv_flow.debug('> RENDER ITEM P1_X SOURCE'); RETURN NULL;
- Post Calculation Computation: :P1_X || ' POST-CALCUL'
Default
- Default value: wwv_flow.debug('> RENDER ITEM P1_X DEFAULT'); RETURN 'RENDER ITEM P1_X DEFAULT';
- Default Value Type: PL/SQL Function body
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_X CONDITION'); wwv_flow.debug('> P1_X="'||:P1_X||'"'); RETURN TRUE;
Read Only
- Read Only Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_X READ_ONLY CONDITION'); RETURN FALSE;
4. I created a second item with the following properties
- Name: P1_Y
- Display As: Textfield
Displayed
- Region: Alpha
Source
- Source Used: Only when current value in session state is null
- Source Type: PL/SQL Function body
- Source value or expression: wwv_flow.debug('> RENDER ITEM P1_Y SOURCE'); RETURN NULL;
- Post Calculation Computation: :P1_Y || ' POST-CALCUL'
Default
- Default value: wwv_flow.debug('> RENDER ITEM P1_Y DEFAULT'); RETURN 'RENDER ITEM P1_Y DEFAULT';
- Default Value Type: PL/SQL Function body
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_Y CONDITION'); wwv_flow.debug('> P1_Y="'||:P1_Y||'"'); RETURN TRUE;
Read Only
- Read Only Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER ITEM P1_Y READ-ONLY CONDITION'); RETURN FALSE;
5. I created a button with the following properties
Name
- Button Name: GO
- Text Label/Alt: Go
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Go CONDITION'); RETURN TRUE;
6. I created a second button with the following properties
Name
- Button Name: GOERRNULL
- Text Label/Alt: Go invalid
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Go invalid CONDITION'); RETURN TRUE;
7. I created a thrid button with the following properties
Name
- Button Name: RESET
- Text Label/Alt: Reset cache
Displayed
- Display in Region: Alpha
- Button Position: Top of Region
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER BUTTON Reset CONDITION'); RETURN TRUE;
Optional URL Redirect
- Target is a: Page in this Appplication
- Page: 1
- resetpagination for this page: checked
- Request: RESET
- Clear Cache: 1
8. I created a computation with the following properties
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:Before Header
Source
- Computation: wwv_flow.debug('> RENDER CALCUL P1_Y SOURCE'); RETURN 'RENDER CALCUL P1_Y SOURCE';
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER CALCUL P1_Y CONDITION'); RETURN TRUE;
9. I created a process
Name
- Name: Beta
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Load - Before Header
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> RENDER PROC Beta SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> RENDER PROC Beta CONDITION'); RETURN TRUE;
-- In the Page Processing part --
10. I created a computation
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: wwv_flow.debug('> PROC CALCUL P1_Y SOURCE'); RETURN 'PROC CALCUL P1_Y SOURCE';
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC CALCUL P1_Y CONDITION'); RETURN TRUE;
11. I created a second computation
Item Name
- Item Name: P1_X
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: wwv_flow.debug('> PROC CALCUL P1_X SOURCE'); RETURN NULL;
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC CALCUL P1_X CONDITION'); RETURN TRUE;
12. I created a validation
Validation
- Name: Delta
- Type: Function Returning Boolean
- Validation Expression 1: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN FALSE;
Error Message
- Error Message: err msg
- Associated Item: P1_X
Conditionals
- When Button Pressed: GOERRNULL (Go invalid)
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC VALIDATION Delta CONDITION'); RETURN TRUE;
13. I created a process
Name
- Name: Gamma
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Submit - Before Computation and Validations
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> PROC PROC Gamma SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC PROC Gamma CONDITION'); RETURN TRUE;
14. I created a second process
Name
- Name: Epsylon
- Type: PL/SQL anonymous block
Process Point
- Process Point: On Submit - After Computation and Validations
- Run Process: Once Per Page Visit (Default)
Source
- Process: wwv_flow.debug('> PROC PROC Epsylon SOURCE');
Conditional Processing
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC PROC Epsylon CONDITION'); RETURN TRUE;
15. I created a branch
Point
- Branch Point: On Submit: After Processing (After Computation, Validation and Processiong)
Action
- Target Type: Page in this Application
- Page: 1
- include process success message: checked
Conditions
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: wwv_flow.debug('> PROC BRANCH P1 CONDITION'); RETURN TRUE;
As can be seen, I've programmed all condition to be true and therefore making all objects do thier calculations.
Here is the debug output when we click on "Go". (a line number was added for easy refence)
{color:#999999}001 0.05: A C C E P T: Request="GO"
002 0.09: Metadata: Fetch application definition and shortcuts
003 0.09: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
004 0.09: alter session set nls_language="AMERICAN"
005 0.09: alter session set nls_territory="AMERICA"
006 0.09: NLS: CSV charset=WE8MSWIN1252
007 0.09: ...NLS: Set Decimal separator="."
008 0.09: ...NLS: Set NLS Group separator=","
009 0.09: ...NLS: Set date format="DD-MON-RR"
010 0.09: ...Setting session time_zone to -05:00
011 0.09: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
012 0.09: Session: OK to reuse builder session for user:APEX_PUBLIC_USER
013 0.09: Fetch session state from database
014 0.10: ...Check session 2800365259756461 owner
015 0.10: ...Metadata: Fetch Page, Computation, Process, and Branch
016 0.10: Session: Fetch session header information
017 0.10: ...Metadata: Fetch page attributes for application 202, page 1
018 0.10: ...Validate item page affinity.
019 0.10: ...Validate hidden_protected items.
020 0.10: ...Check authorization security schemes
021 0.10: Session State: Save form items and p_arg_values
022 0.10: ...Session State: Save Item "P1_X" newValue="RENDER ITEM P1_X DEFAULT POST-CALCUL" "escape_on_input="N"
023 0.10: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE POST_CALCUL"
024 0.10: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
025 0.11: {color}{color:#ff9900}> PROC PROC Gamma CONDITION{color}{color:#999999}
026 0.11: ...Process "Gamma": PLSQL (ON_SUBMIT_BEFORE_COMPUTATION) wwv_flow.debug('> PROC PROC Gamma SOURCE');
027 0.11: {color}{color:#ff9900}> PROC PROC Gamma SOURCE{color}{color:#999999}
028 0.11: Branch point: BEFORE_COMPUTATION
029 0.11: Computation point: AFTER_SUBMIT
030 0.11: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
031 0.11: {color}{color:#ff9900}> PROC CALCUL P1_Y CONDITION{color}{color:#999999}
032 0.11: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
033 0.11: ...Performing function body computation
034 0.12: {color}{color:#ff9900}> PROC CALCUL P1_Y SOURCE{color}{color:#999999}
035 0.12: ...Session State: Saved Item "P1_Y" New Value="PROC CALCUL P1_Y SOURCE"
036 0.12: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_X
037 0.12: {color}{color:#ff9900}> PROC CALCUL P1_X CONDITION{color}{color:#999999}
038 0.12: ...Perform computation of item: P1_X, type=FUNCTION_BODY
039 0.12: ...Performing function body computation
040 0.12: {color}{color:#ff9900}> PROC CALCUL P1_X SOURCE{color}{color:#999999}
041 0.12: ...Session State: Saved Item "P1_X" New Value=""
042 0.12: Tabs: Perform Branching for Tab Requests
043 0.12: Branch point: BEFORE_VALIDATION
044 0.12: Perform validations:
045 0.12: {color}{color:#ff9900}> PROC VALIDATION Delta CONDITION{color}{color:#999999}
046 0.12: ...PL/SQL "function body returning boolean" Validation: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN :REQUEST 'GOERRNULL';
047 0.12: {color}{color:#ff9900}> PROC VALIDATION Delta SOURCE{color}{color:#999999}
048 0.13: Branch point: BEFORE_PROCESSING
049 0.13: Processing point: AFTER_SUBMIT
050 0.13: {color}{color:#ff9900}> PROC PROC Epsylon CONDITION{color}{color:#999999}
051 0.13: ...Process "Epsylon": PLSQL (AFTER_SUBMIT) wwv_flow.debug('> PROC PROC Epsylon SOURCE');
052 0.13: {color}{color:#ff9900}> PROC PROC Epsylon SOURCE{color}{color:#999999}
053 0.13: Branch point: AFTER_PROCESSING
054 0.13: ...Evaluating Branch: AFTER_PROCESSING type: "REDIRECT_URL" button: (No Button Pressed) branch: wwv_flow.debug('> PROC BRANCH P1 C5NDITION'); RETURN TRUE;
055 0.14: {color}{color:#ff9900}> PROC BRANCH P1 CONDITION{color}{color:#999999}
0.00:
0.00: S H O W: application="202" page="1" workspace="" request="" session="2800365259756461"
0.00: Language derived from: FLOW_PRIMARY_LANGUAGE, current browser language: en-us
056 0.00: alter session set nls_language="AMERICAN"
057 0.00: alter session set nls_territory="AMERICA"
058 0.00: NLS: CSV charset=WE8MSWIN1252
059 0.00: ...NLS: Set Decimal separator="."
060 0.00: ...NLS: Set NLS Group separator=","
061 0.00: ...NLS: Set date format="DD-MON-RR"
062 0.01: ...Setting session time_zone to -05:00
063 0.01: NLS: Language=en-us
064 0.01: Application 202, Authentication: CUSTOM2, Page Template: 2204612885682472
065 0.01: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
066 0.01: ...ok to reuse builder session for user:APEX_PUBLIC_USER
067 0.01: ...Application session: 2800365259756461, user=APEX_PUBLIC_USER
068 0.01: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
069 0.01: Session: Fetch session header information
070 0.01: ...Metadata: Fetch page attributes for application 202, page 1
071 0.01: Fetch session state from database
072 0.01: Branch point: BEFORE_HEADER
073 0.01: Fetch application meta data
074 0.02: Computation point: BEFORE_HEADER
075 0.02: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
076 0.02: {color}{color:#ff9900}> RENDER CALCUL P1_Y CONDITION{color}{color:#999999}
077 0.02: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
078 0.02: ...Performing function body computation
079 0.02: {color}{color:#ff9900}> RENDER CALCUL P1_Y SOURCE{color}{color:#999999}
080 0.02: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE"
081 0.02: Processing point: BEFORE_HEADER
082 0.02: {color}{color:#ff9900}> RENDER PROC Beta CONDITION{color}{color:#999999}
083 0.02: ...Process "Beta": PLSQL (BEFORE_HEADER) wwv_flow.debug('> RENDER PROC Beta SOURCE');
084 0.02: {color}{color:#ff9900}> RENDER PROC Beta SOURCE{color}{color:#999999}
085 0.02: Show page template header
086 0.03: Computation point: AFTER_HEADER
087 0.03: Processing point: AFTER_HEADER
088 0.03: Computation point: BEFORE_BOX_BODY
089 0.03: Processing point: BEFORE_BOX_BODY
090 0.03: Region: Alpha
091 0.03: {color}{color:#ff9900}> RENDER REGION Alpha CONDITION{color}{color:#999999}
Alpha
092 0.03: {color}{color:#ff9900}> RENDER BUTTON Go CONDITION{color}{color:#999999}
093 0.03: {color}{color:#ff9900}> RENDER BUTTON Go invalid CONDITION{color}{color:#999999}
094 0.03: {color}{color:#ff9900}> RENDER BUTTON Reset CONDITION{color}{color:#999999}
Go Go invalid Reset cache
095 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X CONDITION{color}{color:#999999}
096 0.03: > P1_X=""
097 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X READ_ONLY CONDITION{color}{color:#999999}
098 0.03: Item: P1_X TEXT
099 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X SOURCE{color}{color:#999999}
100 0.03: {color}{color:#ff9900}> RENDER ITEM P1_X DEFAULT{color}{color:#999999}
X RENDER ITEM P1_X DEFAULT POST-CALCUL
101 0.03: {color}{color:#ff9900}> RENDER ITEM P1_Y CONDITION{color}{color:#999999}
102 0.03: > P1_Y="RENDER CALCUL P1_Y SOURCE"
103 0.04: {color}{color:#ff9900}> RENDER ITEM P1_Y READ-ONLY CONDITION{color}{color:#999999}
104 0.04: Item: P1_Y TEXT
Y RENDER CALCUL P1_Y SOURCE POST_CALCUL
105 0.04: {color}{color:#ff9900}> RENDER REGION Alpha SOURCE{color}{color:#999999}
106 0.04: Computation point: AFTER_BOX_BODY
107 0.04: Processing point: AFTER_BOX_BODY
108 0.04: Computation point: BEFORE_FOOTER
109 0.04: Processing point: BEFORE_FOOTER
110 0.04: Show page tempate footer
111 0.04: Computation point: AFTER_FOOTER
112 0.04: Processing point: AFTER_FOOTER
113 0.04: Log Activity:
114 0.04: Execute Count=0
115 0.04: End Show:{color}
Here is the debug output when we click on "Go invlid". (a line number was added for easy refence)
{color:#999999}201 0.14: A C C E P T: Request="GOERRNULL"
202 0.19: Metadata: Fetch application definition and shortcuts
203 0.19: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
204 0.19: alter session set nls_language="AMERICAN"
205 0.19: alter session set nls_territory="AMERICA"
206 0.19: NLS: CSV charset=WE8MSWIN1252
207 0.19: ...NLS: Set Decimal separator="."
208 0.20: ...NLS: Set NLS Group separator=","
209 0.20: ...NLS: Set date format="DD-MON-RR"
210 0.20: ...Setting session time_zone to -05:00
211 0.24: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
212 0.24: Session: OK to reuse builder session for user:APEX_PUBLIC_USER
213 0.24: Fetch session state from database
214 0.29: ...Check session 2800365259756461 owner
215 0.29: ...Metadata: Fetch Page, Computation, Process, and Branch
216 0.29: Session: Fetch session header information
217 0.29: ...Metadata: Fetch page attributes for application 202, page 1
218 0.30: ...Validate item page affinity.
219 0.30: ...Validate hidden_protected items.
220 0.30: ...Check authorization security schemes
221 0.30: Session State: Save form items and p_arg_values
222 0.31: ...Session State: Saved Item "P1_X" New Value="RENDER ITEM P1_X DEFAULT POST-CALCUL"
223 0.31: ...Session State: Saved Item "P1_Y" New Value="RENDER CALCUL P1_Y SOURCE POST_CALCUL"
224 0.31: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
225 0.32: {color}{color:#ff9900}> PROC PROC Gamma CONDITION{color}{color:#999999}
226 0.32: ...Process "Gamma": PLSQL (ON_SUBMIT_BEFORE_COMPUTATION) wwv_flow.debug('> PROC PROC Gamma SOURCE');
227 0.32: {color}{color:#ff9900}> PROC PROC Gamma SOURCE{color}{color:#999999}
228 0.33: Branch point: BEFORE_COMPUTATION
229 0.33: Computation point: AFTER_SUBMIT
230 0.33: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
231 0.34: {color}{color:#ff9900}> PROC CALCUL P1_Y CONDITION{color}{color:#999999}
232 0.34: ...Perform computation of item: P1_Y, type=FUNCTION_BODY
233 0.34: ...Performing function body computation
234 0.34: {color}{color:#ff9900}> PROC CALCUL P1_Y SOURCE{color}{color:#999999}
235 0.34: ...Session State: Saved Item "P1_Y" New Value="PROC CALCUL P1_Y SOURCE"
236 0.34: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_X
237 0.34: {color}{color:#ff9900}> PROC CALCUL P1_X CONDITION{color}{color:#999999}
238 0.34: ...Perform computation of item: P1_X, type=FUNCTION_BODY
239 0.34: ...Performing function body computation
240 0.35: {color}{color:#ff9900}> PROC CALCUL P1_X SOURCE{color}{color:#999999}
241 0.35: ...Session State: Saved Item "P1_X" New Value=""
242 0.35: Tabs: Perform Branching for Tab Requests
243 0.35: Branch point: BEFORE_VALIDATION
244 0.35: Perform validations:
245 0.75: {color:#ff9900}> PROC VALIDATION Delta CONDITION{color}{color:#999999}
246 0.76: ...PL/SQL "function body returning boolean" Validation: wwv_flow.debug('> PROC VALIDATION Delta SOURCE'); RETURN FALSE;
247 0.78: {color}{color:#ff9900}> PROC VALIDATION Delta SOURCE{color}{color:#999999}
248 0.78: ...{color}{color:#ff0000}Validation did NOT pass{color}{color:#999999}
249 0.78: ...{color}{color:#ff0000}Inline validation error count = 1{color}{color:#999999}
250 0.86: Show current page with inline validations
251 0.87:
252 0.87: S H O W: application="202" page="1" workspace="" request="" session="2800365259756461"
253 0.87: NLS: Language=en-us
254 0.87: Application 202, Authentication: CUSTOM2, Page Template: 2204612885682472
255 0.88: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
256 0.88: ...ok to reuse builder session for user:APEX_PUBLIC_USER
257 0.88: ...Application session: 2800365259756461, user=APEX_PUBLIC_USER
258 0.88: ...Determine if user "FORD10" workspace "80447903191151509" can develop application "202" in workspace "80447903191151509"
259 0.88: ...Metadata: Fetch page attributes for application 202, page 1
260 0.88: Branch point: BEFORE_HEADER
261 0.88: Fetch application meta data
262 0.88: Computation point: BEFORE_HEADER
263 0.88: ...Evaluate condition "FUNCTION_BODY" for computation of item: P1_Y
264 0.92: {color}{color:#99cc00}> RENDER CALCUL P1_Y CONDITION{color}{color:#999999}
265 0.92: Processing point: BEFORE_HEADER
266 0.92: ......Do not perform process because inline validation condition found.
267 0.92: ...Do not run process "Beta", process point=BEFORE_HEADER, condition type=FUNCTION_BODY, when button pressed=
268 0.92: ...Recompute field lables for fields in error.
269 0.97: Show page template header
270 1.20: Computation point: AFTER_HEADER
271 1.20: Processing point: AFTER_HEADER
1 error has occurred
* Error msg
272 1.20: Computation point: BEFORE_BOX_BODY
273 1.20: Processing point: BEFORE_BOX_BODY
274 1.21: Region: Alpha
275 1.23: {color}{color:#ff9900}> RENDER REGION Alpha CONDITION{color}{color:#999999}
Alpha
276 1.25: {color}{color:#ff9900}> RENDER BUTTON Go CONDITION{color}{color:#999999}
277 1.25: {color}{color:#ff9900}> RENDER BUTTON Go invalid CONDITION{color}{color:#999999}
278 1.28: {color}{color:#ff9900}> RENDER BUTTON Reset CONDITION{color}{color:#999999}
Go Go invalid Reset cache
279 1.30: {color}{color:#ff9900}> RENDER ITEM P1_X CONDITION{color}{color:#999999}
280 1.30: > P1_X=""
281 1.30: {color}{color:#ff9900}> RENDER ITEM P1_X READ_ONLY CONDITION{color}{color:#999999}
282 1.30: Item: P1_X TEXT
X POST-CALCUL
Error msg
283 1.30: {color}{color:#ff9900}> RENDER ITEM P1_Y CONDITION{color}{color:#999999}
284 1.30: > P1_Y="PROC CALCUL P1_Y SOURCE"
285 1.31: {color}{color:#ff9900}> RENDER ITEM P1_Y READ-ONLY CONDITION{color}{color:#999999}
286 1.31: Item: P1_Y TEXT
Y PROC CALCUL P1_Y SOURCE POST_CALCUL
287 1.32: {color}{color:#ff9900}> RENDER REGION Alpha SOURCE{color}{color:#999999}
288 1.32: Computation point: AFTER_BOX_BODY
289 1.32: Processing point: AFTER_BOX_BODY
290 1.32: Computation point: BEFORE_FOOTER
291 1.32: Processing point: BEFORE_FOOTER
292 1.32: Show page tempate footer
293 1.32: Computation point: AFTER_FOOTER
294 1.32: Processing point: AFTER_FOOTER
295 1.32: Log Activity:
296 1.32: Execute Count=0
297 1.32: End Show:{color}
Looking at those debug output, I was able to find a workaround. Look at the line 264 and compare that to the lines 076 to 080. What I did is put the computation in the condition. This way, I'm garanteed that the calculation is always done. Here is an exemple:
A Computation (in the Page Rendering part)
Item Name
- Item Name: P1_Y
- Type: PL/SQL Function body
Computation Point
- Computation Point:After Submit
Source
- Computation: RETURN :P1_Y; -- Never executed. Look in the condition for computation
Conditional Computations
- Condition Type: PL/SQL Function Body Returning a Boolean
- Expression 1: :P1_Y := COMPUTE(); RETURN FALSE;
This works but totally break the semantics created in APEX.
Suggestion:
In the Page rendering phase, when a validation fails, the source compution found in a Item (in that case the value is taken from the session state), in a Computation or in Process is never executed.
This should revised.
Their should be a way for the programmer to choose what behavior the rendering phase will have when a validation fails other than using a workaround that might break in futur versions of APEX.
Edited by: user4591233 on Nov 19, 2008 6:32 AM
Edited by: user4591233 on Nov 19, 2008 6:34 AM

Dominique,
Thank you for the detailed problem description. Although you posted it some ten hours ago I have just now finished reading it.
Form pages must be built so they can operate correctly when inline validation errors are displayed. The assumption (by the engine) is that session state (and package state) as it exists at the point the validations are performed is sufficient (and correct) to support the redisplay of the page without the need to fire on-load processes or computations. Session state or package state changes made by after-submit computations or after-submit/before computations/validations processes that prevent correct page behavior on the "validation redisplay" must be avoided.
The condition types Inline Validation Errors Displayed/No Inline Validation Errors Displayed can be used for on-load events/controls (processes, computations, regions, items, ...) for which you need finer control over this behavior.
Also, you can forgo the use of after-submit computations when the resulting alteration of session state would be inimical to proper "validation redisplay" behavior and use On Submit - After Computations and Validations processes instead.
I hope I have understood your situation and that this answer adequately answers your questions.
Scott

JSF page rendered propert

Similar Messages

Maybe you are looking for