This is an addendum to the release notes provided within the product. As new
issues arise, they will be added to this addendum.
Nested tables are not supported (6934398)
JDeveloper 10g does not support nested tables.
UI drawing problems or drawing slowness
Depending on your graphics drivers and hardware you may experience intermittent
UI drawing problems or drawing slowness. This can affect many aspects of the
UI including menus, dialogs, and icons. If you encounter this issue, try adding
this to jdev.conf, or as a command line parameter:
-J-Dsun.java2d.noddraw=true
Issues with multiple paths in model path (5973583)
Having multiple paths in the model path may fail with cannot find package errors
or an inability to display the packages of UML graphical shapes. It should be
possible to resolve this issue by creating directories for the missing packages
in the first path entry.
Running EJB 3.0 applications (5524015 & 5410005)
The EJB 3.0 runtime changed significantly between JDeveloper release 10.1.3
and JDeveloper release 10.1.3.1. An EJB 3.0 application created in JDeveloper
10.1.3 will only work with AS 10.1.3, and an EJB 3.0 application created in
JDeveloper 10.1.3.1 or higher will only work with SOA 10.1.3.1. You can migrate
EJB 3.0 applications from JDeveloper 10.1.3 to JDeveloper 10.1.3.1 following
the instructions in the online help topic Getting Started with Oracle JDeveloper
> Migrating to Oracle JDeveloper 10g > Migrating EJB 3.0 Applications
from Oracle JDeveloper 10g Release 10.1.3 to 10.1.3.1.
Migrating libraries in faces applications (5973804)
For faces applications, only jsf-impl.jar and adf-faces-impl.jar under <JDevWebProject>\web-inf\lib
will be migrated. If the user has added any other libraries under <JDevWebProject>\web-inf\lib,
then users have to manually update these libraries.
Exception while closing JDeveloper on Apple Mac (4967012)
The "Quit JDeveloper" application menu item for JDeveloper on Mac
(JDeveloper > Quit JDeveloper) throws an exception in the console and does
not properly shut down JDeveloper. The workaround is to use File > Exit from
the main menu.
ADF Faces components displayed without background image
(5756033)
Some ADF Faces components such as CommandButton, goButton, menuTabs, and resetButton
lose their background images at design time if the application name or project
name contains non-ASCII characters, and if the Oracle skin, which is the default
for the 10.1.3.2 release, is being used.
If you want to ensure that the images are visible at design time, the workaround
is to ensure that the application name and project name do not contain non-ASCII
characters.
JSF page not displayed in design view (5716043)
JSP and JSPX pages may not display properly in the Visual (Design) Editor when
custom servlet filters or JSF PhaseListeners are specified in the web.xml or
faces-config.xml respectively. Current workaround is to temporarily comment
them out while designing or embedding java.beans.Beans.isDesignTime() logic
in the code to prevent execution at design time.
Application name with non-ascii characters may cause HTTP
404 errors (5730659)
When an application name in JDeveloper or the context root contains non-ASCII
characters, the define link in the first page of the OmniPortlet may throw HTTP
404 errors. The workaround is to click Action -> Customize to instead use
Customize UI.
Regenerating WS from WSDL fails to update the implementing
java class (5680769)
After making changes to the WSDL, the user has to Regenerate Web Service from
WSDL twice or thrice to get the relevant files updated correctly, fx., adding
an operation, regenerating from wsdl and getting the method added to the interface
and implementation class. When an operation name is changed in the WSDL, the
implementation class doesn't replace the earlier method, but adds a new one
with the new name. User has to manually remove the unrequired method from this
class. When an operation is deleted from the WSDL, the implementation class
doesn't remove the method even on regenerating again, and hence needs to be
manually deleted from the implementation Java class.
File upload using <af:inputFile> fails for uploaded
files of any size (5601588)
Using the <AF:inputFile> component to handle file upload, you will receive
the following exception for files uploaded of any size:
java.io.EOFException: Per-request disk space limits exceeded.
There is no workaround. To fix this issue, obtain the one-off patch available
from Oracle Worldwide Support, citing the bug number. This bug does not exist
in release 10.1.3.2.
NullPointerException when creating EJB 2.x CMP entity beans
from tables using a SQLServer 2000 connection (5575802)
When calling the 'CMP Entity Beans from Tables' wizard to create EJB 2.x CMP
entity beans from tables in a SQL Server 2000 connection, you may see an exception
dialog resulting from a NullPointerException that is thrown by the SQL Server
2000 database driver. You can safely ignore this exception, and cancel the dialog
to allow processing to continue. The exception occurs when attempting to close
the connection, and it does not prevent the successful creation of the CMP entity
beans.
ADF Swing WebStart does not work with EJB 3.0 (4755365)
ADF Swing client built against EJB 3.0 DataControl cannot be deployed using
WebStart. This is due to WebStart deployment descriptor limitation. In order
for ADF Swing client work with an EJB 3.0 DataControl, it is necessary to pass
-javaagent command line argument to the VM. However, the WebStart deployment
descriptor does not allow the -javaagent parameter to be specified. This limitation
does not affect EJB 2.1 Data Control.
Restore option does not restore bc4j.ear
Use of the restore facility does not redeploy bc4j.ear to the 10.1.3.0.0 application
server. This should not affect functionality, as datatags.ear is exactly the
same as bc4j.ear. However, if required bc4j.ear must be manually deployed using
the EM console.
The <JDev_Install>/BC4J/redist/ folder contains the renamed datatags.ear
file. In previous releases this file was the bc4j.ear file. The new name more
accurately reflects the contents of this file and it's limited role to provide
web application images and CSS support for the deprecated BC4J JSP Datatag library.
Enable JAAS mode when using ADF with LDAP identity management
When using ADF with LDAP-based identity management, make sure to enable JAAS
mode. Please refer to Oracle Containers for J2EE Security Guide for details
on how to enable JAAS mode.
JAAS mode can be enabled by adding the following line in orion-application.xml:
Bookmark
