Speeding up page rendering

Hi *,
Does anybody know some tips & tricks to speed up page rendering?
I have made a complex MVC application with tons of elements in each view.
When I test the pages on my PC, it works fine (my configuration resembles a small server), but when I test it on regular PC (PIII 500Mhz with 256 RAM) the browsers shows DONE in the status bar, but I see a white screen for 10 to 15 seconds.
I did some runtime analysis and found out that the problem lies not with the application, nor with the network, but purely with Internet Explorer.
I kicked out some htmlb elements which were only used to fancy-up the page, and sticked to pure HTML as much as possible, this improved rendering by 15%, but still the rendering is very slow.
Does anybody know some other tricks to speed it up?
Thanks in advance
Mario Vangerven

Sounds very strange. The drawing of the page elments can not take so long.
I guess that the problem is not in the rendering.
Check the HTTP trace of the browser. I suspect some unavailable of 'long-accessible' resources there.

Similar Messages

Why is connection speed and page rendering so much slower in FF 3.6.13?

After installation of the 3.6.13 upgrade, website connection and page rendering speed became significantly slower than in all previous versions. I searched the knowledge base and Forum and found this post:
http://support.mozilla.com/en-US/questions/668695#answer-108852
After changing settings as described in the post, speed was easily more than doubled.
I'm wondering if anyone else has experienced the slowdown in connection and rendering speed with 3.6.13. And also why, if the settings worked so well for me, they aren;t standard in FF?

http://www.nasdaq.com/asp/quotes_news.asp?cpath=20040608\ACQBIZ200406080001BIZWIRE_USPR_____BW6209.htm&symbol=amd&selected=amd&kind=&mode=basics&formtype=&mkttype=&pathname=&page=news

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

Want to prevent pictures from loading in order to speed up page loading.

In order to minimize data usage and to speed up page loading, I can get by with text only. No pictures required.
Any way to do this in a "global" way?
Thank you

You can disable images completely by setting permissions.default.image to 2 on the <b>about:config</b> page.
Note that this can cause issues with buttons that are a background image.
*http://kb.mozillazine.org/permissions.default.image
You can look at this extension:
*Image Block: https://addons.mozilla.org/firefox/addon/image-block/

ADF how can i execute a query with parameters when the page renders

hi
i am using ADF web 11g
i need to execute a query with parameters when the page renders
thanks

hello,
I'm a fan of Java code, I really am.
But when you use ADF, you decided to move to a more declarative environment.
So why not do it declarative, the adf way?
In your pagedef insert a action binding.
This can be anything, a call to the application module, a call on the iterator(Like executeWithparams, etc.)
Create an invokeAction in your pagedef and set the condition.
This example refreshes(Action 2 is execute query) the data.
First the method binding:
    <action IterBinding="PersoonIterator" id="Execute" InstanceName="LSAppModuleDataControl.Persoon"
            DataControl="LSAppModuleDataControl" RequiresUpdateModel="true" Action="2"/>And the invoke action
    <invokeAction Binds="Execute" id="refreshData"/>This always refreshes the data on page entry, but anything is possible, you can set condictions for the invokeAction.
-Anton
PS Yes I know that pagedefs become backing beans in the end and yes that is Java code, but if you wanna play the ADF way, the goal is the reduction of Java code and the increased performance of declarative programming.

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

ADF Faces : simultaneous partial page rendering

