Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Apex in iframe broken in 4.1?

Olafur TAug 30 2011 — edited Aug 24 2013
Hi,

I am experiencing a strange problem after I upgraded Application Express to 4.1.

Every new application I create, will not work in an iframe. The frame shows up as empty (with chrome's element inspector showing the content as simply <html><head></head><body></body></html>

But older applications (created in 4.0 and earlier) they show up fine without problems.

I have tried all the themes in 4.1 they all do not work in an iframe and if I create new pages in an older application the new pages work fine in an iframe.

So there is some change in the 4.1 that seems to be breaking apex apps within iframes.

I looked at the sequence of events in the Chrome Network tab of the Developer Tools. I see a request for "f" with a response of "302" (temporarily moved), which is fine, its the session mechanism redirecting.
Then I see another request for "f" which gets the response of "Canceled".

I can get an apex error message to show by pointing to a non-existing page in a new 4.1 app, but that is the only response I have been able to get..

Any ideas anyone?

Oli
This post has been answered by Patrick Wolf-Oracle on Aug 30 2011
Jump to Answer

Comments

Hi,

Welcome to OTN. The behavior you are noticing is expected. If you would like to display a custom exception/convertor, check out this doc.

http://docs.oracle.com/cd/E25178_01/web.1111/b31973/af_validate.htm#BABGIEDH

-Arun
SantoshVaza
Hi,
have an af:table with the filtering enabled
on corrosponding field add af:convertNumber tag like 
<af:inputText>
            <af:convertNumber/>
</af:inputText>
So instead of throwing exception it will prompt the user to add a numeric value..

Regards,
User794216-Oracle
Thanks for the replies.
I was aware of those "fixes" except that

- users need to be able to use < or > in the filter criteria, so restricting them to numbers is not a solution
- the custom implemenation is a lot of work for something I would expected ADF to deal with.

I don't get the number exception when I enter "> 100" or "< 100" so the < and > seem to pass succesfully.
But if by accident I enter "= 100" instead of "100" it throws the number exception
So I still feel this should be handled more gracefully out of the box.

Thanks, Ingrid
Here is a simple workaround that I make use of, might help!

Consider I have a bind variable searchString of String type being used in a view criteria. View criteria has a numeral attribute as well as text attribute to compare with :searchString. Now what I do to avoid the exception is that I create another bind variable called searchStringForInt of String type. I set the value of this bind variable as expression type "+searchString != null ? searchString.replaceAll("\\D+","") : null+" and use this :searchStringForInt for comparing with numeral attribute instead of :searchString.
Also FYI, QBE behaviour can be customized. Take a look at http://radio-weblogs.com/0118231/stories/2003/07/11/implementingAViewCriteriaAdapterToCustomizeQueryByExampleFunctionality.html.
1 - 5
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 21 2013
Added on Aug 30 2011
#11g, #apex, #apex-discussions, #error, #javascript
34 comments
15,234 views