My Oracle Support Banner JAAS login error. Null or empty password was provided. (Doc ID 2211855.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle JDeveloper - Version and later
Information in this document applies to any platform.


According to what you can read in the following blog article, it is possible to instantiate an Application Module in a standalone Java application without the need deploy it on a web application server.

Based on the created Application Module instance, the View Objects and View Links defined in the Application Module's data model can be accessed and test cases for the common CRUD operations (Create, Read, Update, Delete) can be easily implemented against them. Executing and debugging these test cases is very simple since they can be launched as standalone Java applications.

The subject of this document is a standalone Java application compliant with what described above. In the same workspace of that application, a View Controller has been added to have a web application that can be deployed on a web application server. Further to that, the main class of the standalone Java application hard-codes the bc4j.xcfg contents generated for the full ADF Fusion Web Application.

When the web application is configured with ADF Security, the following error occurs when executing the standalone Java application

The Java standalone client is working fine with ADF Business Components client when no ADF Security is enabled on the Model using the "Configure ADF Security" wizard.
Also the web application works fine with the ADF Security enabled.
However, the Java standalone application is not working when ADF Security is enabled and when trying to query the Model the above stack trace is dumped.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.