hi
I'm wondering what I can expect from "simultaneous partial page rendering".
I would like to have some af:selectOneChoice components on a page, with next to them some related information about the selected value.
This example application, created using JDeveloper 10.1.3.3.0, does this using partial page rendering (check README.txt):
http://verveja.footsteps.be/~verveja/files/oracle/SimultaneousPPRApp-v0.01.zip
It as a pprPage.jspx with these components ...
          <af:panelPage title="pprPage">
            <af:panelHorizontal>
              <af:commandButton text="some button"/>
              <af:objectSpacer width="10" height="10"/>
              <af:outputText value="requestCounter.value = #{requestCounter.value}"/>
            </af:panelHorizontal>
            <af:panelHorizontal>
              <af:selectOneChoice label="selectOneChoice A"
                                  id="selectOneChoiceA" autoSubmit="true"
                                  binding="#{backing_PPRPage.selectOneChoiceA}"
                                  valueChangeListener="#{backing_PPRPage.onChangeSelectOneChoiceA}">
                <af:selectItem label="null value label"
                               value="#{null}"/>
                <af:selectItem label="first choice label"
                               value="first-choice-value"/>
                <af:selectItem label="second choice label"
                               value="second-choice-value"/>
                <af:selectItem label="third choice label"
                               value="third-choice-value"/>
              </af:selectOneChoice>
              <af:objectSpacer width="10" height="10"/>
              <af:outputText value="#{backing_PPRPage.selectOneChoiceARelatedValue}"
                             partialTriggers="selectOneChoiceA"/>
            </af:panelHorizontal>
            <af:panelHorizontal>
              <af:selectOneChoice label="selectOneChoice B"
                                  id="selectOneChoiceB" autoSubmit="true"
                                  binding="#{backing_PPRPage.selectOneChoiceB}"
                                  valueChangeListener="#{backing_PPRPage.onChangeSelectOneChoiceB}">
                <af:selectItem label="null value label"
                               value="#{null}"/>
                <af:selectItem label="fourth choice label"
                               value="fourth-choice-value"/>
                <af:selectItem label="fifth choice label"
                               value="fifth-choice-value"/>
                <af:selectItem label="sixth choice label"
                               value="sixth-choice-value"/>
              </af:selectOneChoice>
              <af:objectSpacer width="10" height="10"/>
              <af:outputText value="#{backing_PPRPage.selectOneChoiceBRelatedValue}"
                             partialTriggers="selectOneChoiceB"/>
            </af:panelHorizontal>
            <af:outputText value="userAgentHelper.info = #{userAgentHelper.info}"/>
          </af:panelPage>... and has a backing bean like this ...
public class PPRPage
     public String getSelectOneChoiceBRelatedValue()
          return "some " + fSelectOneChoiceB.getValue() + " related value"
               + ", requestCounter.value = " + ELHelper.get("#{requestCounter.value}");
     public String getSelectOneChoiceARelatedValue()
          return "some " + fSelectOneChoiceA.getValue() + " related value"
               + ", requestCounter.value = " + ELHelper.get("#{requestCounter.value}");
     public void onChangeSelectOneChoiceA(ValueChangeEvent pValueChangeEvent)
          // simulating a slow operation/response
          try
               Thread.sleep(2000);
          catch (InterruptedException ex)
               ; // ignore;
     public void onChangeSelectOneChoiceB(ValueChangeEvent pValueChangeEvent)
          // nothing here to slow things down
}It is important to note that changing the value for the "selectOneChoice A" dropbox has some time consuming operation to perform (possibly calculating/querying the related information to show next to it).
Using IE 6 ("userAgentHelper.info = ... MSIE 6.0 ..."), this behaves like this:
(ie-1) Run pprPage.jspx in JDeveloper, which results in a page that shows this:
selectOneChoice A [null value label] some null related value, ...
selectOneChoice B [null value label] some null related value, ...(ie-2) Select "first choice label" from the "selectOneChoice A" dropbox and immediatly after that select "fourth choice label" from the "selectOneChoice B" dropbox, which results in a page that shows this:
selectOneChoice A [first choice label] some first-choice-value related value, ...
selectOneChoice B [fourth choice label] some null related value, ...(ie-3) Select "second choice label" from the "selectOneChoice A" dropbox, which results in a page that shows this:
selectOneChoice A [second choice label] some second-choice-value related value, ...
selectOneChoice B [fourth choice label] some fourth-choice-value related value, ...Using Firefox 2.0 ("userAgentHelper.info = ... Firefox/2.0.0.12"), this behaves like this:
(ff-1) Do the same as in step (ie-1), which has the same result as step (ie-1).
(ff-2) Do the same as in step (ie-2), which results in a page that shows this:
selectOneChoice A [first choice label] some first-choice-value related value, ...
selectOneChoice B [fourth choice label] some fourth-choice-value related value, ...
questions:
(q1) Why does the related information, for the selected "fourth choice label", not show up in step (ie-2) (as it does in step (ff-2))?
(q2) Why does the related information, for the selected "fourth choice label", show up in step (ie-3) while the value was only/already changed in step (ie-2)?
(q3) Does some general approach exist to prevent "simultaneous partial page rendering" behaviour as described in (q1) and (q2)?
many thanks
Jan Vervecken

repost
--

ADF Faces : partial page rendering in f:subview

