Skip to Main Content

Java Development Tools

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.

show message in page fragment with oracle RDK

Abdelrahman ElGiarSep 19 2022 — edited Sep 19 2022

Hello,
I have a problem with showing messages faces messages or jbo exception messages
I am using page fragments to create pages inside oracle RDK when I show any message in the application I need to click twice to show it and it shows on the top right of the page
when I hide the top menu it shows in the middle from the first click.
how I solve this problem.
thanks in advance.
my jdev ver:12.2.1.2
Screenshot 2022-09-19 093112.jpgScreenshot 2022-09-19 093858.jpg

Comments

Billy Verreynne

Follow which instructions?

How/where are you attempting to assign a schema to an Apex workspace?

What is the schema name? It is case sensitive?

Ivan2405

Managing Workspace to Schema Assignments

Under Editing an Existing Schema and Workspace Assignment.


Like I said it worked for me before every time, but since I added a new workspace, it doesn't worn on either of them.
I have APEX 4.2.2.


Shema name is CM, everything is in capital letters.


Regards,

Ivan

Billy Verreynne

Not an easy error to resolve as it does not seem to be related to user input.

The error library says:

44003, 0000, "invalid SQL name"
// *Document : Yes
// *Cause    : The input parameter string was not a valid simple SQL name.
// *Action   : Check with the DBMS_ASSERT spec to verify that the parameter
//             string is a valid simple SQL name.

Cannot recall running into this exception myself. But it likely is a result to a cursor parse - which implies the error is a result to a dynamically created SQL by Apex.

This should not happen - unless there are something missing or misconfigured in Apex (assuming you have not run into an unknown bug).

I suggest you try manually (via SQL*Plus) using an Apex API call. See APEX_INSTANCE_ADMIN. If this throws an exception, we should have an error and call stack that will provide additional details as to what went wrong where.

Ivan2405

Thanks Billy!

I managed to add the schema to workspace this way, but the error still persists.
I guess I'll just have to it this way from now on...

Regards,

Ivan

1 - 4

Post Details

Added on Sep 19 2022
5 comments
266 views