APEX

I changed my procedure to better reflect what is happening in my situation:

create or replace procedure hello(p_who in varchar2)

as

begin

  raise_application_error(-20000,'Hello '||p_who);

end;

And now I can reproduce it. It shows "sqlerrm:ORA-20000: Hello World" when run from the Apex Builder, nothing when run from outside the builder.

It looks like raise_application_error is suppressed in runtime mode. I do have Ajax calls that work fine, but looking a bit closer they don't raise an error, but use htp.p to show the error.

Interestingly LEVEL9 debug shows no difference between APEX and non-APEX sessions. Maybe a bug. As a workaround you may replace your AJAX callback with a Execute PL/SQL Code dynamic action.

Are you sure your AJAX call was actually successful? You might want to add an error callback to the AJAX request. It might be throwing an error but you dont have any actions defined in the event of an error. You only have success defined.

If you've never done that, just copy your success object and paste it after your existing success object. Rename it to error and then change your console log to say something else.

You might want to add an error callback to the AJAX request.

There is no error, just an empty response.

If there was an error, it would be even worse. That would mean that when the applications runs from the builder, it would return a success, but run from outside the builder it would return an error.

That's exactly what appears to be happening. From within the builder the AJAX call runs your "hello" processes successfully. We know this because it is firing the success actions that you have defined. It does not appear that your "hello" process is running successfully from outside of the builder right now. If it were, you would be seeing your success actions firing. The AJAX call will complete successfully regardless of whether your "hello" process runs successfully or not. In order to see errors thrown by your "hello" process you need to define an error handler. The success and error blocks in the call are to determine whether your "hello" ran successfully. Does that make sense?

In both situations there is a console log from the success branch:

console.log("hello result: " + pData);

When run from builder: hello result: sqlerrm:ORA-20000: Hello Me

When run from outside the builder: hello result:

So, there is no error.

You can see it on apex.oracle.com:

Workspace: SQLINT

User: OTN

PW: OTN111111

Application: OTN

Page: 5

Oh, got it! Sorry, I thought you were saying it wasn't firing the success actions at all from outside. I thought you were just seeing the error in the developer tools.

Looking at your app, it doesn't appear to pass a value for P5_WHO at all from outside the builder. This might be a bug. I have built these many times and I have never seen that happen before. However, we are still moving to 19 and I haven't written any of these in this version yet. Let me look at a couple more things.

Jen

The plsql code is:

raise_application_error(-20000,'Hello '||p_who);

If p5_who was not passed, the result would still be "Hello" (without a name), so that is not the problem. You can completely remove the parameter if you want.

It's really just how Apex handles raise_application_error differently when running from the builder or not.

Hello,
What is the solution for the "AjaxCallBack response is empty outside of Builder" problem?
Thanks&Regards

It looks like raise_application_error is suppressed in runtime mode. I do have Ajax calls that work fine, but looking a bit closer they don't raise an error, but use htp.p to show the error.
Correct, the Ajax calls are communicating through the http buffer - which isn't impacted by the raise_application_error.