hi
Please consider this blog post, "ADF Faces: How-to issue a PPR event from a f:subview and how-to PPR of subviews" :
http://thepeninsulasedge.com/frank_nimphius/2008/02/14/adf-faces-how-to-issue-a-ppr-event-from-a-fsubview-and-how-to-ppr-of-subviews/
In this post, Frank Nimphius writes : "... PPR from a containing page to the subview - unfortunately - only works for the whole subview, which means that the included page is getting refreshed. Because the f:subview component does not support PR, you need to work with a wrapping ADF Faces container, like af:panelGroup ...".
But, it looks like such partial page rendering in a subview can be done without a specific "wrapping ADF Faces container" like this ...
        <h:form id="firstPPRPageFormID">
          <af:panelPage title="firstPPRPage">
            <af:panelHeader text="components on firstPPRPage">
              <af:panelForm>
                <af:panelLabelAndMessage label="dateUtil.currentDateAsString, with partial trigger">
                  <af:outputText value="#{dateUtil.currentDateAsString}"
                                 partialTriggers="firstSubviewID:firstSubviewCButton"/>
                </af:panelLabelAndMessage>
                <af:panelLabelAndMessage label="dateUtil.currentDateAsString">
                  <af:outputText value="#{dateUtil.currentDateAsString}"/>
                </af:panelLabelAndMessage>
                <f:facet name="footer">
                  <af:commandButton text="firstPPRPage button"
                                    id="firstPPRPageCButton"
                                    partialSubmit="true"/>
                </f:facet>
              </af:panelForm>
            </af:panelHeader>
            <f:subview id="firstSubviewID">
              <jsp:include page="/firstSubview.jspx" flush="true"/>
            </f:subview>
          </af:panelPage>
        </h:form>... and where firstSubview.jspx contains something like this ...
<af:panelHeader text="components on firstSubview">
    <af:panelForm>
      <af:panelLabelAndMessage label="dateUtil.currentDateAsString, with partial trigger">
        <af:outputText value="#{dateUtil.currentDateAsString}"
                       partialTriggers=":firstPPRPageFormID:firstPPRPageCButton"/>
      </af:panelLabelAndMessage>
      <af:panelLabelAndMessage label="dateUtil.currentDateAsString">
        <af:outputText value="#{dateUtil.currentDateAsString}"/>
      </af:panelLabelAndMessage>
      <f:facet name="footer">
        <af:commandButton text="firstSubview button" id="firstSubviewCButton"
                          partialSubmit="true"/>
      </f:facet>
    </af:panelForm>
</af:panelHeader>Note the value ":firstPPRPageFormID:firstPPRPageCButton" for the partialTriggers attribute.
see http://verveja.footsteps.be/~verveja/files/oracle/PartialPageRenderingInSubview-v0.01.zip (check README.txt)
questions:
(1) Why exactly does this approach seem to work?
(2) Because of question (1), what could be potential issues with this approach?
regards
Jan Vervecken

Jan,
good job ! I actually never thought of reversing what I said about PPR'ing a component from a subview.
Actually
partialTriggers=":firstPPRPageFormID:firstPPRPageCButton"/>
works because the leading ":" makes ADF Faces to start the component search from the root container. Note that if you use af:form instead of h:form, the trigger is
partialTriggers=":firstPPRPageCButton"/>
I'll update my blog
Frank

Page rendering process doesn't run after validation error

I have a page rendering process (On Load - After Regions) that needs to be run for my page to be rendered properly; however, it doesn't run when the page is rendered after a validation error. In debug mode, I see the following line:
"0.05: ......do not perform process because inline validation condition found."
Is this a bug? Validations are meant to prevent execution of On Submit processes, but is there a reason to also not run rendering processes?
I need to dynamically construct some javascript and insert it somewhere after a certain item on the page. Is there a workaround?
Thanks.
Rodney

Rodney,
Let me see if I understand your question:
1. A page is rendered
2. The page is submitted
3. A validation fires and fails
4. The page is re-rendered displaying the validation error message
5. Your on-load after regions process did not fire
You want to run a process in all cases; in the standard page load case (1) and in the re-load case (4).
You can do this by creating a region of type PL/SQL. You can give the region a null template so that it will not display any values. The region can be the last one displayed on the page; so that it will be run last.
You also asked if it is a bug that the on-load after regions process did not fire; as the debug message indicates this is proper. Here is an example that illustrates why you typically don't want to perform processes when rendering a page after it was posted causing a validation to fire.
Lets take the following example:
1. create a form on the emp table; assume a salary column called "SAL"
2. create a validation that says the salary must be numeric
3. edit a row of the EMP table
4. change the employee job from clerk to manager; and enter a "X" in the salary item
5. submit the page
6. the validation will fire; page processing will stop; and the page will be re-displayed
7. the process which fetches the rows will not fire; and the page will be re-displayed; the job item will display the change from "clerk" to "manager" and salary will still contain the invalid "X" value. If the process had fired it would have replaced the values in the form.
My recommendation is that you use regions for any processing that is UI releated. I hope this helps.
Mike

