This document lists known issues for this release. As new issues arise, they
will be added to this document.
We welcome and encourage your feedback. Your input helps us make the product
better. Please use the JDeveloper
community discussion forum on OTN for questions and answers, as well as
to let us know what you think!
General Issues
Migration
Upgrading Existing Oracle WebLogic Server Instances to the 11.1.1.1.0 ADF
Runtime
Open the uninstaller for of the Oracle WebLogic Server instance you want to upgrade.
Select JDeveloper 11g (11.1.1.1.x) Studio Edition 11.1.1.1.0.
Deselect everything under WebLogic Server.
Click Next to complete the uninstall. If you're interested you can click on the Details button to see what was uninstalled.
Open the JDeveloper 11.1.1.0.2 installer.
Select the Oracle WebLogic Server instance where you want to install the new version of the ADF runtime.
Deselect everything, and then select only Application Development Framework Runtime. Note: This will also automatically select the JDeveloper and ADF folders.
To avoid class loading issues, rebuild all your EAR files.
Note: You will find the Oracle WebLogic Server uninstaller either as
$WLSHOME/wlserver_10.3/uninstall/uninstall.sh or %WLSHOME%\wlserver_10.3\uninstall\uninstall.cmd
. On a headless server (like a Linux or Unix-based system), you may need
to set the DISPLAY variable to an X Server like VNC or
Xming. (Assuming that $WLSHOMEor %WLSHOME% is your home
directory for the WebLogic Server 10.3 installation.)
Integrated WLS
Integrated WLS not available for Windows 2000 (8249773)
The Integrated WLS feature is not available on Windows 2000 due to bug 8249773.
If you are using JDeveloper on Windows 2000 platform and wish to build and test
applications requiring WLS, you should configure JDeveloper to connect to a
WLS instance running in a supported configuration.
Windows installations on systems which have disabled
NTFS 8.3 (7342763,7293026)
JDeveloper, ADF Runtime and WebLogic Server make use of 8.3 short filenames on Windows to handle cases where certain paths, such as the JDK and WebLogic domain location, contains spaces. If you wish to use spaces in those paths, please be sure you have NtfsDisable8dot3NameCreation set to the default value of 0 (not 1) before installation. You can re-enable 8.3 naming by using regedit to set HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/FileSystem's NtfsDisable8dot3NameCreation to 1.
You may use the fsutil command at a command prompt to both query and set this value:
eg. c:> fsutil behavior query disable8dot3
On Linux, do not use a system directory with spaces
in it (8447574)
When JDeveloper is first run, the default domain for Integrated WLS is automatically created. If JDeveloper uses a system directory which has spaces in the path you will see a domain creation error in the log window. This is because Integrated WLS (and Oracle WebLogic Server) does not support creation of domains in paths which contain spaces.
The workaround is to avoid having a space in the system directory by using the default system directory. This is of the form ~/.jdeveloper/systemxx.xx.xx.xx, therefore it has no spaces.
In particular, you should not do the following:
Run JDeveloper using jdev -J-Dide.user.dir=/<directory-with-spaces>
Use setenv JDEV_USER_HOME <directory-with-spaces>
Recommended system resource ulimit on Linux (8693621)
The recommended system resource ulimit is 4096 for JDeveloper on Linux. Otherwise,
the "too many open files" limitation may be hit.
To determine the configuration for your system:
/bin/sh -c 'ulimit -n'
Edit your /etc/security/limits.conf file.
* hard nofile 4096
* soft nofile 4096
Files cannot be deleted on Windows systems because
the path is too long (8222570)
JDeveloper may exceed the length of the path names permitted by Windows, and
when you delete files you may see a message reporting that file paths are too
long or not valid.
Some additional steps are required to install JDeveloper on Mac OS beyond what is documented in the installation guide. Please refer to the installation guide for additional details on installing JDeveloper for Mac OS X.
1. Make Java 6 the default VM.
Run Java Preferences (in /Applications/Utilities/Java)
Move the Java SE 6 (64 Bit) to the top of the Java application versions list (General tab)
2. Create a symbolic link for classes.jar
Enable root user:
Open the Directory Utility app from Applications - Utility
Ensure the settings are unlocked (click the lock if necessary)
Choose Edit > Enable Root User and provide the root user password.
Note, you can return to this same screen to disable root user after creating the symbolic link
Create the symbolic link: cd /SystemLibrary/Frameworks/JavaVM.framework/Versions/1.6.0/Home/
su root
mkdir jre
CD jre
mkdir lib
CD lib
ln -s ../../../Classes/classes.jar rt.jar
Running with Integrated WLS fails on Mac OS (8681385)
With Java for Mac OS X Update 4, Apple introduced some hardened security features
which cause the Integrated WLS to fail when running or debugging any Java EE
application. The messages displayed in the console will look something like
the following:
DefaultServer started.
[Running application App_jdk13 on Server Instance DefaultServer...]
java.io.FileNotFoundException: /var/folders/BF/bF5Yc5YAGqCcW9Xwns 5U
TQ/-Tmp-/adfmeta3556177385782956689.xml (No such file or directory)
[01:56:04 PM] #### Deployment incomplete. ####
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
...
#### Cannot run application App_jdk13 due to error deploying to DefaultServer.
[Application App_jdk13 stopped and undeployed from Server Instance DefaultServer]
The workaround is to add the following statement to the jdev.conf file:
AddVMOption -Djava.io.tmpdir=/var/tmp
Do not set CLASSPATH environment variable (8576066)
JDeveloper itself does not look at the value of CLASSPATH or JAVA_HOME to determine
its classpath or jdk. It stores this information in proprietary locations. The
Weblogic domain installation scripts, however, extend the supplied value of
the CLASSPATH variable, and we have come across installations where Weblogic
domain creation will fail if CLASSPATH is set.
We recommend, therefore, that you remove these variables from the environment
before launch JDeveloper. On Windows if you are experiencing problems
with Weblogic domain creation, do start, control panel, system, Advanced tab.
Then select environment variables, and rename CLASSPATH to CLASSPATHX.
IDE and Java SE Development
Double click on IDE application navigation items do not
work first time on Linux (5868618)
It appears that this an OS level issue and affects any Java Swing application
such as JDeveloper. The double click default time is 200 milliseconds in Linux/Gnome,
which is quite short. Therefore, depending on the user's mouse clicking speed
(which usually varies) the user's experience will be that some double clicks
do not work. The root cause is that X-Windows is not registering the double
click as such but rather as two separate (albeit quite close) single clicks.
While Gnome does allow the user to change the mouse click speed, this does not
affect Java/Swing applications since they receive the mouse click directly from
X-Windows, which is still set at 200 milliseconds.
Modifying the X-Windows double click milliseconds manually, therefore, is a
valid workaround. This will also affect all other applications running in this
desktop.
Create a file in user home ($HOME or ~)
.Xdefaults
in Oracle Linux (or .Xresource on other linux flavors) add to the file the
following line:
*multiClickTime: 400
Save and close the file. (The value 400 shown here is based on typical user
experience, you can decide what works best for you.)
Next, execute the following:
xrdb -merge $HOME/.Xdefaults
Relaunch JDeveloper.
Note: This issue and the workaround affect all JDeveloper releases to
date.
Subversion Commit Working Copy does not warn of unsaved
files (7708302)
Users of Subversion may experience unexpected results when saving composite
elements with Commit Working Copy. The issue can occur when, for example, the
user adds a Java file, which appears as a candidate in the Pending Changes list.
However, when the user selects Commit Working Copy, only the Java file is saved;
the associated XML file, which has been edited but not saved, is not committed
at the same time as the Java file. The workaround is to make sure to save all
files in a composite element, and to check the Subversion Pending Changes list
when committing the working copy.
Exception thrown when editing button labels inline (8563316)
If users use List resource bundle for the project, when using inline editing
to update resource bundle value for the component label, it will throw an exception.
There are two workarounds for this issue:
1. Update from java resource bundle file(when using inline editing to update
the default component label like "commandButton 1", it will generate a Java
resource bundle file) directly.
2. Invoke "Select Text Resource" dialog by following three ways:
Second click on the component, click "Select Text Resource" on the coming up flying editor.
Press "F2", click "Select Text Resource" on the coming up flying editor.
In Property Inspector, click the drop down icon next to the Text attribute, choose "Select Text Resource".
Update the resource bundle value from the dialog and make sure to use the existing
key.
Supported CVS configurations
The JDeveloper CVs extension currently supports the following client/server
configurations:
CVs Client
GNU CVs 1.11.1.p1+ Server
CVSNT 2.5.04+ Server
JDeveloper (Internal)
supported
not supported
GNU CVs 1.11.1.p1+
supported
not supported
CVSNT 2.5.04+
supported
supported
Error and warning page of compiler
When the error and warning compiler page is minimized, exceptions might be
thrown after the user fixes errors and warnings and reruns the application.
The workaround is to keep the compiler page docked when visible, which is the
default behavior, and not use the minimize button.
Database Development
Columns in DB2 Connections Display in Structure Window
For IBM UDB DB2 connections, you can see column and constraint information in the Structure window when you select the table in the Database Navigator.
Running out of memory when generating many offline
database objects to SQL script (8580564)
If you try to generate a very large number of offline database objects, for example an offline database of a few thousands of objects, to a SQL file, you may see a low memory message and if you are running with the console, a java.lang.OutOfMemoryError: GC overhead limit exceeded error.
You can avoid this by generating fewer database objects at a time to SQL files.
You will be able to generate more complex schemas that contain a larger number
of offline database objects if you change the setting for AddVMOption
-Xmxto 900M in jdev-install/ide/bin/ide.conf.
Type definition in a PL/SQL file (8609754)
If the PL/SQL in a file has a " before a new line at the end of a file, when
you restart JDeveloper and reopen the file, the file is empty. For example:
CREATE OR REPLACE TYPE "LINEITEM_V" IS VARRAY (2147483647) OF "LINEITEM_T"
The workaround is to do one of the following:
Only use quotes if you need them. If you do, use " as the last character
in the file do not add a new line.
Add a comment at the end of the file, for example:
CREATE OR REPLACE TYPE "LINEITEM_V" IS VARRAY (2147483647) OF "LINEITEM_T"
/* end of type */
Deployment
Running out of memory (7507741)
If you run multiple applications in Integrated WLS, you may run out of memory and see the java.lang.OutOfMemoryError: PermGen space exception.
You can stop Integrated WLS by doing one of the following:
Going to jdeveloper-user-home/DefaultDomain/bin and running stopWebLogic.cmd (on Windows) or stopWebLogic.sh (on Linux).
Ending the Java process using the Task Manager on Windows, or through the kill command on Linux.
You can avoid this happening again by increasing the MEM_MAX_PERM_SIZE from the default of 128m to 256m, 512m, or higher. This is set in setDomainEnv.cmd (Windows) or setDomainEnv.sh (Linux), which is located at jdeveloper-user-home/DefaultDomain/bin.
HTTP error code 502 (7346049,8416355)
If you are deploying to a server running on a machine that is not known to the network DNS server, and you have set a proxy for JDeveloper, deployment will fail with a 502 error code. This is because the proxy does not know where to forward the request. This includes a server on the localhost that is referred to by its machine name (this is typical for SOA development).
The workaround is to add the machine to the Exceptions list in the proxy settings in the Web Browser and Proxy page of the Preferences dialog, which is available from the Tools menu. Alternatively choose not to use a HTTP Proxy Server for any connections.
Memory not released when repeatedly deploying and undeploying
in JDeveloper (8312810)
If you are repeatedly deploying and undeploying an ADF application to an Oracle WebLogic
Server, memory resources may not be released which eventually can result in
a lack of memory. This situation is common during application development using
JDeveloper and the Integrated WebLogic Server.
A new system property, oracle.jrf.EnableAppContextInit, has been created to control whether the Oracle WebLogic Server can use an alternate AWT.
This system property is only consulted by the JRF during WebLogic Server startup and not during each deployment of an application. Because it is consulted at WebLogic Server startup, you must set this property before the actual WebLogic startup process. The property should be set to true for ADF or any other framework that uses any AWT APIs. The default value is false.
As with other Oracle WebLogic system properties, you can set this property
several different ways:
Out of memory error after multiple redeployments (8263421)
In some situations, users may encounter an Out of Memory error as a result
of a memory leak occurring during repeated deploy-run-undeploy-redeploy cycles.
The leak is due to ThreadLocal variables that are allocated by the groovy framework.
The leak is usually insignificant but may become severe if an application server
instance is used to support many Java EE applications and/or if an application
is repeatedly deployed/undeployed on a running application server process. This
issue can effect a standalone runtime environment as well as the Integrated
WLS in JDeveloper. Any application using the groovy framework (including ADF
applications) is susceptible.
A patch is available to customers with a support contract on My Oracle Support.
Please visit http://metalink.oracle.com
and search for patch number 8263421.
How to package a project to be a shared library in WebLogic
Server
If you are packaging a project and want to deploy it as a shared library in a WebLogic
Server, you must wrap the ADF Library JAR with a WAR or EAR file and then install
the WAR or EAR as a shared library into the Oracle WebLogic Server.
For design time usage, producers of the ADF library JAR can create a .library
file that contains the paths to the ADF Library JAR files. The consuming project
can add this Library file to the project's libraries and classpath. When the
Library file is created, the Deploy by Default option must be deselected, otherwise
the JAR paths in the Library file will be included in the user's deployment,
thereby creating a runtime conflict with the same JARs in the shared library.
When the consuming application is being deployed, the dependent ADF Library JAR
wrapped inside a WAR or EAR must already have been deployed to the Oracle
WebLogic Server as as shared library.
Create an ADF Library JAR file.
Right-click the project and select Project Properties > Libraries and Classpath and
add the ADF Library JAR file created in step 1.
Create a WAR deployment profile for the project.
Create the WAR or EAR file. If you do not have ADF Faces components in your
project, add the ADF Faces technology scope to your project before you create the
WAR or EAR file.
Deploy the WAR or EAR file to the WebLogic Server as a shared library using tools
such as the Oracle Fusion Middleware Configuration Wizard, Enterprise Manager,
or WLST scripts.
From the main menu, choose Tools > Manage Libraries.
In the Manage Libraries dialog, click Load Dir.
In the Load Directory dialog, select the directory where you want to place
the Library files. This folder should be in a location next to the corresponding
folder of ADF Library JAR files to simplify the process of locating files.
It can even be the same folder.
In the Manage Libraries dialog, click New.
In the Create Library dialog, enter a library name and click Add Entry.
In the Select Path Entry dialog, select the libraries you want to add and click
Select.
In the Create Library dialog, be sure that Deployed by Default is not selected,
click OK and click OK again.
Open the Library file you created in Step 10 in a text editor and set the
locked property to true and save the file.
At design time, any consuming project can reference this shared library
by adding the Library file to the project using the Project Properties window.
In the Application Navigator of the consuming project, from the main menu,
choose Tools > Manage Libraries.
In the Manage Libraries dialog, click Load Dir.
In the Load Directory dialog, select the directory where the Library
files were created in Step 7.
In the Application Navigator of the consuming project, right-click a project
and select Project Properties.
In the Project Properties window, select Libraries and Classpath and click Add
Library.
In the Add Library dialog, select the Library file and click OK.
click OK.
You must edit either the WEB-INF/weblogic.xml for a WAR or the
META-INF/weblogic-application.xml for an EAR to include a library-ref
entry that specifies the name and version of the shared library that was produced
in Step 4.
Post-deployment application configuration using ADF MBeans
If you plan to configure ADF connection information or adf-config.xml using ADF MBeans after the application has been deployed, make sure that the application is configured with MDS. The adf-config.xml file must include MDS entries, as shown in the following example. If it does not, edit the file to include them.
Post-deployment changes to connections.xml persist as customizations
When the connections.xml file is changed after deployment using AdfConnection MBean, the complete connection is saved as a customization. This means that changes to the connection in a redeployed application are overwritten by the customization.
When you use Enterprise Manager to make changes to an application's connections.xml file after deployment, a new connections.xml file is created as a customization and stored in the MDS repository. This customization persists for the life of the application. Therefore, if you redeploy the application, the customized connections.xml file continues to be applied as a customization on the application.
To allow the redeployed application's connections.xml file to be applied without the prior customization (from Enterprise Manager), you must explicitly remove the connections.xml customizations from the MDS repository.
For example, say you deploy an application with a web services data control.
Then you use Enterprise Manager to attach the 'username token client policy',
and subsequently detach the policy. Then you return to JDeveloper to edit
the application and attach the 'http token client policy', and redeploy the
application. When you view the application using Enterprise Manager, you
see that it is not using the 'http token client policy' that you attached.
That is because it is using the customized connections.xml file that you previously
created using Enterprise Manager. If you remove the connections.xml customizations
from the MDS repository, the application will use the its own connections.xml
file.
Debugging
Supported Browser / Platform for JavaScript Debugging
Supported Browser: Mozilla Firefox 3.0.x
Supported Operation System: Windows XP
Web Services Development
Avoid creating multiple top down web services in the same
project/package (7165531)
Unless they are operating on the same schema avoid creating multiple top-down
web services in the same project as each successive top-down service may overwrite
the ObjectFactory class created by the previous one if generated into the same
package.
Manually edit the header details if invoking WLS stateful
(conversational) web services from HTTP Analyzer (7388843)
When calling conversational web services from HTTP Analyzer, the request message headers for the 'continue' methods need to be manually updated with the conversation id that is specific to that particular conversation. This value is available from the response SOAP message of the method that starts the conversation.
From the response message of the conversation start method, copy the xml tags
similar to the one below:
Services migrated from a previous JDeveloper release are
not guaranteed to deploy and run in WLS
Because of the OC4J proprietary nature of some of the properties set on web services that were created with previous JDeveloper releases (which supported OC4J), it is likely that there will be problems when attempting to deploy and run such services on WLS (including the integrated WLS that is bound with JDeveloper). Known problems include JAX_RPC services that have annotations, stateful services, DIME encoding, OWSM Policy (both 10.1.3 and 11 styles including WS-Security and WS-Reliability).
Cannot deploy and run JAX-RPC with bare array types as
method parameters (7493019)
When using JAX-RPC web services deployed to weblogic using the generators in JDeveloper you may have trouble with method signatures that contain "bare" array types. For example: public class Hello
Unknown macro: { public String[] list(); public String[] echo(String[] value); public void process(int[] values); }
These will either not deploy or when deployed will not work properly with errors complaining about mapping issues. There are a few workarounds for this problem:
Only do wrapped parameters, when starting from a java class Create a bean object that contains all the properties. When creating the web service make sure you select Document/Literal rather than Document/Wrapped to prevent double wrapping.
Make sure you don't allow properties to be unwrapped when doing "top down" On the mapping options page when generating a Java web service from a WSDL make sure you uncheck the "Unwrap Wrapped parameters" box on the "Specify Default Mapping Options" page of the wizard.
Use the weblogic jwsc ant task The ant task will generate a working service from the bare list types but the schema for the WSDL will generate synthetic Java schema types which may not be what the user wants.
It is not possible to successfully invoke a JAX-RPC style conversational (stateful) web service deployed in weblogic server from a JAX-WS style proxy client. The design time JAX-WS proxy creation does not currently warn the user if the supplied WSDL document contains conversational behavior advertisement. Even though the tool leads to a successful generation of JAX-WS client artifacts, invoking the service from this client results in a SOAPFaultException. Only the conversation 'start' methods will get executed successfully. Invoking any other conversational methods after a conversation 'start' method will result in error.
The workaround is to use a JAX-RPC style proxy client to call a stateful service deployed in the weblogic server.
HTTP Analyzer will not capture traffic from a JAX-WS Java
client that is being sent to localhost (7310483)
This is fixed in JDK 1.6 Update 14 and JDeveloper automatically added the required
"~localhost" entry to the proxy excludes list. It is recommended you switch
to this version of Java to work around this issue. If for whatever reason you
cannot try a different version of the JDK you could consider one of the following
ways to work around this:
Use your machine name rather than localhost when calling the service. Either at generation time or runtime call the client with ((BindingProvider)port).getRequestProperties(BindingProvider.ENDPOINT_ADDRESS, "http://mymachine.../...");
where mymachine is the name of your local machine.
Change the default localhost by using the following parameter to the JDeveloper command to set a system property -J-Doracle.jdeveloper.webservices.localhost.default=localhost.localdomain
If you are running JDeveloper on Linux you need to make no more changes.
If you are running JDeveloper on Windows, edit the c:\windows\system32\drivers\etc\hosts file and change the line 127.0.0.1 localhost
to be127.0.0.1 localhost localhost.localdomain
If you are running JDeveloper on Mac OS X, edit the /etc/hosts file as root to include the name of the local machine. That is, change the line
127.0.0.1 localhost
to be
127.0.0.1 localhost localhost.localdomain
JAX-WS async client for a 10.1.3 BPEL process will not
run by default (7422130)
The BPEL server included in 10.1.3 SOA only knows how to use the '2003 draft version of the WS-Addressing specification. The JAX-WS async client will be default generate a client that by modifying the WS_ADDR_VER constants to support either the final '2005 or the member submission '2004 version of the specification. To support the '2003 version the user will need to make some minor modification to the code in order to invoke the process properly.
In the callback handler you need fix the code that requests the relatesToHeader as shown here:
// HeaderList ...
//Header relatesToheader = headerList.get(WS_ADDR_VER.relatesToTag, true);
//String relatesToMessageId = ralatesToheader.getStringContent();
String relatesToMessageId = RelatesTo.getValue();
This uses the header which get automatically bound to a method parameter. Now the BPEL service explicitly defines both the ReplyTo and MessageID headers in the WSDL so the default proxy generator will map these to method parameters. Assuming that you accept this default you need to pass both the replyTo address and the message ID in as parameters to the method rather than as header as you will see in the generated code. The only exception for this is the WS-Addressing action header which if it is required should be set using the '2003 namespace. Here is an example that invokes a loan process that has the required edits.
americanLoan = new AmericanLoan();
LoanService loanService = americanLoan.getLoanServicePort();
// prepare Message Id
AttributedURI messageId = new AttributedURI();
messageId.setValue( "uuid:" + UUID.randomUUID() );
// prepare ReplyTo
AttributedURI address = new AttributedURI();
address.setValue("http://x.x.x.x:7101/Application23-Project1-context-root/LoanServiceCallbackPort");
EndpointReferenceType replyTo = new EndpointReferenceType();
replyTo.setAddress( address );
// prepare action header
WSBindingProvider wsbp = (WSBindingProvider)loanService;
wsbp.setOutboundHeaders(
new StringHeader(
new QName( "http://schemas.xmlsoap.org/ws/2003/03/addressing", "Action" ),
"http://services.otn.com/LoanService/initiateRequest" ));
// Prepare payload
LoanApplicationType payload = ...
// Invoke service with replyTo and messageID parameter
loanService.initiate(lt, replyTo, messageId);
JAX-WS clients may require an extra jar added to project
classpath (8440262)
In some rare corner cases, the default stax parser bundled with weblogic may
cause a read error of the form 'Got character[0] expected a valid XML character'
when running a JAX-WS client. If this happens you will need to force the runtime
stack to use the woodstox parser instead of the default weblogic one by adding
the com.bea.core.woodstox_1.0.0.0_3-2-5.jar file to the project's classpath
ahead of the 'JAX-WS Client' library in the list of classpath entries for the
project. To achieve this, open the 'Project Properties' dialog for the project.
Move to the 'Libraries and Classpath' page. Click on the 'Add JAR/Directory'
button. In the 'Add Archive or Directory' dialog, locate and select the com.bea.core.woodstox_1.0.0.0_3-2-5.jar
file, which will be located under the 'modules' sub-directory of your installation
root directory. With the com.bea.core.woodstox_1.0.0.0_3-2-5.jar file
selected in the 'Classpath Entries' list, click on the 'Move Up' button until
it is ahead of the 'JAX-WS Client' entry in the list and 'OK' the 'Project Properties'
dialog. When these steps are complete, the read error should no longer be encountered
when running the client.
Running a WS-Reliability enabled 10.1.3 proxy migrated
to 11gR1 may fail with NoClassDefFounndError (8545586)
WS-Reliability is not supported in JRF web services stack in JDeveloper 11gR1
nor is this feature portable from JDeveloper 10.1.3 to JDeveloper 11gR1. Moreover,
the WS-Reliability from JDeveloper 10.1.3 is not compatible with the WS-ReliableMessaging
(WS-RM) that the new version of applications use. Hence it is not expected that
any migrated JAX-RPC proxy projects with enabled reliability in 10.1.3 would
be fully compatible and work in JDeveloper 11gR1.
However, in order to overcome the class not found error of JPS related files, manually include the following jar files into the project's libraries. This does not guarantee to work in all such cases.
Regenerating a WS-Reliability enabled 10.1.3 proxy migrated
to 11gR1 loses header details (8551757)
WS-Reliability is not supported in JRF web services stack in JDeveloper 11gR1
nor is this feature portable from JDeveloper 10.1.3 to JDeveloper 11gR1. Moreover,
the WS-Reliability from JDeveloper 10.1.3 is not compatible with the WS-ReliableMessaging
(WS-RM) that the new version of applications use. Hence the regeneration of
a migrated JAX-RPC proxy project with enabled reliability in 10.1.3 is not expected
to retain the old reliability header details found in the migrated proxy.
Converting 10.1.3 (OC4J) JAX-RPC web service to WLS compliant
JAX-RPC web service only available for first one in project (8587051)
If a user migrates a 10.1.3 project that contains more than one JAX-RPC web
service, the facility to convert those services to a WLS compliant JAX-RPC web
service will only be available for one of those services. Once it has been activated
once, the project will be reconfigured for WLS JAX-RPC services and the conversion
option will no longer be available for the other services. The user will then
have to manually regenerate each of the other services (using one of the regenerate
options from the context menu for each service) in order to convert each of
them to WLS compliant services.
EJB, JPA, and Java EE Development
Configuring an EJB/POJO-Based ADF-BC service for deployment
to the SOA platform (8516162)
To use an EJB/POJO SDO ADF-BC service from a fabric composite using SDO external bindings, you need to set up the Weblogic application deployment listener to invoke the ServiceRegistry logic. Set this up by adding the listener reference to your weblogic-application.xml file. To add the listener reference, add the following code to the weblogic-application.xml file in your application, which by default is located in <workspace-directory>/src/META-INF.
Once this listener is added, JDeveloper automatically registers the SDO service
application name JBOServiceRegistry_<appname> into the fabric service
registry in the composite.xml.
Toplink Development
Working with Toplink report query (7608075)
Follow the below steps when working with Toplink POJO and report query,
Create a wrapper class with the attributes needed in report query.
Generate accessors.
Expose the query to SessionBean
Change the return type of the method in SessionBean accordingly (the wrapper
class name).
Persisting into detail table (7645015)
The recommended method when persisting into a detail table is to use the Create
operation and mergeEntity method.
ADF table (7640738)
Avoid including the relational attributes in ADF tables.
Team Productivity Center
Switching to a different Team Productivity Center server
during the same JDeveloper session fails (7715433)
Attempting to connect to a different Team Productivity Center Server in the same JDeveloper session will fail if you are using JDeveloper Studio Edition. The workaround is to restart JDeveloper.
User with administrator permissions is not able to create/modify
team queries (8430322)
Team Productivity Center users are not able to create or modify team queries, but only user queries. The workaround is for Team Productivity Center administrators to add themselves to a team, then add queries for use by the team.
OK button in select status not activated (8398589)
Users may encounter unexpected results while using the search field in the Bug DB to search for a specific status type. Once the Select "Status" dialog has returned the status that the user searched for, the OK button is not activated until the user selects the status from the list of values returned. If the user does not select the status, the OK button is not active. The workaround is to select the desired status, then click OK.
Team Productivity Center attachments open in Windows default
application, not JDeveloper (8407888)
Users who open an attachment associated with a Team Productivity Center workitem on Windows are presented with the Windows save/open dialog. If they choose to open the file, it opens in the default Windows application for the file type, not in JDeveloper. For example, an HTML attachment saved with a Team Productivity Center workitem will open in the user's default browser, not in JDeveloper's HTML editor. The workaround is to save the file, then open through JDeveloper.
The JIRA connector needs support of operator set for workitem
fields at field level (8421679)
Users who create a query in JIRA may encounter unexpected results regarding the workitem field in searches. After selecting the first criteria, the operator defaults to Like. When the user clicks Search, they may see an error screen informing them that the Like operator is not supported in JIRA search.
The JIRA connector does not support "Not Equals" in multiple
value searches (7411881)
Users who create a query in JIRA may encounter unexpected results when using multiple values in the same search. For example, a query with the following values will not return the expected results:
Status Not Equal Closed
Status Not Equal Resolved
The expected results would be to return all issues that are not marked either Closed or Resolved. At present, queries with individual values will return the expected results; that is, a query with the value Status Not Equal Closed will return all issues that are not marked Closed. The workaround is to query with individual values.
Non-privileged users cannot query MS project repository
based on project names (8406073)
Non-privileged users who attempt to query a Microsoft Project repository may encounter unexpected results if they base their query on project names. When a user does not have sufficient privilege in MS Project, the project names are not visible to that user, and the connector will not display them to be queried against. The workaround is to query by resource name or by date.
OPTC.WAR deployed on Tomcat server cannot be used on Weblogic
server (8499532)
Once otpc.war is deployed or installed using Oracle Team Productivity Center Installer on an Apache Tomcat server, it cannot be moved/used on a Weblogic (WLS) server, or vice versa.
This is because Team Productivity Center does not bundle eclipselink libraries
to otpc.war when installed on Web Logic Server, because Web Logic Server already
shipped the libraries. In fact, bundling eclipselink libraries on otpc.war (in
otpc/WEB-INF/lib folder) will cause problems on WLS installation. See "Option
1: Leave shipped module as is - Recommended" on http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
Since eclipselink libraries don't come with Tomcat out of the box, Team Productivity Center Installer bundles them in otpc.war deployment.
Users will need to run a new TPC installation against each type of application server.
Note: Users can still move the deployed otpc.war from one application server to another, providing the application servers are from the same vendor (i.e. tomcat to tomcat, or WLS to WLS). They cannot move the deployed otpc.war from one vendor's server to a different vendor's server.
Standalone WLS 10.3.0 users need to ensure persistence
files are present (8588599)
Users who install Oracle Team Productivity Center on standalone Web Logic Server
10.3.0 have encountered problems running WLS, because after installation of
Team Productivity Center, the persistence files javax.persistence_*.jar
and org.eclipse.persistence_*Jar are not present under the /modules directory.
Users of standalone Web Logic Server 10.3.1 and users of the integrated Web Logic Server are not affected.
Suggested workaround is to upgrade to standalone WLS 10.3.1. If this is not
possible for some reason, make backups of the persistence files before installing
Oracle Team Productivity Center, and then copy them back after installation.
ADF Desktop Integration
Inserting
Excel rows into an ADF read-only table component (7626970)
Inserting an Excel row into an ADF Read-only Table results in a new Excel row that behaves as if it were part of the downloaded data set. In fact, the new row exists only in Excel.
To avoid this issue, use ADF Table instead.
Excel
validation and ADF table component's placeholder row (7509432)
Excel validation does not get applied to the placeholder row in an ADF Table component that contains data.
Known
limitations on changing ADFdi components at runtime
Moving a Column in a Runtime ADF Read-only Table Component (6196783)
If the user of the worksheet containing a Read-only Table component uses Excel's
cut-and-insert operations to move a column to be the leftmost column of the
table, an exception occurs on the next download. To resolve the situation,
the user should close the workbook without saving the changes.
Change Tracking After Moving a Column to the End of an ADF Table Component (6032482)
Change tracking is disabled if an end user moves a column to the end of an ADF Table component at runtime.
Deleting an Integrated Excel Worksheet at Runtime (6161839)
Oracle ADF Desktop Integration does not support the deletion of integrated worksheets at runtime.
If the user deletes an integrated worksheet, un-handled exceptions will occur.
Workaround: close the workbook without saving any changes.
Switching
an integrated Excel workbook from test mode to design mode (7134292)
Summary: Unhandled Excel exception when returning from Test mode to
design-time mode if Excel filtering is applied to a table.
Steps:
Create a workbook with a table
Click the run button to enter test mode
Select the header row of the table
Enable Excel filtering ("Sort & Filter" in the Home tab)
Use Excel filter to display a subset of the rows in the table
Click the Stop button to return to design-time mode
At this point, an un-handled exception occurs. Workaround: To resolve the situation, dismiss the error dialog and remove
the filter from the table. Then, click the Stop button again to return to design-time
mode.
Microsoft
Excel always prompts users to save integrated Excel workbooks (6148067)
Microsoft Excel prompts an end user to save an Excel workbook that has been configured with Oracle ADF functionality (an integrated Excel workbook) even if the user has not modified the Excel workbook after opening it.
This is expected behavior because the Oracle ADF Desktop Integration module modifies an integrated Excel workbook each time an user opens it.
Select
components in web pages do not respect z-order as expected when page displayed
from dialog actions (7205486)
Summary:
Select components in web pages do not respect z-order as expected when the page is displayed from Dialog actions.
Steps:
Create an integrated workbook with a button that invokes a Dialog action
On the web page displayed by the Dialog, include an HTML "select" component as well as some other HTML components.
Use a "div" to overlay the components and make them appear to be in a disabled state
When this page is displayed in a normal web browser, the div performs as expected. When it is displayed in the .NET Web Browser control used in the Dialog action, the "select" control appears on top of the div instead of beneath it.
Workaround:
To avoid this problem, use web page control types that are not affected by the problem.
ADFdi
Excel context menus do not hide or show properly (7511508)
Microsoft Excel does not invoke the "before right click" event when a user invokes a context menu from a keyboard. Users should use either the keyboard or the mouse's right-click button to invoke a cell's context menu. Do not use both in the same user session. This behavior occurs at design time and runtime in integrated Excel workbooks.
ADF
button components and Excel zoom level (8305907)
Summary: Excel disables ADFdi Button components in integrated worksheets
when "zoom" is set to any value other than 100%. Workaround: Set Excel's Zoom level to 100% so that ADF Button components
can function correctly in integrated Excel workbooks.
Conditional
formatting in integrated Excel workbooks (7639699)
Oracle ADF Desktop Integration does not support the conditional formatting features provided in Excel by clicking Home > Conditional Formatting.
Failure
details for foreign key violations not displayed properly (8262587)
Users may encounter unexpected reports of errors under certain circumstances during the Upload operation for an ADF Table component. The Upload operation processes rows in batches. After posting changes from a batch ADFdi executes the action specified by the CommitBatchActionID. Errors that occur during the commit action may continue to be reported on subsequent batch commit actions, even though those batches of records do not contain the error.
Workaround: End-users should resolve the errors from the first failed
batch and then retry the Upload operation.
Server-side
row set can be positioned on wrong row when DoubleClickActionSet invoked on
ADF read-only table component (8272539)
An ADF Read-only Table component only caches the original row set index in an integrated Excel workbook. Invoking a DoubleClickActionSet on an ADF Read-only Table component results in an attempt to position the server-side row using the cached row index.
If the server-side row set changed in between the time the ADF Read-only Table component caches the original row set index and the DoubleClickActionSet is invoked, the server-side can be positioned on the wrong row. Workaround:
Consider using an ADF Table component instead.
Known issues involving workbook download
Customization Error When Attempting to Download an Integrated Excel Workbook via Internet Explorer (7146589)
Internet Explorer displays a customization error when a user attempts to download an integrated Excel workbook if the web page link references the integrated Excel workbook as follows:
excel/testp.xlsx
Make sure that the web page link references the integrated Excel workbook as follows:
/excel/testp.xlsx
Error Text:
Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: Customization does not have the permissions required to create an application domain. ---> System.Security.SecurityException: Customized functionality in this program will not work because the location of <url> is not in the Office Trusted Locations list, or all trusted locations are disabled. Contact your administrator for further assistance.
Downloading an Integrated Excel Workbook with parameters (7503854) Summary: opening a workbook immediately when the download URL includes
query string parameters results in an error:
Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: Customization does not have the permissions required to create an application domain. ---> System.Security.SecurityException: Customized functionality in this program will not work because the location of <url> is not in the Office Trusted Locations list, or all trusted locations are disabled. Contact your administrator for further assistance.
Workaround: Save the workbook prior to opening it. Solution: Install the "Excel 2007 hotfix package for February 24,
2009" to resolve this issue: http://support.microsoft.com/kb/966310
Getting customization exception when workbook URL > 256 chars (8758240) Summary: Open a workbook with a URL longer than 256 characters results
in an error: Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException:
Customization does not have the permissions required to create an application
domain. ---> System.Security.SecurityException: Customized functionality in
this program will not work because the location of is not in the Office
Trusted Locations list, or all trusted locations are disabled. Contact your
administrator for further assistance. This problem only occurs when accessing
the URL from Internet Explorer. Workaround: Use a shorter URL and save the workbook to local storage
before opening. Alternatively, use Firefox to access the URL.
Using
variableUsage element causes null pointer exception in ADFdi remote servlet
(6377073)
Summary:
ADFdi does not support variables in the page definition declared with the syntax of variableUsage. Details:
If the developer creates variableUsage in the ADFdi-related page definition, it will produce NullPointerExceptions in the server at runtime. Workaround:
Instead create variables using the <variable> element in the page definition.
Restore
server context and ADF table component's upload action (8402634)
Problem description
Download and make changes to an ADF Table component with a dynamic column. Save, close and reopen the integrated Excel workbook. Invoke the ADF Table component's Upload action. The ADF Table component's Upload action attempts to validate the list of columns before server data context (RSDC) can be restored by invoking a custom method that restores the data context of a dynamic view object.
Workaround:
In the action set that contains the ADF Table component's Upload action, first invoke a custom method action that does nothing. Invocation of this custom method action allows RSDC to restore the view object. The ADF Table component's Upload action now executes as expected.
ADF
Faces dialog framework (7510296)
The web browser control that renders web pages invoked from integrated Excel
workbooks does not support pages built with the ADF Faces dialog framework.
Avoid building pages with the ADF Faces dialog framework. If you cannot avoid
building pages, avoid invoking links from pages you build with the ADF Faces
dialog framework.
Known issues with the design-time property inspector and expression builder features
The property inspector and expression builder features in the ADFdi Designer
are driven off of the saved component metadata. As a result, there are some
known issues when dealing with new objects or values. In each case, the workaround
is to save the object and then reopen.
Sample issues:
New components in the expression builder (6314302) - An expression builder invoked from a newly-inserted ADF table-type component's property that supports EL expressions does not display the newly-inserted ADF table-type component in the Components node of the expression builder.
Cannot select UniqueAttribute for a new Table (7269921) - An error message appears requesting that you first specify a value for the ADF Table component's TreeID property when you attempt to set a value for a newly-inserted ADF Table component's UniqueAttribute property. This error message appears even though a value is set for the TreeID property.
Time
zones and java.sql.Date Java data type (8494449)
Oracle ADF Desktop Integration does not properly support the java.sql.Date
Java data type across time zones. For example, an end user enters January 3,
2009 in an integrated Excel workbook. Subsequently, this may change to January
2, 2009. Use a different Java data type, such as java.sql.Timestamp, for date-time
data.
Known
issues with ADFdi list of values components
An empty choice list can cause null pointer exceptions (8571395/8571474) - Avoid empty choice lists
Limitations on Dependent List of Values Configuration (8270742/ 8267114)
Oracle ADF Desktop Integration requires that items in a dependent List of Values component remain constant across all rows of an ADF Table component because Oracle ADF Desktop Integration caches items that appear in a dependent list of values.
Dynamic Column in an ADF Table Component and List of Values (8421275)
Oracle ADF Desktop Integration does not support the rendering of a list of values in a dynamic column of an ADF Table component.
Dependent List of Values using ADF Desktop Integration List of Values Components Show Blank Items (7874871)
A dependent list of values using ADF Desktop Integration List of Values components shows blank items for all values if the view object's query has bind variables where the value (static) is passed to the bind variable in an action invoked by the worksheet Startup event.
The Oracle ADF Desktop Integration servlet (adfdiRemote) does not support participation in the ADF page lifecycle. An executable binding does not refresh as desired if changes are made to the Refresh attribute of an invokeAction element in a page definition file. Leave the default value (deferred) of the Refresh attribute in place.
Known
issues with SSL
Authentication issue when using SSL for client-server communication (8584875)
When a workbook is configured to use SSL to secure the communication between
the ADFdi and the web application, end users are prevented from successfully
authenticating by an error message and/or the login dialog not closing automatically
as expected. Non-SSL communication with the same web application works as
expected.
Integrated Excel Workbooks and HTTPS (7117108)
Attempts to connect to a web application from an integrated Excel workbook
over HTTPS result in an error if the certificate is not present on the client
machine. Error text:
The underlying connection was closed: Could not establish trust relationship
for the SSL/TLS secure channel. The remote certificate is invalid according
to the validation procedure.
Tamper check reports a "false positive" failure
in certain situation (8530721)
For workbooks with multiple integrated worksheets where at least one worksheet
title is altered by the user or set dynamically from a resource expression,
the tamper check performed in the next Excel session after the title change
may report a tamper check failure even though no tampering has occurred. The
workaround is to avoid altering the worksheet titles at runtime.
ADF Faces and Data Visualizations
Supported platforms
ADF Faces is currently supported in the following user agents (i.e. browsing platforms):
User Agent
Windows
Solaris
Mac OS X
Red Hat Linux
iPhone OS
Known Bugs and Limitations
Internet Explorer 7
7.0
not supported
not supported
not supported
not supported
In some layout-components, images in commandImageLink are clipped. Application Developer can get fix it by setting styleClass="AFLinkIEWorkaround" on the af:commandImageLink component.
Firefox 2
2.0.0.2+
2.0.0.2+
2.0.0.2+
2.0.0.2+
not supported
No cursor on text fields in popup or table (Bugzilla bug 226933)
Firefox 3
3.0+
3.0+
3.0+
3.0+
not supported
Safari 3
3.1.2+ (desktop)
not supported
3.1.2+ (desktop)
not supported
3.0+ (mobile)**
AF:richTextEditor does not function properly in
WYSIWYG mode (Webkit bug 7138), many keyboard shortcuts do not work properly,
AF:inputNumberSlider and AF:inputRangeSlider not working properly on iPhone
(bug 8304518)
Google Chrome**
1.0+
not supported
not supported
not supported
not supported
When users hit Ctrl-N or Ctrl-T to launch multiple Chrome browser windows and then copy the URL to bring up pages with active data, active data doesn't work correctly.
** Indicates that the browser is supported but not certified
Internet Explorer 8 is neither supported nor certified. If you must use IE8, set the compatibility view settings in your IE8 browser to ALL. In IE8, go to the Tools menu -> Compatibility View Settings and check the last checkbox "Display All Websites In Compatibility View".
Support for JAWS 8 and Bi-Directional languages (such as Arabic or Hebrew) is only available in IE7.
You should disable or remove third party browser add-ons because they have the capability to negatively interfere with the execution of the browser and the ADF Faces client framework.
Known limitations
Hot Keys Application developers must be cautious when assigning access keys to menus. Hot keys may be intercepted by various browsers or even the operating system. One such hotkey, ALT-D, will send focus to the address bar in both IE and FireFox 2. For this hotkey, we have removed the references in our demos. But many more hotkeys may be restricted so it is a good idea to try them out on all of your supported browsers.
Primary Keys from model ADF Faces components expect applications to use primary keys on the model which are pre-populated for new records and do not change with any record updates.
Setting Locale on f:view If locale attribute is set on the f:view tag (e.g. f:view locale='ko_KR') then model project resource bundles don't pick up the specified locale on initial render (subsequent renders of the page work fine). To workaround this instead of using the locale attribute on the view tag you can create a PhaseListener for the PhaseId.RESTORE_VIEW phase and in the afterPhase method you can set the desired locale on the UIViewRoot. You can use the pagedef to register the listener for a specific page or use adf-settings.xml or faces-config.xml to register the listener globally.
Ctrl+N support The application user may experience incorrect behavior if they use Ctrl+N to open a new window from their application, press the refresh button on their browser toolbar (i.e. F5), copy and paste a URL for an ADF Faces app from one window to another, or use the ADF Faces dialog framework to open new browser windows. If these usecases are critical to you, please set the following context parameter in your web.xml file. We expect to support the Ctrl+N use cases by default in a future release.
Popup, Dynamic Region and Automatic Partial Page Rendering ADF Faces and Controller do not support Automatic Partial Page Rendering for dynamic regions within popups. Set the "ChangeEventPolicy" attribute to 'none' on the iterator bindings and value bindings (see "Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework 11g Release" , Chapter "Automatic Partial Page Refresh"). Instead, use ADF Faces Partial Page Rendering (see "Oracle Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework 11g Release" , Chapter 7 "Rendering Partial Page Content").
Application View Cache The Application View Cache won't work for any page where the rendering of the component tree causes the structure of the component tree to change temporarily. Since this is often the case and the application developer has no way of telling when this will occur, USE_APPLICATION_VIEW_CACHE should never be used. It also only helps initial render performance and does not help the session size.
ADF Faces Stamped Components with MDS ADF Faces components do not
support persisting customization changes to MDS if the component is contained
inside of (anywhere in the subtree of) AF:forEach or AF:iterator tags. This
limitation is because, while such structure results in multiple component
copies in the view tree, they have a single representation in the jsp documents.
MDS based customization and '$' in id When MDS validates a page modified by the ChangeManager, validation will fail if any of the id attributes in the page contain a "$' because "$" isn't a valid character in an XML ID attribute. Page authors who have configured their application for customization via MDS based ChangeManager must ensure either of the following
None of the id attributes of the tags in the jspx/jsff page where customization will occur contain '$'
If any of the components on the page has an id attribute that contains '$', MDS persistence must be turned off for all persistable components on that page. Turning off MDS persistence on a page can be achieved by setting the dontPersist attribute on all persistable components on the page.
Corrupted CSS file If your page does not render properly so that it appears that the CSS style sheet is not properly being applied, there are two workarounds:
Delete the generated CSS file on the server and restart the server. Have all users clear their browser cache. Next time the server is accessed, a new
CSS file will be generated, and chances are that it will be a valid CSS file.
If workaround #1 doesn't suffice, disable content compression in the web.xml file
Firefox does not print Flash content, which is the default imageFormat for DVT Graph and Gauge. Applications should set the imageFormat to PNG for use in printable pages when the browser is Firefox. Flash content, including ADF DVT Graphs and Gauges, prints fine when the browser is IE.
There are known issues using Flash graphs in BiDi locales. The workaround is to use PNG graph image format.
(Bug 8568290) - The TagDoc for the imageFormat property of the Graph tag incorrectly defines the value as an EL Settable String. To change imageFormat at runtime your expression language needs to evaluate to a java.lang.Number rather than a java.lang.String. The correct constants for the imageFormat Types are in the oracle.adf.view.faces.bi.component.dataView.UIDataView class with the following constants available:
IMAGE_FORMAT_PNG
IMAGE_FORMAT_SVG
IMAGE_FORMAT_AUTO
IMAGE_FORMAT_FLASH
IMAGE_FORMAT_PNG_STAMPED
(Bug 7620495) - When creating a generic Application using the ADF Data Visualizations
Core tag library, the required ADF DVT Core Runtime Library is not deployed
with the application, causing ClassNotFoundExceptions at runtime. To workaround
this issue, edit the Project Properties to explicitly add the following three
(3) JARs to the classpath entries: dvt-client.jar, dvt-trinidad.jar, and dvt-utils.jar.
All three Jars are available in the <Oracle_home>/jdeveloper/modules/oracle.adf.view_11.1.1
directory.
Users of the ADF DVT simple Graph tags listed in the table below are advised to use the following new syntax going forward:
In order to store edits the PivotTable needs to bound to a DataControl/Model that supports writeback operations. A Rowset based DataControl, like the BC4J based DataControl is transformed into a cube and due to the transformation cannot support writebacks.
PivotTable does not reliable capture edits using input controls other than inputText.
In the browsers Chrome and Safari custom cursors do not appear.
When using Internet Explorer in BIDI mode the PivotTable scrollbars can sometimes reset to their original position.
User made selections can override cellformatting information in the datacells.
Cellformat text styles definitions are currently ignored.
(Bug 8461943) - If the application has been configured to store personalization state in the MDS Repository AND the following conditions are met: 1) only a single data item attribute is mapped to a Pivot Table Binding, and 2) the "No Label" option is specified for that single data item attribute, then a NullPointerException may be thrown at runtime when the Pivot Table Binding tries to save model state changes (due to a pivot, drill, or sort operation) as personalized page state. The workaround is to remove the "No Label" option from the Pivot Table Binding's single data item attribute.
ADF DVT Gantt
In the browsers Chrome and Safari custom cursors do not appear.
No actionEvents are fired on a custom rightmouse menu on the chart area using the chartPopupMenu facet.
ADF DVT Geographic Map
(Bug 8553837) - The Binding XML for a <dvt:mapPointTheme>
can get corrupted if a developer changes an existing iterator binding through
the design time dialog. The workaround is to either edit the Binding XML source
directly in the PageDef, or else delete the <dvt:mapPointTheme>
and recreate it.
ADF Enterprise Manager Integration
Create ADF connections (8541196)
Problem Description: In Enterprise Manager (EM), J2EE application
home page -> Deployment Menu -> ADF > Administration > ADF
Connections page, Connection Types strings in dropdown list are cached on server,
so even if client locale is changed, it always returns the cached strings for
locale with which the user accessed the page for first time.
For example, if first user accesses this page using Japanese language, when
2nd user accesses this page using English, Connection Types strings in dropdown
list are displayed in Japanese, if 2nd user can't read Japanese, user is unable
to create connection.
Workaround: User can switch to EM's System MBean browser, then use the
MBeans there for creation of the child MBeans. After MBean is created, user
can switch back to ADF-EM Conn UI to edit the connections.
Detailed Steps:
1. Click "Application Deployment" menu, then choose "System MBean Browser".
2. In the System MBean Browser, go to "oracle.adf.share.connections" mbean.
3. In the right side, switch to "Operations" tab, then click "createConnection" operation.
4. In the "Operation: createConnection" page, enter "Connection Type" and "Connection Name", then click Invoke. Connection will be created.
Note: For the supported Connection Types values, please look at the "Connection Types" attribute of the parent ADFConnection MBean. 19 MBean types are supported.
5. After connection is created, switch back to the ADF-EM Conn UI to edit the
connections.
Cached ADFc settings in adf-config.xml (8495743)
Problem Description: The properties in the ADFc section of adf-config.xml are not refreshed when the values are updated through the Enterprise Manager MBean browser.
Workaround: Restart the server or redeploy the application to force the changes made through the MBean browser to register in the adf-config.xml.
ADF Business Components configuration (8565762)
Problem Description: In EM, ADF > Administration > Business Components
page, if you select any application module other than the first application
module, clicking on apply refreshes page and tabbed ui points to details of
first application module. But the tree doesn't refresh, it still points to original
selected application module.
Workaround: Click on the application module again to see corresponding
details.
Service connections table doesn't refresh when saving using
the apply button (8563700)
Problem Description: In EM, J2EE application home page -> Deployment
Menu -> ADF > Administration > ADF Connections page, consider there
are some saved, and some un-saved invalid service connections in service connection
table. On clicking Apply button, an error message to save invalid service connections
is displayed, but the UI doesn't refresh to remove unsaved connections from
service connection table.
Workaround: Any user action which causes UI refresh, like click on Apply/Revert
button, create connection, contract-expand panel box containing service connection
table.
Incorrect label is displayed for the ADF metric "Referenced
Module Recycled" (8540118)
Problem Description: In EM, J2EE application home page -> Deployment
Menu -> Performance Summary page, navigate to the metrics palette. An
incorrect label is displayed for the "Referenced Module Recycled" metric.
Workaround: The incorrect label is "Referenced Module Reused". It should be "Referenced Module Recycled".
The ADF application module pool metrics details page always
display details of first application module (8553718)
Problem Description:In EM, J2EE application home page -> Deployment
Menu -> ADF -> Performance page, the detail data only shows details
for the first application module.
Workaround: Navigate to the J2EE application home page -> Deployment
Menu -> Performance Summary page to view details of the Application Module.
ADF Controller
ADFc save points and dialogs
In this release, ADFc save points created while a dialog window is shown are not correctly supported. If an implicit save point is created while a dialog window is shown, a severe warning will be written to the application log. For explicit save points, a runtime exception will be thrown. If an inline popup is shown when a save point is created, the inline popup will not get restored when the save point is restored.
viewScope / pageFlowScope replication within a cluster
In a very narrow set of cases when an application is deployed to a cluster
it's possible for a newly created viewScope or pageFlowScope to not be replicated
to another cluster node . This can result in an unexpected NullPointerException
if a subsequent request is serviced by another cluster node. If this situation
is encountered the workaround is to have the application explicitly mark the
new scope dirty. There are two ways to do this. The first is to
place an object into the scope like this:
Map<String, Object> vs = FacesContext.getCurrentInstance().getViewScope();
vs.put("foo", "bar");
Or, the application can call markScopeDirty() like this:
Map<String, Object> Vs = FacesContext.getCurrentInstance().getViewScope();
ControllerContext.getInstance().markScopeDirty(Vs);
Although the above example is show with the viewScope that same technique can
also be used with the pageFlowScope.
ADF Business Components
Problem editing JDBC positional bind variable with expression-based
default value (8581246)
Problem
Creating a JDBC positional bind variable with an expression-based default value will raise a design time error.
Workaround
1. Copy the invalid xml fragment from the error dialog.
2. Open the Source tab and paste the <Variable> tag as an immediate child
of the <ViewObject> tag.
3. Save and close the file.
4. Reopen the editor.
5. Further updates to this specific bind variable must also be made from the
Source view or else the same error will occur.
Using an ADF-BC service with the SOA platform (8516162,
8549404)
Before you can deploy an ADF Business Components service and invoke the service from a BPEL process in a fabric composite application, the ADF Business Components service has to be registered in the fabric composite:
2. In the fabric composite.xml, you will use <applicationName>_JBOServiceRegistry as the registry name. For details, see release note "Oracle SOA Suite Integration with an ADF-BC Service."
Runtime exception appears when executing service interface
methods (8235654)
When the Fusion application invokes a service method on an service-enabled application module, it is possible to intermittently receive an oracle.jbo.service.errors.ServiceException. This happen when Oracle WLS leaves the ADFContext on the thread local and the thread local gets reused by a new application. To prevent this exception, you can add a ServiceContextInterceptor annotation to your application's service interface implementation class. This web service annotation caches the current ADFContext before calling the service method and then restores the ADFContext after the service method is called. To enable the annotation, add the following bold lines to the service interface implementation class file in your ADF Business Components project:
import weblogic.javaee.CallByReference;
// ---------------------------------------------------------------------
// — File generated by Oracle ADF Business Components Design Time.
// ---------------------------------------------------------------------
@Stateless(name="hrmodel.oracle.hr.am.common.HRModuleServiceBean", mappedName="HRModuleServiceBean")
@Remote(HRModuleService.class)
@PortableWebService(targetNamespace="http://example.com/hrmodel/oracle/hr/am/common/",
serviceName="HRModuleService", portName="HRModuleServiceSoapHttpPort",
endpointInterface="hrmodel.oracle.hr.am.common.serviceinterface.HRModuleService")
@CallByReference @Interceptors(ServiceContextInterceptor.class)
public class HRModuleServiceImpl extends ServiceImpl implements HRModuleService
...
Cannot deploy workspace with both WebService and PortableWebService
in same project (8374643)
If you have a single project containing a java class with a web service annotation (@WebService) as well as an ADF Business Components service interface (which uses the @PortableWebService annotation), you will encounter a deployment error.
The workaround is to either split the Java class with a web service annotation
into a separate project, or alternatively adjust the deployment profile files
so the WAR profile contains just the web service and the Business Components
Service Interface profile contains just the Portable Web Service by unchecking
the appropriate checkboxes in the profile editor.
Enabling MTOM support for SOAP protocol clients
The SDO data objects of the service-enabled application module maps BlobDomain/ClobDomain
to javax.activation.DataHandler. DataHandler properties will be passed as attachments
during SDO data object marshalling/unmarshalling. To enable MTOM support for
your SOAP protocol, you need to manually enable this support on the service
interface implementation class (for example, StoreFrontServiceImpl.java). To
add the @MTOM annotation, click in the source code for the service interface
implementation class, then open the Property Inspector and select Enable MTOM
in the Web Services section. This will allow you to test MTOM support using
a custom method in the application module. The method must operate on a
ViewRow with BlobDomain/ClobDomain attribute.
ADF Task Flow
Applications with multiple WARs (8395585)
If your ADF J2EE application (EAR) contains multiple web application modules (WAR files), and more than one contains ADF task flows, then you may get unexpected behavior due to one web application using another one's same-named task flow XML file (the problem is most likely to occur with the adfc-config.xml file since typically each web application has one). You can avoid this problem by setting a distinct "web app root" for each web application (WAR). Only at most one web application may have no web app root setting. To set the "web app root" for a web application you must add an XML file called META-INF/adf-settings.xml to the WAR under WEB-INF/classes with contents like the following:
The value of the rootName attribute can be any name which uniquely identifies the web application (war) within the overall application (ear).
In JDeveloper the new file can be added as follows:
Expand the web application project in the Application Navigator
Right click on "Application Sources" and select the "New" item
Select "XML Document" and click OK
Type in "adf-settings.xml" as the file name
Click the "Browse" button, select the project source directory, click the
"Create new subdirectory" iconic button at the top right corner, type in directory
name "META-INF" and click OK, then click Select
You should now have file name "adf-settings.xml" and directory name "<project
source directory>/META-INF"
Click OK to create the new file
In the Source editor, paste in the above XML and put in a suitable value
for the rootName attribute (this is known as the "web app root" setting)
Make sure the deployment profile for the Web application includes the new
META-INF/adf-settings.xml file under WEB-INF/classes.
ADF Customization (Seeded and User Customizations)
Modification of connections is not supported for the Customization
Developer Role
The creation, deletion, and modification of connections (both application connections
and IDE connections) is not supported for the Customization Developer role in
JDeveloper. Though some of the connections-related operations are enabled
in the Customization Developer role, do not attempt use them in the Customization
Developer role. Use of these operations may produce unexpected errors.
You should always configure connections in Default role before opening an application
in Customization Developer role.
Override bundle must be packaged manually in MAR
When you create or modify resource keys in the JDeveloper Customization Developer role, your changes are saved to an application-level override bundle in XLIFF format. Currently, when an application is packaged in JDeveloper, it does not include the override bundle. If you plan to use "design time at runtime" capabilities to add or edit resource keys in the override bundle at runtime, you must include the override bundle in the MAR package. To include the override bundle in the MAR package so that your changes are available to the application at runtime, you must explicitly add the override bundle to the MAR deployment profile.
To add the override bundle to your MAR deployment profile:
Open the Application Properties dialog (Application > Application Properties), and click Deployment.
Select your MAR deployment profile, and click Edit. If you don't already have one, click New, select MAR File, and click OK.
In the Edit MAR Deployment Profile Properties dialog, click User Metadata (under Metadata File Groups).
Click Add, and enter the path to the directory that contains the override bundle (for example, \app-name\resourcebundles).
Now click Directories (under User Metadata), select the xliffBundles directory to include it in the MAR, and click OK.
MAR packaging could create wrong namespace mapping under
<mds-config> in adf-config.xml
The namespace configuration under <mds-config> for MAR content in the adf-config.xml file is generated based on your selections in the MAR Deployment Profile Properties dialog. If you select a parent node and then deselect some child nodes, the namespace is generated for the parent node only, which might not be the intended behavior if you want to generate namespace mappings for only the child nodes. When the namespace is generated for the parent package, the documents under deselected sub packages are also looked up from the MDS repository at runtime. To avoid ambiguity in the namespace mapping, you should deselect all customizations, and then directly select the specific packages that you want to seed in the MDS repository.
Packaging metadata from multiple web projects in an application
Although uncommon, an enterprise application (packaged in an EAR) can contain multiple web application projects (packaged in multiple WARs), but the metadata for all these web applications will be packaged into a single metadata archive (MAR). The metadata contributed by each of these individual web applications can be global (available for all the web applications) or local to that particular web application.
To avoid name conflicts for metadata with global scope, make sure all metadata objects and elements have unique names across all web application projects that are part of the enterprise application.
To avoid name conflicts and to ensure that the metadata for a particular web application remains local to that application, you can define a web-app-root for that web application project.
The web-app-root is an element in the adf-settings.xml file for a web application project. The adf-settings.xml should be kept in the META-INF directory under the public_html directory for the web project. The following example shows the contents of a sample adf-settings.xml file:
In this example, the adf-settings.xml file has a web-app-root element that defines the rootName as order.
If your enterprise application has only one web application project then there is no need to define a web-app-root element. If your enterprise application has multiple web application projects, then you should supply a web-app-root for all the web applications except one, without which the deployment would fail. For example, if you have web-application1, web-application2, and web-application3, two of these web application projects must define a web-app-root to preclude any name conflicts.
No MAR support for multiple web projects with duplicate
metadata
At present, there is no support to package customizations from multiple web application projects as part of the MAR when project-specific customizations in each project result in duplicate document name and package name.
For example, say you have an EAR that contains two web application projects: ViewController1 and ViewController2. If both of these projects contain a metadata object called public_html/oracle/page1.jspx that contains customizations, then it is not possible to package the customizations of page1.jspx from the different web application projects as part of the same MAR even though you specify the web-app-root for the web application projects.
Semantics of the getValues() method
The semantics of MDS's customization class' getValues() method has changed. When getValues returns null, it with throw an exception (and not allow customizations at that layer to be applied. In additions the UserCC or ADFUserCC classes now return null when the current user is "anonymous". This way, for unauthenticated users, MDS will throw an oracle.mds.exception.NoTipCustomizationLayerException exception indicating that the user is not logged in and can't make customizations.
Any site level customizations that have been applied when the user is unauthenticated (is "anonymous") will remain once the user authenticates.
Deprecation of ADFUserCC
ADFUserCC has been deprecated so please change your code to use UserCC.
Persisting saved searches for the query component
In order to persist saved searches for the query component, you must update your adf-config.xml and place the following code within the mds-config element after the cust-config element.
<persistence-config>
<metadata-namespaces>
<namespace path="/persdef" metadata-store-usage="MAR_TargetRepos"/>
</metadata-namespaces>
<metadata-store-usages>
<metadata-store-usage id="MAR_TargetRepos" deploy-target="true"
default-cust-store="true"></metadata-store-usage>
</metadata-store-usages>
</persistence-config>
ADF Security
Migrated 10.1.3 application fails to logout (8561424)
When you enabled ADF Security in a 10.1.3 application, your web.xml file will
map the adfAuthentication servlet using the URL pattern as follows:
This change to the servlet mapping in 11gR1 may prevent the adfAuthentication servlet from locating the target page after logging out. In this case, the browser will display a 404 Not Found error.
In order to allow the adfAuthentication servlet to complete the logout, you
can modify your migrated application using either of these options:
Option 1: Change the logout URLs that your pages contain to:
JDeveloper 11g changes the way ADF Security is implemented to improve the developer experience and application performance. After migrating a 10.1.3 application with ADF Security, you have the choice to either modify the application to use the new ADF Security runtime and design time support or to run the application with the 10.1.3 compatibility flag <contextEnv name="oracle.adf.security.metadata" value="false"/> in place.
Note that if you migrate your application and add the 10.1.3 compatibility flag, you will not be able to take advantage of the ADF security enhancements made in 11g. In JDeveloper 11g, ADF Security no longer supports the same set of 10.1.3 security permission checks. Consequently, securing the application no longer involves making grants for view/read access to individual ADF artifacts.
Specifically, in JDeveloper 10.1.3 ADF security did not support security metadata
and required explicit grants on page definitions, iterators, attributes, and
methods. In 10.1.3, the ADF runtime dynamically created the permission target
name to enforce page viewability, rowset and attribute read/update, and button
enable/disable. In JDeveloper 11g, bounded taskflows and pages not in bounded
taskflows are secured by default and the application developer creates explicit
grants to application roles. Additionally, in 11g, the application developer
can specify security metadata or use EL expressions or Groovy expressions to
secure attributes of entity objects and buttons.
Therefore, before choosing to add the 10.1.3 compatibility flag to your migrated
application, consider modifying the migrated application to use EL expressions,
Groovy expressions or security metadata to secure artifacts that need to be
secured. With ADF security in 11g, your application's migrated bounded task
flows and pages in unbounded taskflows will be secured by default and developer
grants can be made to application roles.
If you decide to run the migrated application with the 10.1.3 ADF Security runtime behavior, add the <contextEnv name="oracle.adf.security.metadata" value="false"/> compatibility flag to the adf-config.xml file located in the /adf/META-INF folder relative to the application. The sample below shows the adf-config.xml with the flag added:
Migration considerations for ADF security authentication
(8418902)
If you edited the web.xml file in your user interface project to enable ADF Security authentication, you may have added the adfSecurity filter element. This filter is no longer used by the ADF Security framework. When present in your web.xml file, you must remove the adfSecurity element. When not present, no ADF Security migration is required.
Open the web.xml file and remove the following adfSecurity <filter> element directly from the file:
Alternatively, you can double-click the web.xml to edit the contents in the overview editor. In the overview editor, select the Filter tab, highlight adfSecurity in the Filters list, and then click Delete.
MultiByte character user names and passwords cause authentication
to fail (8265819)
Form-based authentication in a Web application does not support multi-bye characters for j_username and j_password. To enable request encoding in JSPs, add the j_character_encoding as follows to your login form (in the ADF Security framework, the login form may be generated by the Configure ADF Security wizard).
where the "encoding you want" might be "Shift_JIS", for example.
ADF Swing
ADF Swing WebStart support
"Java Web Start" with BC4J as the model layer needs a "login dialog"
to be generated for JClient applications to prompt for the database credentials. The
Login Dialog needs to be generated using the Form wizard. WebStart is supported
without "login dialog" for bean datacontrol.
ADF layer security
ADF security in this release of JDeveloper 11g has limited support with
ADF Swing and customers who require ADF security to work completely
in ADF Swing, should wait for the next release of JDeveloper 11g.
Deployment Options
ADF Security
Work around to be followed
ADF Swing application run from JDeveloper
Works, no work around needed
N.A.
ADF Swing app deployed in jar files run from command line
Works with workaround
The following JVM properties need to specified when launching the swing application oracle.home - This is the directory where the JDeveloper
11g is installed. oracle.security.jps.config - This is the full path to your application jps-config file. You will typically find this under <application_dir>\src\META-INF folder. jps.authz - Default authorization to read the credential store wallet to retrieve the password.
If your Swing application is deployed as "application.jar", then On Windows, these properties would be specified on the java command line as
Java-jar application.jar -Doracle.home=c:\jdev11g\jdeveloper -Doracle.security.jps.config=c:\jdev11g\JClientApp\src\META-INF\jps-config.xml -Djps.authz=DEBUG_NULL
where, c:\jdev11g\jdeveloper is the dir where jdeveloper is installed. and C:\jdev11g\JClientApp is your application directory
On Linux / Unix, the command line would look something like
Java-jar application.jar -Doracle.home=/home/jdev11g/jdeveloper -Doracle.security.jps.config=/home/jdev11g/JclientApp/src/META-INF/jps-config.xml -Djps.authz=DEBUG_NULL
where, /home/jdev11g/jdeveloper is the dir where jdeveloper is installed. And /home/jdev11g/JClientApp is your application directory
ADF Swing app deployed using WebStart
Does not work
NA
Documentation and Tutorials
Updated af:resource information in chapter 19 creating
and reusing fragments, templates, and components
In section "19.5 Adding Resources to Pages", replace the paragraph with the following:
You should use the AF:resource tag to add CSS or JavaScript to pages, templates,
or declarative components. This tag is especially useful for templates and declarative
components because resources can only be added to the page (in the HTML head
element). When you can use this tag in templates and declarative components,
the resources will be added to the consuming page during JSP execution. If this
tag is not used, browsers may need to re-layout pages that use templates and
declarative components whenever it encounters a style or link tag. The resources
can be added to the page during any page request, but they must be added before
the document component is rendered.
The resource tag can be used with PPR.
During PPR, the following requirements apply:
URL resources are compared on the client before being added to the page. This ensures duplicates are not added.
CSS resources are removed from the page during a PPR navigation. The new page will have the new CSS resources.
In section "19.5.2 What Happens at Runtime: Adding Resources to the Document Header", replace the paragraph with the following:
During JSP tag execution, the AF:resource tag only executes if its parent component
has been created. When it executes, it adds objects to a set in the RichDocument
component. RichDocument then adds the specified resources (CSS or JavaScript)
to the consuming page.
Oracle Help for the Web (OHW-RC)
PPR-Navigation must be turned off in web.xml (7487061,7459002)
The PPR-Navigation flag is off by default in web.xml and must be off for OHW-RC.
If you use OHW-RC with an ADF Faces
Application and you want OHW-RC to share the accessibility settings that the
user sees in the ADF-Faces application, you should deploy OHW-RC together
with your ADF Faces app. Steps to deploy the two together are documented in
the Oracle Help Guide.
Accessibility and popups (8438073)
If supporting Accessibility users is required,
you should not use the popup feature in your help files:
If supporting accessibility users
is required, associative links should not be used in your help files
An associative link is a link that is associated with more than one target.
When the user selects an associative link in a topic, a list of all topics
associated with the link is displayed, and the user can choose a topic from
the list.
<a href="alink:worksheet">Related Topics</a>
Multiple locales (8561124)
If your OHW-RC server instance will be accessed
by more than 3 locales, you must update the cacheSize parameter in ohwconfig.xml
to match the number of locales that will be accessed.
Accessibility
JSP and HTML visual editor toolbar not keyboard
accessible (8351632)
When opening the visual editor you may not be able to see all the toolbar functions available and there is no visual indication [... or =>] that more toolbar functions are available. You can, however, expand the window wider to see them all.
Focus may be lost when running an offline database
report (8294671)
The report output is not always selected. When this occurs Ctrl+Shift+A to select the navigator does not work either. The workaround is to Alt+Tab out and back in again.
Cannot edit database table data in the table viewer using
the keyboard (8481190)
In the data tab of a database table in the Table Viewer you cannot use the keyboard to insert or delete rows, or to commit changes to the database.
The workaround is to use the SQL Worksheet to edit the table data, using SQL INSERT, DELETE, and COMMIT statements to insert rows, delete rows (using the primary key of the row in the WHERE clause), and commit changes.
Field labels in the database diff wizard not available
to a screen reader (8207740)
Screen readers are unable to correctly read the UI labels in the Diff wizard.
The workaround is to use the Generate SQL from Database Objects wizard, which is available from the New Gallery, to diff the objects in two databases.
Export table data dialog cannot be read by a screen reader
(7459062)
The Export Table Data dialog invoked from the context menu of a table, the data tab of the Table Viewer, a SQL Worksheet result set, or report output, cannot be read using a screen reader.
The workaround is to use a SQL query statement in the SQL Worksheet that produces the output required, then save that to a file.
Version banner database reports cannot be read using a
screen reader (7301211)
Database reports, available from the Database Reports Navigator, cannot be read in a screen reader.
Navigating between tabs of SQL Worksheet using the keyboard
(8567565)
The different tabs in the SQL Worksheet can be accessed in the following ways. Note: You cannot navigate directly from one tab to another.
Results tab. Activate the tab by running Execute Statement (F9) in the SQL Worksheet, then use Ctrl+Tab to navigate to it.
Script Output tab. Activate the tab by running Run Script (F5) in the SQL Worksheet, then use Ctrl+Tab to navigate to it.
Explain tab. Activate the tab by running Execute Explain Plan (F6) in the SQL Worksheet, then use Ctrl+Tab to navigate to it.
Autotrace tab. Activate the tab by running Autotrace (F10) in the SQL Worksheet, then use Ctrl+Tab to navigate to it.
DBMS Output. You cannot activate this tab, and there is no way to navigate to it. The workaround is to use SQL*Plus to get the information you want.
OWA Output. You cannot activate this tab, and there is no way to navigate to it. The workaround is to use SQL*Plus to get the information you want.
Accessing commit and rollback in SQL Worksheet from a keyboard
(6752383)
In the SQL Worksheet, you can use the following accelerators:
The ADF Faces AF:progressIndicator component provides notifications of progress
while processing long running tasks. This is accomplished by updating a progress
message (typically specifying the percentage of the task that has been completed)
on some regular polling interval. While these updates are visible to sighted
users, screen readers do not typically respond to these changes automatically,
making it difficult for blind users to monitor this progress. We hope to leverage
WAI-ARIA live regions in a future release to allow progress notifications to
be communicated to screen reader users.
Difficulty interacting with the create ADF Faces
table dialog (6789861)
Screen reader users may have difficulty interacting with the "Create ADF Faces Table" dialog. Users that are unable to complete this dialog may hit the Enter key to create the table component using the default settings and then may customize the table component using property inspector and structure pane.
ADF DVT Hierarchy Viewer (8374410, 8374542)
Developers running the JAWS screen reader may encounter difficulties using the Create Hierarchy Viewer dialog in their design time environment. The workaround is to edit the <dvt:hierarchyViewer> tag and the corresponding binding with the Source editor.
The Application Navigator Display Options are not keyboard accessible. They can only be reached via the dropdown menu which requires mouse navigation.
Refactoring dialog for renaming a Java class member
(6080130)
The Refactoring dialog for renaming a Java class member offers to show the extend of this operation in a preview window to allow the user to assess the impact. If the user decides it is OK to proceed the user has to press a button in this preview window to actually perform the refactoring operation. However, if you are using the keyboard only it is not possible to access this button. To workaround this issue deselect the option 'Preview' in the Refactoring dialog when using keyboard only.
Navigating between different help topic editors
(6784654)
When navigating between different Help Topic Editors, to get into the next editor you need to select the corresponding node in the table of contents navigator or return to JDeveloper in the case of a context sensitive help to open the wizard (or whatever you want the help on) and then press F1 to get to the help topic.
Tasks window (6788671)
The Tasks window, opened by selecting the menu item "Tasks" from the main menu
"View", allows the user to add filters to narrow the number of tasks displayed.
The construction of such a filter is done in the "Filter Tasks" dialog. However,
if using the keyboard only, it is only possible to add a new filter but not
to modify its configuration.
Using advanced search (6790898)
Using the Advanced Search context menu option from the Resource Palette, adding or removing of search criteria can only be done using the mouse. It is not keyboard accessible.
Editing table columns (8206320)
When editing table columns for a sf html readonly table, JAWS fails to read
the first column 'Display Label' data for each row in the table.
Deployment log details (8214814)
When an application is deployed from JDeveloper the deployment log details
all the events during deployment. It is not currently possible for JAWS
to read these details.
Swing designers (8216345)
It is not currently possible to read from the Swing Designers using JAWS.
Removing or adding code templates (6792631)
It is not possible to add or remove code templates using the keyboard.
Users must navigate using the mouse when working in the Preferences - Code Editor:
Code Templates page.
Viewing a page preview from the visual editor
(8351673)
When viewing a page preview from the visual editor using the default browser
users should:
From the main menu, click Tools=>Preferences...=>Shortcut Keys
Locate the JSP and HTML Visual Editor
Preview in Browser and assign a key
Click OK and push button to close preferences.
This option will now be keyboard accessible.
Column headers for total/subtotal cells (6931494)
ADF Faces users can typically produce accessible table content by specifying
column headers for every column in their af:table. However, in certain complex
cases, such as when the AF:table contains total or subtotal rows, the cell containing
the labels for these rows may be inappropriately associated with the containing
column's column header. For example, assuming a column contains employee names
and has the header text "Employee Name", a cell containing the text
"Total" will be inappropriately identified to screen reader users
as being an "Employee Name". In order to avoid confusion, such cells
should not be associated with any column header. ADF Faces does not provide
any mechanism for suppressing column headers for such cells.
Keyboard selection request frequency (6238722)
When interacting with an AF:table, AF:tree, or AF:treeTable, using the up/down
arrow keys to change the selection can result in a round trip to the server.
ADF Faces already optimizes to reduce the number of round-trips by only sending
a single request at a time, and also by dropping requests for intermediate selection
states that occur while a request is outstanding. However, in some cases keyboard
users may find the current behavior inefficient, since a request is sent to
the server as soon as the request queue frees up. Ideally, no request would
be sent until after the user has reached the item that they intend to select
- ie. until after the user has paused keyboard activity for some short period
of time.
Tree node level state (8407966)
ADF Faces enhances AF:tree and AF:treeTable content to include information
about the tree node's level when running in screen reader mode, thus making
this information available to screen reader users. However, this level information
is only present for parent tree nodes - ie. tree nodes that contain children.
No level information is currently provided for leaf (childless) tree nodes.
Read-Only input components (5889673)
Currently read-only input components, such as AF:inputText, are rendered by
ADF Faces as plain text. As such, there is a loss of information that may be
meaningful to screen reader users - ie. screen reader users have no way to determine
that the text in question corresponds to a input control. In addition, since
plain text content is not included in the tab navigation order, screen reader
users may fail to recognize that this read-only content is present on the page.
Query criteria label uniqueness (8265301)
The af:query component automatically generates input controls to capture
the values for each query criteria. In cases where the query criteria
represents a range of values, the input control for the start of the
range uses the same label text as the input control for the end of the
range. It is not currently possible to provide a unique label for each
of these input controls.
Tabbbing out Graph when in screen reader mode (8407667)
When Graph is in the screen reader mode, it delivers an imagemap with area
elements for each data point. Once the focus is inside the graph, the user must
tab through all data points in order to navigate to the next tab stop. Under
some circumstances the user must apparently loop through the data points more
than once before navigating out of the graph.
Disabling row selection in af:treeTable (8295444)
When disabling row selection in the AF:treeTable by setting the rowSelection
attribute to 'none', the resulting AF:treeTable content is not keyboard navigable.
In particular, it is not possible to use the keyboard to navigate to and expand/collapse
nodes in the AF:treeTable. This issue can be avoided by not disabling row selection
for this component.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065, USA http://www.oracle.com
Bookmark