Global error page - compatible with partial page rendering

My global error page doesn't show in some isolated cases. Could this be because of partial page rendering? What changes might be needed to have it work in all cases?
I have created a global error page and set it in the web.xml with:
<error-page>
<exception-type>java.lang.Exception</exception-type>
<location>pages/htmlErrorPage.html</location>
</error-page>
This displays the htmlErrorPage when errors occur in nearly all my tested cases. However, when the test error is created inside one page redraw I find that the application dies without ever displaying my error page. On the console I get an error message that starts with:
Jun 13, 2008 12:54:11 PM oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer encodeAll
SEVERE: Error during partial-page rendering
javax.faces.el.EvaluationException: javax.faces.FacesException: javax.faces.FacesException: Can't instantiate class: 'com.softrek.adf.view.managed.JFreeChartPlotter'.. class com.softrek.adf.view.managed.JFreeChartPlotter : java.lang.NullPointerException
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:190)
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:143)
But my error page doesn' t show up. I've used the identical test error in most other parts of my application and it shows - so other than the partial page rendering going on, I can't see why this case would be different.
Is there any known bug (or feature) about the use of an error page during partial page rendering?
Any ideas will be welcome.

I'm unclear on how I would get the error to redirect.
I've changed my web.xml to go to a servlet of my creation, set up the mapping and all.
It works fine for exceptions generated in a backing bean normally.
When the exception occurs as part of partial page rendering the error servlet is not called and the user's session dies.
This is being done in JDeveloper 10.1.3.3
The new web.xml contains:
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/servlet/errorAction</location>
</error-page>
Which is working for errors generated under most circumstances but not when they are inside my partial page change.
How do I get errors to go to my error page when the error occurred during PPR?
PS. Using the PartialPageUtils.isPartialRequest() method generated a recursive error in my error servlet. This looks like the known limitation for Faces error handling.

Can the g_f0x variables be accessed in PL/SQL code in page rendering?

Hi,
I have set a button in a tabular form that runs a dynamic action made up of 2 parts in sequence:
(1) a PL/SQL code that updates a collection using g_f01 (selected items in the tabular form)
(2) a javascript that calls apex.server.process to display the selected items in a region
All this code is in the page rendering section being called from a button,and thats the only way it seems to fire PL/SQL and javascript from a button
one after the other.
I have a page process called "submit" that does a loop through the g_f01 values again and updates the collection again just to check.
Now, the PL/SQL code in the dynamic action does not see any selected values in the g_f01 array,while the code in the "submit" page process.
sees them correctly. I've used debug to check.
Question: Can the g_f0x values of a tabular form columns be accessed through a PL/SQL in page rendering, or can they
only be accessed through a page process?
If not, can the g_f0x values be saved in a global array somewhere although that will make things more complicated.
Leckraj

leckj wrote:
Hi Jorge,
Thanks for answering,
If only I had known, because my whole cunning plan was based on this!
Been in APEX only for some 2 weeks, and its a whole new environment coming from the quiet forms6i way
of doing things, and sometimes a bit strange.
I am using collections in fact as my tabular form is based on a view based on a collection.
However, the cells in the form only seem to be placeholders and any changes seem to be made to only the
g_f0x arrays, and the underlying collection members have to be updated programatically.
So if I lose the g_f0x values I cannot update the collection. chicken and eggs.
The flow needs to run a PL/SQL to update the collection,followed by a javascript call to apex.server.process to print the values in a region.
Yon cannot have javascript as a page process, and g_f0x values in the rendering part, so is there anywhere apart from a 2-step dynamic action,
that we can force the run of PL/SQL code followed by javascript?This sounds excessively complicated. The normal APEX approach would be to submit the page, and update the collection from the tabular form <tt>apex_application.g_fxx</tt> array values in a post-submit process. The updated collection values can be displayed in a region using SQL or PL/SQL on page show without recourse to JavaScript.
This early in your use of APEX, why are you not just using the basic technique?

Can we implement partial page rendering on item style Flex??

Hi All,
In an xml,
I have item style 'Flex' for expense account.
Requirement is :
In the same page i have other LOV which brings the data based on one of the segments of that expense account.
So any changes in one of the segments for the expesne account need to be stored and LOV query should be modified accrodingly..
So trying with following possibilties
1) Use partial page rendering for expense account
2) Split the page into two so that first expense account is displayed and any modifications to it are handled in controller and use LOV Mappings to update the query.
So can partial page rendering can be implemented for Item style "Flex".
Can anyone please provide the inputs to handle this scenario and best possible solution?
Issue is very hot right now.. Quick help needed..

Hi
No u can not use PPR for flex items although u can create context flexfield .
thanx
Pratap

When I opened up a new tab, I used to get the Speed Dial page. I like that. However, since I updated my AVG anti-virus program, now when I open a new tab, I get the AVG search page. Can I change it back so that I get the Speed Dial?

In the past, when I opened up a new tab, I used to get the Speed Dial page. I like that. However, since I updated my AVG anti-virus program, now when I open a new tab, I get the AVG search page. Can I change it back so that I get the Speed Dial?

I had that too. On the bottom right of the AVG search page is a link which leads you to where you can switch it off. This restores normal Speed Dial operation.
This hijacking has really cheesed me off. I've just downloaded Avast and am going to put it on in place of AVG.

Apex 4.1 Custom error function and page rendering

Hi
I have setup a demo application at http://apex.oracle.com/pls/apex/f?p=19820:1 which is a simple testing application for testing of the apex_error_handling_example function Patrick wolf put into Oracle documentation. I have setup a error on the page rendering of page 2 in the application. The error process contain this simple error code declare
v_id number;
begin
select 'x' as one into v_id from dual;
end;
which generate plsql numeric or value error. The process is running before regions on page rendering on page 2. I have also created the same error process on page processing before DML processing on the page. When i insert apex_error_handling_example into the application level and run the application the error is not caught and the page is rendered as nothing was wrong. When the page is submitted the error function is executed and work correct.
When i remove the error function from the application the error is caught and displayed on the APEX error page with the detail link for drill down to show more about the error.
Any which can tell what is wrong with the setup i have done. The error function apex_error_handling_example setup is simply a copy/paste from the documentation with some few debug message put into a logging table.
kindest regards
jon

Hi
Yes, when you submit the page the page processing is displaying the error message inline, but it does not show the same error on page rendering for page 2, if i remove the custom error function it will show the error on APEX separate error page. The debug output from the page 1 is as following:
0.12084     0.00345     ...metadata, fetch items     4
5
     0.12431     0.00146     Show page template header     4
2
     0.12576     0.00152     Rendering form open tag and internal values     4
2
     0.12728     0.00034     Computation point: After Header     4
1
     0.12767     0.00040     Processes - point: AFTER_HEADER     4
1
     0.12801     0.00508     ...Process "Fetch Row from DEMO_CUSTOMERS" - Type: DML_FETCH_ROW     4
8
     0.13312     0.00242     ...Execute Statement: begin begin select ROWID,"CUSTOMER_ID","CUST_FIRST_NAME","CUST_LAST_NAME","CUST_STREET_ADDRESS1","CUST_STREET_ADDRESS2","CUST_CITY","CUST_STATE","CUST_POSTAL_CODE","PHONE_NUMBER1","PHONE_NUMBER2","CREDIT_LIMIT","CUST_EMAIL" into wwv_flow.g_column_values(1),wwv_flow.g_column_values(2),wwv_flow.g_column_values(3),wwv_flow.g_column_values(4),wwv_flow.g_column_values(5),wwv_flow.g_column_values(6),wwv_flow.g_column_values(7),wwv_flow.g_column_values(8),wwv_flow.g_column_values(9),wwv_flow.g_column_values(10),wwv_flow.g_column_values(11),wwv_flow.g_column_values(12),wwv_flow.g_column_values(13) from "OLE1923"."DEMO_CUSTOMERS" where "ROWID" = :p_rowid; end; end;     4
4
     0.13552     0.00038     Computation point: Before Box Body     4
1
     0.13590     0.00032     Processes - point: BEFORE_BOX_BODY     4
0
     0.13621     0.00051     ...Process "gen error" - Type: PLSQL     4
1
     0.13672     0.00142     ...Execute Statement: begin declare v_id number; begin select 'x' as one into v_id from dual; end; end;     4
2
     0.13814     0.00052     Add error onto error stack     4
1
     0.13866     0.00048     ...Error data:     4
1
     0.13914     0.00048     ......message: ORA-06502: PL/SQL: numeric or value error: character to number conversion error     4
1
     0.13962     0.00049     ......additional_info: ORA-06502: PL/SQL: numeric or value error: character to number conversion error     4
1
     0.14011     0.00048     ......display_location: ON_ERROR_PAGE     4
1
     0.14059     0.00047     ......is_internal_error: false     4
1
     0.14106     0.00073     ......ora_sqlcode: -6502     4
1
     0.14179     0.00048     ......ora_sqlerrm: ORA-06502: PL/SQL: numeric or value error: character to number conversion error     4
1
     0.14227     0.00049     ......error_backtrace: ORA-06512: at line 6 ORA-06512: at "SYS.DBMS_SYS_SQL", line 1926 ORA-06512: at "SYS.WWV_DBMS_SQL", line 966 ORA-06512: at "SYS.WWV_DBMS_SQL", line 992 ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 649 ORA-06512: at "APEX_040100.WWV_FLOW_PROCESS", line 129      4
1
     0.14276     0.00050     ......component.type: APEX_APPLICATION_PAGE_PROCESS     4
1
     0.14326     0.00079     ......component.id: 64815543714133426115     4
1
     0.14405     0.00058     ......component.name: gen error     4
1
     0.14463     0.00067     ...Execute Error Handling Callout defined on Page or Application Level     4
1
     0.14530     0.00184     ...Execute Statement: begin declare l_error wwv_flow_error.t_error; begin l_error := wwv_flow_error.g_error; wwv_flow_error.g_error_result := apex_error_handling_example ( p_error => l_error ); end; end;     4
3
     0.14714     0.00055     ......Values changed by callout:     4
1
     0.14769     0.00049     .........message: MY.....MY ERROR PL/SQL: numeric or value error: character to number conversion error     4
1
     0.14818     0.00065     .........display_location: INLINE_IN_NOTIFICATION     4
1
     0.14883     0.00331     Region: Form on DEMO_CUSTOMERS     4
5
     0.15214     0.00174     Item: P2_ROWID NATIVE_HIDDEN     4
3
     0.15388     0.00090     Item: P2_CUSTOMER_ID NATIVE_NUMBER_FIELD
The debug output show that the custom error function is running and changing the display location from ON_ERROR_PAGE to INLINE_IN_NOTIFICATION, but there is something going wrong in this processing.
jon

Partial Page Rendering - newbie question

I am a newbie to ADF and I am in the process of trying out the tutorial "Developing Ajax-Based User Interfaces with ADF Faces Rich Client Components" http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_56/jdtut_11r2_56.html
I have a question regarding Step 4. I am not very sure where to post this question, if this is not the correct forum, pardon me.
Under "Step 4: Implementing Partial Page Rendering" there is this following comment
In order to have a refresh of the Product Details when you select another row in the Product table, we need to set the Partial Rendering behavior. To do so, perform the following steps:
Similarly On Step 3, sub step 26 states "Finally, double-click on any of the rows in the product table. Notice that the Product Details pane does not reflect the change in the selected product. To implement this synchronization, we need to add partial page rendering functionality."
Question: even before I tried any of the changes mentioned in step 4, I am finding that the product details pane does show information related to the product selected on the panel collection (in other words it is displaying the master detail information automatically). What am I missing here? As per the training document it is supposed to work only after implementing changes mentioned in step 4. Can one of you kindly point out if this is a mistake in documentation or if I have misunderstood the statement?
Thanks
A Sreedhar

Frank,
Thank you very much for the quick turnaround; I appreciate it.
Yes, I am using what seems to be the latest version of JDev (11.1.2.3.0); and yes the ChangeEventPolicy for the iterator is set to "ppr". Thank you for pointing that out.
Does that mean ppr is standard for most components (when I say components, I mean adf tables, button's etc), don't we need to add any special events to get that to work?
I just wanted to see, what will it due if the ChangeEventPolicy for the iterator is set to "None"; made the change saved it, there were two iterators I changed the "ChangeEventPolicy" on both to none; saved it and ran the page. It worked same as before; I was expecting it will not load the corresponding data at the child level, but it did. can you kindly point out what is wrong.
<executables>
<variableIterator id="variables"/>
<iterator Binds="root" RangeSize="25" DataControl="StoreProducts" id="StoreProductsIterator"
ChangeEventPolicy="none"/>
<accessorIterator MasterBinding="StoreProductsIterator" Binds="products" RangeSize="25" DataControl="StoreProducts"
BeanClass="tutorial.model.Product" id="productsIterator" ChangeEventPolicy="none"/>
</executables>
Thanks
Aravind S

Speeding up page rendering

Similar Messages

Maybe you are looking for