Oracle JDeveloper and Application Development
Framework (ADF) 11g Release 2 Update 1 (11.1.2.1.0)


Known Issues for JDeveloper and ADF 11g Release 2 Update 1 (11.1.2.1.0)

last updated: Oct. 20, 2011

Content

Introduction

    Oracle JDeveloper and Application Development Framework 11g Release 2 (11.1.2.1.0) is a minor bug-fix update to 11.1.2.0.0. There are hundreds of new features and thousands of bug fixes. For a list of new features in 11g Release 2, and specific customer bugs fixed in the update release see the What's New document on OTN. 

    This document describes known issues with the release. If and when new issues are discovered they will be added to this document. Please also use the JDeveloper community discussion forum on OTN for questions and answers and to let us know what you think!

    One very important note about this version is the fact that it is released off-cycle from Oracle Fusion Middleware. While this allows the
    team to bring the product to market faster, there are a number of critical implications.

1) There is no design-time or runtime support for SOA and WebCenter components in 11g R2

ADF 11g Release 2 is intended primarily for customers who are building stand-alone ADF applications. If your business requirements entail the use of ADF in conjunction with Oracle SOA Suite or Oracle WebCenter, it is recommended to use the latest, fully integrated 11g Release 1 of Oracle Fusion Middleware (currently 11.1.1.5.0 at time of publication), including Oracle JDeveloper 11g Release 1.

2) There is no stand-alone installation of the Application Development Runtime component in 11g R2

ADF 11g Release 2 needs to be installed as a patch on top of of an existing 11.1.1.5.0 Application Development Runtime installation. The steps for upgrading 11.1.1.5.0 server to run 11.1.2.0.0 ADF applications is described later in these release notes, and documented in the Administrator's Guide for Oracle Application Development Framework.

Note: JDeveloper should always be installed in a new MIDDLEWARE_HOME.

Installation

Please read the installation guide for details on system requirements and specific installation instructions for various platforms.

 

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 (http://download.oracle.com/docs/cd/E24382_01/install.1112/e17074/toc.htm) 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

An additional step is required to successfully run applications on Mac systems that have Java for Mac OS X 10.5 Update 4 installed (8681385):

  1. Open the jdev.conf file. The file is located in the MW_HOME/jdeveloper/jdev/bin/ directory.
  2. Add the following line to the jdev.conf file: AddVMOption -Djava.io.tmpdir=/var/tmp

QuickStart

    QuickStart Contains Link to 11g Release 1 (11.1.1.4) Documentation Library (12365574)

When you click "Access documentation online" on the QuickStart window (accessible from the Start Menu), you are taken to the Oracle Fusion Middleware 11g Release 1 (11.1.1.4) documentation library. The link should take you to the Oracle Fusion Middleware 11g Release 1 (11.1.1.5) documentation library, which is available at: http://download.oracle.com/docs/cd/E21764_01/wls.htm.

Migration

JSF 2.0 Migration

When opening a workspace that uses JSF technology, we migrate the application to JSF 2 by doing the following:

  • Change project properties that refer to JSF tag library and runtime libraries to JSF 2.0 tag library and runtime libraries
  • Migrate web.xml:
    • a. Upgrade web.xml to version 2.5
    • b. Add the following parameters:
      • set  javax.faces.PARTIAL_STATE_SAVING to "false"
      • set oracle.adf.view.rich.security.FRAME_BUSTING to "differentDomain"
  • Upgrade faces-config.xml to version 2.0
  • If the application uses Facelets:
    • a. Remove any references to the Facelets 1.x library
    • b. Make the following changes in web.xml:
      • > if there is "org.apache.myfaces.trinidad.FACELETS_VIEW_MAPPINGS" parameter in web.xml, set "javax.faces.FACELETS_VIEW_MAPPINGS" to the same value
      • > remove "facelets.DEVELOPMENT" parameter
      • > remove "org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER" parameter
      • > change the following param names:
        • facelets.SKIP_XML_INSTRUCTIONS => javax.faces.FACELETS_SKIP_XML_INSTRUCTIONS
        • facelets.SKIP_COMMENTS => javax.faces.FACELETS_SKIP_COMMENTS
        • facelets.DECORATORS => javax.faces.FACELETS_DECORATORS
        • facelets.RESOURCE_RESOLVER => javax.faces.FACELETS_RESOURCE_RESOLVE

JSF Upgraded to 2.0

The JSF version packaged in 11.1.2.0.0 has been upgraded to 2.0 which may cause applications using the exact-match flag set to true
to fail to deploy. The solution is to set exact-match to false. JSF 2.0 is backwards compatible with previous versions and should not
cause any problems.

 

IDE and Java SE Development

Structure Pane Enhancements (11887639)

A couple of new enhancements in the structure pane were introduced, particular to assist when dealing with large, complex tree structures:

  • Users now have the ability to search for items in the tree by clicking on the Find icon in the toolbar and typing in the desired text. Next and previous capabilities are included.
  • Users can now arbitrarily mark any node as the current "root" node so they can focus on a particular part of the tree. This is accomplished by clicking on the node and selecting Show As Top from either the right-click context menu or from the toolbar. To get back to the full tree can be done by either selecting Show Root from the right-click context menu or clicking the Show Root icon just above the current "root" node. The behavior synchronizes with the Design This Container/Design Main Page feature of the JSP Visual Editor.

Pasting from Windows directly into JDeveloper running on hosted Linux via VNC (11842393)

When using JDeveloper through VNC Viewer, pasted data originating from the VNC client will not be available to the hosted JDeveloper process. To synchronize JDeveloper with the system clipboard, switch focus from JDeveloper to another application, and then back to JDeveloper again.

 

Password field disabled for keyboard entry on 64-bit Red Hat Linux

A JDK bug will sometimes prevent keyboard input into Swing password fields. You may be able to click in the field but you cannot enter a string or use navigation keys such as the Tab key. This occurs on 64-bit Red Hat Linux systems.

You may encounter this issue when you are using:

  1. Domain Configuration Wizard when logging into the Integrated WebLogic Server for the first time
  2. Standalone Domain Configuration Wizard (launched from Quickstart to configure a standalone WebLogic Server)
  3. ADF Model Tester (which prompts for a password when testing an application with ADF security enabled)
  4.  Create Database Connection dialog

The workaround is to issue the following setenv command before you launch the IDE or Quickstart.
class="code-java">setenv LC_ALL en_US

Change in Default for "Check for Externally Modified Files on Startup" setting

In previous releases, JDeveloper was configured by default to check the timestamp of files on disk for opened projects at startup.
If modifications are found, JDeveloper synchronizaes the project contents with the version that is on disk. For performance reasons,
the default setting for this option has been changed in this release.

With this setting off, it's possible for the contents in the JDeveloper project to be out of date with respect to files on disk if those files
have been modfied by another program. To refresh the project contents (you can select multiple projects at once in the navigator), use
the View > Refresh command.  Alternatively, you can modify the setting in Tools > Preferences, Environment tab by checking the option
to Check for Externally Modified Files on Startup.

If you migrate your IDE settings from a previous release, you will continue to have the same behavior as you are accustomed.

Web Applications

Warnings appear when using JSFC attribute with HTML tags (Bug 10252336)

We do not currently support the use of the JSFC attribute with HTML tags.

Delay when redeploying app using wls datasource (12796317)

A redeployment of an ADF BC web application is delayed for 60 seconds because of a wait time for the datasource to be removed. This is a performance regression compared to previous JDeveloper versions because of a change in the ADF BC layer to use WLS datasources - which is a best practice.

Database Development

Go to Declaration and Find Usages for Packaged Procedures and Functions (Bug 12422139)

Usages of packaged procedures and functions from outside the package are only listed when you use Find Usages on the definition in the package spec. Usages of packaged procedures and functions from within the package body are only listed when you use Find Usages on the definition in the package body. The usages are not listed together.

Goto Declaration and Find Usages for Type methods(bug 12422169)

Methods in Type bodies may not be correctly identified when you use Goto Declaration or Find Usages.

Creating a Database View on a Database Diagram (12334344)

When you first create a new view in a live database on a database diagram, the relational usage that the view has on a table is shown as NOT LOCATED. The workaround is to save the diagram and either use View > Refresh, or close the diagram and reopen it, and the relational usage will be shown correctly.

Migrating .generate Files from Earlier Releases of JDeveloper (10385245)

The persistence format of .generate files changed between JDeveloper 10.1.3 and JDeveloper 11.1.1.4.0.  If you are migrating from earlier releases to JDeveloper 11.1.1.4.0 as part of the migration to JDeveloper 11.1.2.0.0 and you have .generate files, then you need to force any .generate files to be saved by JDeveloper 11.1.1.4.0 in the new format. The way to do this is to open the .generate file and make a change to it, then click OK to save the file.

Generating from Offline DB to SQL Script (12945650)

If you generate offline database objects from an offline database to a SQL script, and in the Choose Operation page you select Override Schema, an error is reported.

The workaround is to generate the SQL script without selecting Override Schema and specify a different schema by editing the generated SQL file.

Alternatively, rename the schema in the offline database before generating the script.  In this case you need to check Prefix object name with schema name on the "SQL Script Options" page.

 

Deployment

Problems running WLS on Windows 7 64-bit or Mac (9466912, 8969281)

JDeveloper does not look at the value of CLASSPATH or JAVA_HOME to determine its classpath or jdk; it stores this information in proprietory locations. The WebLogic domain installation scripts, however, extend the supplied value of the CLASSPATH and JAVAHOME variables, and WebLogic domain creation will fail if JAVAHOME contains ')' or CLASSPATH contains a space. The former happens when, for example, the 32bit JDK is installed in its default path, for example:  C:\Program Files (x86)\Java\jdk1.6.0_18.  The latter if an application such as Apple QuickTime adds itself to the to the CLASSPATH environment variable, for example:
CLASSPATH=.;C:\Program Files (x86)\QuickTime\QTSystem\QTJava.zip

In either of these cases, creation of the Integrated WebLogic Server domain fails with a message similar to:

 

[waiting for the server to complete its initialization...]
\Java\jre6\lib\ext\QTJava.zip was unexpected at this time.
Process exited.

 

The workaround is to install the JDK in a path withpout ')', and remove the Apple QuickTime entry from the classpath,
and restart JDeveloper.


Migrated 10.1.3.5 Application Fails With Validation Problems (8822394)

If you migrate an application that contains web.xml with <form-login-config> from JDeveloper 10.1.3.5, it may fail with validation problems when it is run on Integrated WebLogic Server.

To fix this, open web.xml in the source editor and add "/" in front of "login.html" and "error.html" in the login-config tag. For example,

<login-config>
   <auth-method>FORM</auth-method>
   <form-login-config>
     <form-login-page>/login.html</form-login-page>
     <form-error-page>/error.html</form-error-page>
   </form-login-config>
</login-config>

 

Upgrading a 11.1.1.5 Application Server and JSF 2.0 shared library to run ADF 11.1.2.1.0 Applications

The ADF Runtime will be installed into a standalone application server by applying an Opatch bundle on top of a PS4 11.1.1.5 version of the Application Developer shiphome. In the event that additional patches are needed or desired in addition to the Sherman 11.1.2 patch (for example, if an additional patch is needed for another component in the Application Development Runtime shiphome), those patches will need to be installed separately.

Important Note: The patch is intended to be applied to an Application Developer shiphome only. Applying the patch to a different shiphome (for example SOA Suite or WebCenter) is not supported.

Key Installation steps for EXISTING Oracle WebLogic Server Users

  1. Ensure server is an 11g Release 1 Patch Set 4 (11.1.1.5) Application Developer shiphome. Patch Set 4 itself will be available in both a "patchset" form as well as a "full" install. Customers using a version of Application Developer shiphome prior to Patch Set 4 will need to upgrade their environment to Patch Set 4 before installing Sherman 11.1.2. For more information see the Oracle Fusion Middleware Patching Guide.
  2. Download the Sherman 11.1.2 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12979653 and WebCenter patch bug#12917525
  3. Shutdown the target domain servers.
  4. Run the WLST "upgradeADF" command in offline mode.
  5. Restart the servers.

 

Key Installation steps for NEW Oracle WebLogic Server Users

  1. Download and install WLS 10.3.5 (CIE install).
  2. Download and install Application Developer 11.1.1.5 (OUI install). For more information see the Oracle Fusion Middleware Installation Planning Guide.
  3. Run the Fusion Middleware Configuration wizard and create a new domain, or extend an existing domain, using the JRF + EM + OWSM domain template.
  4. Download the Sherman 11.1.2.1.0 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12979653 and WebCenter patch bug#12917525
  5. Shutdown the target domain servers.
  6. Run the WLST "upgradeADF" command in offline mode.
  7. Restart the servers.

Key Installation steps  for IBM WebSphere Application Server Users

  1. Download and install WebSphere if needed. For more information, see the Oracle Fusion Middleware Third-Party Application Server Guide and IBM WebSphere Application Server documentation.
  2. Download, install, and configure Application Developer 11.1.1.5 (OUI install). For more information, see Oracle Fusion Middleware Installation Planning Guide.
  3. Download the Sherman 11.1.2.1.0 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12979653 and WebCenter patch bug#12917525
  4. Shutdown the servers.
  5. Run the wsadmin "upgradeADF" command in online mode while connected to the server.
  6. Restart the servers.

Install the Patch

  1. Install the patch. For WebLogic, install the adfwLSTCommand.py script into the 11.1.1.5 ORACLE_HOME/oracle_common/common/wlst directory. For WebSphere, install the ADFAdmin.py script into the 11.1.1.5 ORACLE_HOME/oracle_common/common/wsadmin directory.
  2. Run either the WLST or wsadmin shell and invoke the commands as described in the next section.
  3. Use the application server's administrative console to verify that the shared library is installed correctly on the server.
  4. Deploy JSF 1.2.9 and JSF 2.0 applications to validate that they work. Note that if an existing application explicitly specify that it requires an exact match against a JSF 1.2.x version, then you must match this version before running the application against the 11.1.2 shared library. This should not be a typical case.
  5. Validate the shared library using Enterprise Manager.

Run the Commands 

  1. For WebLogic, invoke the following command in WLST offlne mode.  For example: 
    wls:/offline> upgradeADF('/scratch/jdoe/oracle/jdeveloper/system11.1.1.5.37.60.32/DefaultDomain')
Target Library "jsf#2.0@1.0.0.0_2-0-2" to JRF "DefaultServer"


    Parameter 1 (Required) - DomainLocation - Domain to be upgraded
    Parameter 2 (Optional) - JSF Library Name. Defaults to jsf.
    Parameter 3 (Optional) - JSF Library Spec Version. Defaults to 2.0.
    Parameter 4 (Optional) - JSF Library Impl Version. Defaults to 1.0.0.0_2-0-2.

  2. For WebSphere, invoke these commands in wsadmin online mode (i.e. when connected to the server). Note: you can obtain the SOAP port number from the deployment manager's portdef.props file. 

    > wsadmin.sh -conntype SOAP -port portnumber -user username -password password
> ADFAdmin.upgradeADF('DefaultCell', 'OracleCellFederatedNode', 'OracleAdminServer')


    Parameter 1 (Required) - Cell
    Parameter 2 (Required) - Node
    Parameter 3 (Required) - Server
    Parameter 4 (Optional) - JSF Library Name. Defaults to jsf.
    Parameter 5 (Optional) - JSF Library Spec Version. Defaults to 2.0.
    Parameter 6 (Optional) - JSF Library Impl Version. Defaults to 1.0.0.0_2-0-2.

 

 

 

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.
     

    Webservice generation functionality broken when using JDK 1.6u27 and later (13076887)

     

    When using later builds of the JDK the large majority of the soap web services functionality no longer works due to a change in the JDK,
    you can work around this by pulling an earlier version of the JDK or getting hold of the patch attached to the bug via support.
     

    When generating web services in some cases, error messages appear about being out or PermGen space (13095627)

    If you see this message you can increase the amount of PermGen allocated by editing .../jdeveloper/jdev/jdev.conf to increase the value
    from 256M to 288M.
     

    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:

    <conv:ContinueHeader xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/">

    <conv:conversationID>uuid:701f9f3d434bfc98:-3f39a0ef:11c4b649fd4:-7fff</conv:conversationID>

    </conv:ContinueHeader>

    From the HTTP Content tab in HTTP Analyzer, insert the above tags within the header element of the SOAP request message, as below:

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header>

    <!- other header elements-->

    <conv:ContinueHeader xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/">
    <conv:conversationID>uuid:701f9f3d434bfc98:-3f39a0ef:11c4b649fd4:-7fff</conv:conversationID>
    </conv:ContinueHeader>

    </env:Header>

    <env:Body>

    <!- message data details ->

    </env:Body>
    </env:Envelope>

    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
{
    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:

    1. 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.
    2. 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.
    3. 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.

    JAX RPC stateful service: JAX WS client is throwing exception (7533170)

    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.

TopLink DBWS Generation Fails with NPE (11665601)

The fix for this is available from ARU patch 13573106.

Running TopLink DBWS secured with OWSM policies that require a keystore fails (10229986)

It is not possible to run a Toplink database web service provider secured with an OWSM policy that requires a keystore. There is likely
to be a XML read error thrown from the OWSM layer on the server side. Though there is no workaround for this specific issue, securing
the provider service with a simple username token policy that does not rely on a keystore for credentials would make it work.

Policy not enforced on a provider service with no WSDL

For a web service provider with no WSDL associated with it, any policy attachments on it are not enforced by the server.  In order to warn the user from deploying such a service, JDeveloper puts up a warning on the code editor when such a scenario is detected. The workaround for this problem is to keep a WSDL for the provider service and attach it to the service using the 'wsdlLocation' annotation parameter.

Failure to PUT or POST to a Jersey REST Service co-located in a project with ADF components (12542672)

You might notice a "{{org.xml.sax.SAXNotRecognizedException: http://javax.xml.XMLConstants/feature/secure-processing}}" exception when using the PUT or POST operation on a Jersey resource that is co-located in an application that contains any ADF components or any project that overrides the default XML parser to use the one that is part of the XDK. This is caused by WLS bug 12543845 where an invalid configuration property is store and causes all further XML parser instances to fail.

The workaround is to disable the part of Jersey that sets this proper with a servlet init param:

<servlet>
    <servlet-name>jersey</servlet-name>
<servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class>
    <init-param>
<param-name>com.sun.jersey.config.feature.DisableXmlSecurity</param-name>
      <param-value>true</param-value>
    </init-param>
    <load-on-startup>1</load-on-startup>
  </servlet>

This should only be applied if the user knows for sure they are using the XDK otherwise this will open up a possible security whole.

JAX-RPC web service design-time support now deprecated

With the deprecation of JAX-RPC in the Java EE 6 platform, this will be the last major JDeveloper release (ie the 11g release set) where the generation of a JAX-RPC style web service will be supported in the JDeveloper web service design time. Therefor, in the next major release set (currently scheduled to be 12c), the JAX-WS and JAX-RS standards will be the web service standards supported by the JDeveloper
web services design-time and there will be no support for the generation of web services that conform to the JAX-RPC standard.

Can't create data control metadata over web service method parameters and returns (12433980)

When creating a web service on an EJB session bean, you must manually update the parameter name and return name annotations with the type before generating the associated WSDL file to add to the project.

By default, the @WebParam name is set to "arg#", and the return type is not generated in the annotation. Before you generate the WSDL file, you must do the following for each method:

 

  • Change the name value of the @WebParam to the appropriate parameter type name.
  • Prepend the name value of the @WebResult to the method's generated return type.

For example, say you created a web service method with the following annotation:

@WebMethod
public Employee getManager(@WebParam(name = "arg0") Departments dept) {...}

You would need to manually edited the method to look like this:

@WebMethod
public @WebResult(name="Employee") Employee getManager(@WebParam(name="Departments") Departments dept) {...}

Note that this workaround does not work with methods that have multiple parameters of the same type, or if the underlying artifacts
(EJB, XSD) are not local to the project.
 

java.lang.illegalstateexception: sslcontextimpl is not initialized after migration from PSx (12660729)

If you are upgrading from PS5 or another release of JDeveloper you may find exceptions of the following form when using code that accesses https connection or configures code that might access network connections.

java.lang.IllegalStateException: SSLContextImpl is not initialized
&nbsp;&nbsp;&nbsp;&nbsp; at
com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory
(SSLContextImpl.java:145)
&nbsp;&nbsp;&nbsp;&nbsp; at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
&nbsp;&nbsp;&nbsp;&nbsp; at
oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory
(LazySSLContextSpi.java:67)
&nbsp;&nbsp;&nbsp;&nbsp; at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
&nbsp;&nbsp;&nbsp;&nbsp; at

This is generally caused because the user has altered the default HTTPS settings, probably the trust store, to point to a certificate file that
no longer exists. (In the cases we have seen this is because they point to the cacerts file from a previous install that has been removed)

You can resolve this problem by resetting the HTTPS settings in Tools->Preferences->Credentials->HTTPS Credentials->Default. 
A tool restart might be required.

Cannot run EJB @Stateless Web Service Provider (Bug 12896076)

You will find that a @WebServiceProvider that is also a EJB @Stateless object will fail to start up properly and it will fail with the
following error.

<Aug 19, 2011 3:20:45 PM IST> <Error> <HTTP> <BEA-101020>
<[ServletContext@32421865[app:Application2
module:/Application2-Project1-webapp path:/Application2-Project1-webapp
spec-version:null]] Servlet failed with Exception
java.lang.NullPointerException
at weblogic.wsee.jaxws.WLSServletAdapter.publishWSDL(WLSServletAdapter.java:239)
at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:166)
at weblogic.wsee.jaxws.HttpServletAdapter.get(HttpServletAdapter.java:193)
at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:93)
at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
Truncated. see log file for complete stacktrace

 


Spring and Weblogic SCA Development

JDeveloper hangs when using Spring tooling without an active network connection (10050723)

When editing a spring bean definition you might experience hangs as the code incorrectly tries to download files from the internet. 
(In particular datatype.dtd)  You need an active network connection to make use of the Spring tools or apply the patch described
in bug 12712872.

Team Productivity Center Issues

Hudson Plugin available through Installer or Hudson Update Center

The plugin for the Hudson continuous integration system is available in two locations:

 

  • In the Team Productivity Center Server installation JAR.
  • In the Hudson update center

You can install or update the Hudson plugin through the Hudson user interface. From your running installation of Hudson, select Manage Hudson > Manage Plugins, then select the appropriate page from the list of plugins.

Bugzilla access through XML-RPC is no longer supported

In releases prior to 11.1.2.1.0, users of Bugzilla were required to download and install two modules - SOAP Lite and Test-taint - which were necessary for third-party tools to connect to Bugzilla. This was necessary for Team Productivity Center, which used XML-RPC to connect to Bugzilla. Beginning with JDeveloper 11.1.2.1.0, XML-RPC is no longer used for Team Productivity Center to connect to Bugzilla.

WLS Hot Reload

This feature, enabled only in the Integrated WLS in JDeveloper, speeds up the development process by allowing the changes made
          to the project visible upon rebuild without deployment.

    Enabling Fast-swap and its limitations

For JDeveloper deployments, the Fast-swap feature of WebLogic is disabled by default.  Fast-swap allows eligible class file changes to be visible in the application run-time by simply refreshing the browser.  See this WebLogic Fast-Swap document for more details.  Class file changes are copied to the running application when the source file is built.

Enabling Fast-swap:

  • To enable Fast-Swap globally for all applications, select Tools->Preferences->Run->WebLogic->Select Hot Class Reload Policy->Fast Swap
  • To enable or disable Fast-Swap for an individual application, select a Application Properties->Run->WebLogic->Select Hot Class Reload Policy.  Set this back to Tools Preferences Default to use the global default.
The following are known limitations of running with Fast-swap enabled:
  1. When deploying Web Services, the generated WSDL file may contain additional entries for the Object class methods such as (9236022) 
    <operation name="equals">
<input message="tns:equals" />
<output message="tns:equalsResponse" />
</operation>

    It is important not to use WSDL's generated from the server in this mode when publishing WSDL's to third parties to consume. This will represent an incorrect version of the service and may in certain cases prevent the client from functioning properly. The extra methods may also not be secured properly which might imply some compliance problems depending on the back end data.

  2. On Windows, if an app is deployed with Fast Swap enabled, then if a class from a JAR library is being loaded and if that JAR file's URI contains a space, you get an error (11884533): 
    java.net.URISyntaxException: Illegal character in opaque part at index 11: zip:D:/With Space/Application77/lib/DependentLib.jar\!/dependentlib/DependentLibClass.class

    A workaround is to place the application or JAR file in a directory with a URI that does not contain spaces.

 

    Hot Reload does not support modifications to adfm.xml

WLS Hot Reload does not reflect changes made to adfm.xml. You need to redeploy your application if following changes are made.

  1. Creating an Application Module in a new package. A new bc4j.xcfg file is created in the package and the entry added to adfm.xml.
  2. Creating a data control definition of any kind for the first time in a project. Creates a new DataControls.dcx file and is referenced by adfm.xml.
  3. Creating a new project dependency in the workspace (jdeveloper application). If the new project dependency has an adfm.xml of its own, i.e. it contains Business Logic Groups (BLG), shared application module, bean controls, or data binding registry, it will not get picked up. The .jpx, .dcx and .cpx files are referenced in adfm.xml and the adfm.xml in the dependent project will not get picked up.

 

    Hot reloading throws JboSerializationException (JBO-25033) if passivation is enabled in Application Module (10262972)

Application Module failover can interfere with the passivation triggered from Hot Reload. It is recommended to disable Application Module failover when working in Hot Reload mode.

    Fetched rows do not reflect the modified SQL query during Hot Reload

For example, a new view criteria is added to a view object to narrow the query result but same rows are returned. This is the expected behavior as Hot Reload saves your previous state and tries to restore your refreshed state with the same data. The query changes will
take effect in a new login session.

    Performance degradation when Hot Reload is on

Hot Reload is turned on by default when the application is run in the Jdeveloper's integrated weblogic server. To implement the feature ADF runtime checks for modifications to any cached definitions at the beginning of a web request. Based on the size of the project it may slow down the performance of the application. Please note that this is not an issue when the application is deployed to an external weblogic server. If you don't plan to take advantage of the Hot Deploy feature it can be turned off by editing the Project Settings->Java EE Application->Integrated WLS commandline and appending the jvm property -Doracle.jdeveloper.adrs=false.

 

ADF Desktop Integration (ADFdi)

Known Limitations on changing ADFdi components at runtime (6196783, 6032482)

  • Moving a Column in a Runtime ADF Read-only Table Component (bug 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 left-most 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 (bug 6032482)
    Change tracking is disabled if an end user moves a column to the end of an ADF Table component at
    runtime. Subsequent edits to cells in the moved column do not mark the row as changed.

Using a variableUsage Element Causes Null Pointer Exception in ADFdi Remote Servlet (6377073)

ADFdi does not support variables in the page definition declared with the syntax of variableUsage. (6377073)
If the developer creates variableUsage in the ADFdi-related page definition, it will produce NullPointerExceptions
in the server at runtime.
Workaround is to instead create variables using the <variable> element in the page definition.

Known Issues related to displaying web pages using the Dialog action (9718945)

  • If the end user displays a web page from a Dialog action and then allows the web app session to timeout, there may be a loss of
    necessary context if the server renews the session automatically. In such cases, Table.RowDownSync may not produce the expected
    result. (bug 9718945)
    Workaround: enhance the web page's bean code to detect a change in the current row and cancel the dialog.

Known Issues with the design-time property inspector and expression builder features (6314302, 7269921)

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 work-around is to save the object and then re-open.

Sample issues:

  • New components in the expression builder (bug 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 (bug 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.

Known Issues with ADFdi List of Values Components (8651633, 8651645)

Empty Forms (bug 8651633, 8651645)
An Excel form cannot be configured to use ADF List of Values components which use model-driven list bindings if the form's bound
iterator is expected to contain zero rows. Workaround: configure the ADF List of Values component to use a "dynamic" list binding instead.

Known Issues with SSL (7117108, 9536914)

  • Integrated Excel Workbooks and HTTPS (bug 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:
             |  ADFDI-00134: An attempt to connect to the web application has failed.

    Solution: Navigate to a web page from the same application using Internet Explorer. This action will install
    the certificate locally.  Subsequent attempts to use the integrated workbook will succeed.

  • Login dialog flashes briefly for web app w/no authentication but using https (bug 9536914) If your web application is configured to use SSL/HTTPS, but does not use authentication, the login dialog will appear briefly when the workbook establishes a connection and then close again in order to recognize the certificate.

Known issues involving the Read-only Table Component (8272219)

The following known issues may be encountered when working with the ADF Read-only Table Component.
To avoid these issues, consider using the ADF Table component in a read-only configuration.

  • Server-side row set can be Positioned on Wrong Row When DoubleClickActionSet Invoked on ADF Read-only
    Table Component (bug 8272219)
    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.

Known Issues at design-time (9737702)

  • Deleting cells (9737702)
    If the developer deletes a cell adjacent to the cell containing an ADF component and shifts that cell into the position
    of the deleted cell, ADFdi offers to delete the component.

Migrating from previous releases of Oracle ADF 11g (10358830, 12381232)

  • ADFdi Shared Libraries. Starting in 11.1.1.4.0, ADFdi server components are delivered as part of the "JRF" and no longer need to
    be included explicitly in your web application. If you are creating new WLS domains using 11.1.1.5.0, the ADFdi shared libraries are included automatically. However, if you have already created your WLS domain using 11.1.1.3.0, you will need to perform a special step to upgrade that domain. For example, running the WLST command "updateJRF()".  See 'Updating Fusion Middleware Shared Libraries' in the 'Oracle Fusion Middleware Patching Guide link:
    http://download.oracle.com/docs/cd/E21764_01/doc.1111/e16793/patch_set_installer.htm
  • Cannot upload saved changes from 11.1.1.3.0 workbook after migration to 11.1.2.0.0 (bug 10358830)
    Solution: Prior to upgrading from 11.1.1.3.0 to 11.1.2.0.0, be sure to upload or discard any pending changes in saved workbooks.  After migration, be sure to re-download any data in saved workbooks.
    Note: if your workbooks were already migrated from 11.1.1.3.0 to a later 11.1.1* release, this note no longer applies.
  • Workbook Migration
    If you wish to use integrated workbooks created using 11.1.1.3.0 or earlier with ADFdi 11.1.2.0.0, you will have to perform one or more migration steps. The migration can be performed at design-time and also on published runtime workbooks. It is preferable to convert design-time workbooks and re-publish so that end users do not have to experience the migration.
    Note: if your workbooks were already migrated from 11.1.1.3.0 to a later 11.1.1* release, this note no longer applies.
    In general, you cannot have two versions of ADFdi installed on the same computer. There is an exception in this case: you can leave 11.1.1.3.0 installed while migrating workbooks to 11.1.2.0.0. If you do so, you will avoid seeing several errors. However, if you have already uninstalled the old version, you will see 1 or 2 errors during the migration of each workbook as it tries to access the old version. These errors can be dismissed and ignored. 
    Assuming that you are migrating 11.1.1.3.0 workbooks at design-time, the steps are:
  1. Install the new ADFdi client
  2. Create a backup copy of the design-time version of your workbook
  3. Open the design-time version of your workbook
  4. Dismiss any error dialogs if the old client has been uninstalled
  5. When prompted to migrate, click "Yes"
  6. Test your workbook: review/adjust the column widths of your table's Changed and Flagged columns;
    review the runtime ribbon tab contents; adjust any labels as desired.
  7. Publish your workbook
  8. Repeat this process for each integrated workbook in your application
    Note: a migrated workbook can no longer be used with the old client.
  • Automatic client upgrade from 11.1.1.4.0 (bug 12381232)
    In general, it is possible to upgrade the ADFdi client software by placing the new installer on top of the old installer (typically located on a shared file server). The next day, when the end users open Excel, the add-in self-upgrades. Due to an installer name change, this self-upgrade does not work properly when upgrading from 11.1.1.4.0 to 11.1.2.0.0. Workaround: uninstall the client from Windows' Add/Remove Programs control panel and then run the installer for the new version.

ADF Faces and Data Visualization Runtime

Browser Specific Bugs

IE8, IE9 note:   Compatibility View mode must be off.
For a listing of all supported browsers, see Supported Platforms section.
(http://www.oracle.com/technetwork/developer-tools/jdev/jdev11gr2-cert-405181.html#Browsers)

Profiler file logger

The profiler file logger can be used only in a non-portal environment on FF and IE browsers with at least 1.5._06 JRE on the client box and privilege to write to the user home directory. The resulting file format is subject to change without any notice and not intended to be used with any xml parser tool. In order to use the feature, the user has to accept the certificate.

StringIndexOutOfBoundsException in org.apache.myfaces.trinidadinternal.style.util.CSSGenerationUtils (9400134)

This error happens due to bug 6875866 (HotSpot compiler bug in String.indexOf() using SSE4.2 instruction-set on new Intel chips).
Workaround is to add this line to the JVM options: -XX:-UseSSE42Intrinsics, then remove the cached CSS file,
e.g., $APP_TMP_FOLDER/public/adf/styles/cache/blafplus-desktop-ezog8j-en-ltr-gecko-1.9.1.8-cmp.css
restart WLS, clear your browser cache and everything should be working.
Please note that the bug should be fixed with jdk6.18b02, but we see it on 6.18b07

     

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.

Active data service (6926281)

If Active Data Service is enabled in an application, there are certain ADS pages (/adwwls/wls.ads and adw.jspx) that should not be cached.
If Oracle Web Cache runs for the application, need to add cache rule to exclude pages with name of /adwwls/wls.ads or adw.jspx.

Primary keys from model (6894412)

In previous releases, ADF Faces components expect applications to use primary keys on the model data objects that are pre-populated for new records and do not change with any record updates. This limitation has been removed from the current release except for the case where the affected row is not in UI range while its key is changed programatically in a backing bean.

     

Application view cache (6495920)

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.

Trinidad application and new Window detection (8677612)

New Window Detection logic onlyvworks in Rich Client applications, but not in Trinidad applications For Trinidad applications, the following parameter should be added in web.xml to disable New Window Detection logic.

    <context-param> <param-name>oracle.adf.view.rich.newWindowDetect.OPTIONS</param-name> <param-value>off</param-value> </context-param>

Emailable page (8554509, 8868756, 8827678)

The table component has some known issues in emailable page mode.

    • The Total/Subtotal rows of the table are not bold in Outlook (8554509)
      The application developer would need to define the bold style directly on their outputText.
    • The detailStamp, if disclosed, does not render as disclosed in emailable page mode in both Thunderbird and Outlook. (8868756)
    • columnStretching="last" doesvnot work in emailable mode (8827678)
      since this happens in javascript and javascript is not supported by email agents. You need to set the width attribute on the af:column components.

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.

RUEI and UserActivity data (8809021)

Because of a limitation in the IE userData persistence behavior (see Supported Platforms section for details), the userActivity data for previous requests may be partially or sometimes completely unavailable when accessed from pages with a different URL than when it was originally saved.

Calendar Binding Data Type Support

Due to the lack of support in model to convert data of type java.util.Date to java.sql.Date, a runtime error will occur if
java.sql.Date is specified as NDType in the calendar page definition file.  Please use the supported types instead:

  • oracle.jbo.domain.Timestamp
  • oracle.jbo.domain.Date
  • java.sql.Timestamp
  • java.util.Date

 

User Specified Window Names

In this release we start to support user specified window names. A user can launch a window and give it a name, and we will continue
to use that name if it's valid. Currently the supported character set for window name is : [a-z][A-Z][0-9]_

Skinned Icons Resize (10058868)

Until recently there were limitations with skinning icons that -tr-rule-ref and -tr-inhibit were not supported. Further, the skin properties were not inherited from base skin for icon selectors. We fixed these limitations to make the icon selector behavior consistent with general skinning style selectors. Now that we inherit the skin properties for icons, if there were 'content' and other properties like 'width' and 'height' set, and you override just the 'content' property in your custom skin, you would inherit the 'width' and 'height' from the base skin. While this is a change in behavior, it is a change in right direction. If this behavior is not desirable, skinners can use -tr-inhibit to inhibit some properties or 'tr-inhibit: all' to inhibit all properties before overriding the 'content' property.

Popup components with the childCreation attribute set to "deferred" often
render blank with the first invocation

This issue arises if you use the popup component with a region and use the setPropertyListener tag to establish the activation of the region. The setPropertyListener tag with a popupFetch type will not be invoked for the initial fetch establishing the initial content delivery. This is because the markup that defines the setPropertyListener tag is defined within the popup's body. With the option to defer creating the children, the body is not processed until the first fetch for content. The popup fetch event listener (setPropertyListener) is processed in the Apply Request Values phase prior to when it is created in the Render Response phase. The workaround is to use the "popupFetchListener" method expression (PopupFetchEvent server-side event) to establish state that would have been established using the setPropertyListener.

RichText Editor Error Messages (11686814)

It is recommended that the application developer add a validation rule for situations where the Error Message returned by the RichText Editor would include the text contained in the RichText Editor and that text may be large enough to not be properly displayed by the browser.

Facelets Applications Will Lose State After Failover (12382285)

Due to the issue in Jthe SF reference implementation (2048), Facelets applications running in clustered environments will lose state after failover. End users experiencing error messages after faiover should be advised to refresh the page.

 

ADF DVT Graph and Gauge (6904435, 6016950, 11716978)

    • Firefox does not print Flash content, which is the default imageFormat for DVT Graph and Gauge. Flash content, including ADF DVT Graphs and Gauges, prints fine when the browser is IE. Applications should use printable page mode to print Flash content or set imageFormat to PNG. (6904435, 6016950)
    • If using Internet Explorer 9, the users are advised to use the latest Flash plugin version for that browser. (11716978)
    • The following are now deprecated:
      • <dvt:numberFormat> tag is now deprecated. Developers should use the standard Trinidad converted tags, e.g. <af:convertNumber>.
      • imageFormat="AUTO" is now deprecated. Developers should use the new flash-player-usage context parameter in adf-config.xml.

ADF DVT Pivot Table (8895660, 8316539, 11901316, 9927815)

    • In order to store edits, the PivotTable needs to be 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 (8895660)
    • When using Internet Explorer in BIDI mode the PivotTable scrollbars can sometimes reset to their original position (8316539)
    • Size column of editable pivot table misfunctioning in Chrome 10 (11901316)
    • Leading zeros are not carried from the pivot table to exported Excel (9927815)

ADF DVT Pivot Filter Bar (8777349)

    • JAWS tabbing through the PivotFilterBar incorrectly reads the URL (8777349)

ADF DVT Gantt Chart (8684652, 9868647, 11735740, 1189693)

    • Issue when zoom using scroll wheel using Safari browser, CTRL-Scroll wheel is reserved for Browser font resizing (8684652)
    • Time value in tooltip of DataChangeListener incorrectly calculated (9868647)
    • Scheduling gantt region has "no row header found" (11735740)
    • Accessibility/jaws issue on table side of gantt (11869693)

ADF DVT Hierarchy Viewer (12410836)

    • Hierarchy Viewer fails to display when rangesize is set to -1 for iterator. (12410836)

ADF DVT Geographic Map

    • <dvt:numberFormat> tag is now deprecated. Developers should use the standard Trinidad converted tags, e.g. <af:convertNumber>

ADF DVT Thematic Map (12433342)

    • Zoom and center issues with point data layer when only one point, or an empty region is selected (12433342)

JSF Upgraded to 2.0

The JSF version packaged in 11.1.2.0.0 has been upgraded to 2.0, which may cause applications using the exact-match flag
set to true to fail to deploy.  If your application is being opened or used for the first time in 11.1.2.1.0, and you did not previously
implement the solution before when using 11.1.2.0.0, then this solution is provided:  The solution is to set exact-match to false.
JSF 2.0 is backwards compatible with previous versions and should not cause any problems.

ADF Faces and Data Visualization Design Time

    ADF Skin Editor

A new JDeveloper editor is available starting in 11.1.2.0.0 for creating and editing ADF skin files. The core features include:

  • ability to extend from one of the ADF skins as a starting point
  • selector tree listing all the possible skin selectors for ADF Faces and DVT including style classes, global aliases, and pseudo-elements
  • preview pane that renders components and reflects changes made to their skin selectors in real-time
  • inheritance information showing where existing, default properties values are coming from in the skin hierarchy
  • support for seeing which set of components and selectors are utilizing a particular global alias
  • support for editing skin selectors for a particular theme
  • image generation capabilities based on color aliases when extending a fusionFx-simple skin

Applying an ADF Skin that Extends the Fusion Simple ADF Skin to a 11.1.1.4 or 11.1.1.5 Web Application

If you develop an ADF Skin that extends the new Fusion Simple family of skins (for example, fusionFx-simple-v1.desktop) that you want to apply to an 11.1.1.4 or 11.1.1.5 web application, you must also add the fusion-simple-skin.jar file to your web application. The fusion-simple-skin.jar file contains the Fusion Simple family of ADF skins that you extend for these releases (11.1.1.4.0 and 11.1.1.5.0). You download the fusion-simple-skin.jar file from http://java.net/projects/jdev-extensions/downloads/download/skins/fusion-simple-skin.jar.&nbsp;&nbsp;
For information about how to add this JAR file to your application, see the Importing ADF Skins from an ADF Library JAR section in the Skin Editor's User Guide.

Component Palette Reorganization

The ADF Faces components in the component palette were reorganized into new accordions and display groups. This was done to assist users in locating and identifying components more efficiently and effectively by making the organization more predictable and usable. The reorganization will also accommodate the addition of new components in the future.

Support for Building Nested Templates

Previously, one was only able to utilize a single page template in their page (chosen during the creation of the page). Also, one was not able to include another page template while creating a page template definition. That restriction has been removed and a new Template item is now available in the component palette which can be DnD'ed onto either a page template definition or a regular page. A dialog will appear prompting the user to choose a page template to point to. With this new feature, the ability to nest page templates is now possible.

Conversion Support for ADF Faces Layout Components

The ability to convert between various ADF Faces layout components was reintroduced in 11.1.2.0.0 (specifically, decorativeBox, group, panelAccordion, panelBorderLayout, panelBox, panelFormLayout, panelGroupLayout, panelHeader, panelList, panelSplitter, panelStretchLayout, panelTabbed, showDetailHeader, and toolbox). For cases that cannot be resolved algorithmically, a new Convert dialog will be shown to prompt the user for direction.

ADF DVT Databinding and Design Time (8872334, 12399848, 10318124, 12591644)

    • Live data preview in the DVT Graph, Gauge, and Pivot Table binding dialogs is not available during design time if the application is configured with ADF Security. (8872334)
    • Live data preview in the DVT Graph, Gauge, and Pivot Table binding dialogs is not available during design time if the component is bound to a POJO Data Control. (12399848)
    • Binding a DVT Gauge and DVT Gauge Set to the exact same rowset iterator can lead to unpredictable results at runtime. To work around this issue, the Gauge and Gauge Set should be data bound to separate collections. (10318124)
    • Automatic partial page rendering for single data-bound Gauges does not work consistently. To work around this issue, configure partialTriggers on the Gauge instance. (12591644)

ADF Business Components

Duplicate View Instance Usages in an Application Module Definition Leads to Compiler Error (12413907)

Starting with JDeveloper 11.1.2.0.0, duplicate entries of view instances that appear in the application module .xml file, will be reported as an error during compilation. This is a new compiler behavior that is intended to prevent users from creating corrupt XML definitions. If you migrate an application into JDeveloper 11.1.2.0.0 or later, the duplicate XML elements will fail to compile after migration has been completed. In this case, you will need to edit the XML definition to manually remove the duplicate entries and then continue to build the application. Duplicate view instance usages appear in the application module definition like this:

 <ViewUsage
    Name="MyViewObject"
    ViewObjectName="com.model.view.MyViewPackage"/>
<ViewUsage

 

Using ADF Model Tester to test Application Module Deployed as an EJB Session Bean (11884503)

When you enable an application module to support EJB Session Bean, we no longer generate the Configuration for testing in integrated server. You can create the bc4j.xcfg entry for testing by following these steps:

  1. Select Run > Start Server Instance to start the integrated WebLogic server
  2. Select Project Properties... > Deployment and create a Business Components EJB Session Bean deployment profile
  3. Select "IntegratedWebLogicServer" in the Deploy to Connection dropdown
  4. Click Next > Finish

Now you can deploy the EJB Session Bean and select the new configuration (Type=EjbWls) to run the Tester.

Extension SDK

In this release the Extension framework as been changed. It is now based on an OSGi framework and extension written for previous
releases will not run out of the box in this new release. Please read the new Developers Guide for JDeveloper Extensions under
Help --> Table of Contents

Translation and Globalization Issues

Font Issue

When running Jdeveloper in Japanese Windows MUI machine, you may find some Japanese Character are displayed as square, it's caused
by the font used by Jdeveloper UI is not installed in the MUI env.

This font issue does not exist in Native Japanese Windows machine and Linux machine.

Oracle Help for the Web (OHW-RC)

11gR1-PS4 OHW help application fails to run after the user upgrades the Oracle Help system files from 11gR1-PS4 to 11gR2 (12572334)

The user must update and rebuild the OHW help application, because the ohw-rcf-webapp.zip configuration file has been updated in 11gR2. For more information about the ohw-rcf-webapp.zip configuration file, see "Understanding OHW Deployment" in the Oracle Fusion Middleware Developer's Guide for Oracle Help.

Follow these steps to update the OHW help application:

1. Copy the helpset files and the configuration files from the old OHW help application to the new OHW help application location.

2. Update the web.xml file and add the following servlet mapping information.

<\!-\- Route the OHW-RC resources through the resource servlet. \-->
<servlet-mapping>
&nbsp; <servlet-name>resources</servlet-name>
&nbsp; <url-pattern>/ohr/*</url-pattern>
</servlet-mapping>

The following example shows a sample web.xml

<context-param>
<param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name>
<param-value>oracle.adf.view.rich.change.FilteredPersistenceChangeManager</param-value>
</context-param>
<filter>
<filter-name>trinidad</filter-name>
<filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>trinidad</filter-name>
<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>resources</servlet-name>
<servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/afr/*</url-pattern>
</servlet-mapping>
<!-- Route the OHW-RC resources through the resource servlet. -->
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/ohr/*</url-pattern>
</servlet-mapping>
<!-- configuration for product1 help front servlet -->
<servlet>
<servlet-name>product1</servlet-name>
<servlet-class>oracle.help.web.rich.OHWServlet</servlet-class>
<init-param>
<param-name>ohwConfigFileURL</param-name>
<param-value>/helpsets/product1/ohwconfig.xml</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<!-- configuration for product2 help front servlet -->
<servlet>
<servlet-name>product2</servlet-name>
<servlet-class>oracle.help.web.rich.OHWServlet</servlet-class>
<init-param>
<param-name>ohwConfigFileURL</param-name>
<param-value>/helpsets/product2/ohwconfig.xml</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
<!-- servlet mappings for the OHW-RC front servlets -->
<servlet-mapping>
<servlet-name>product1</servlet-name>
<url-pattern>/product1/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>product2</servlet-name>
<url-pattern>/product2/*</url-pattern>
</servlet-mapping>
<!-- OHW-RC servlet filter definition and mappings -->
<filter>
<filter-name>OHWRCFRequestFilter</filter-name>
<filter-class>oracle.help.web.rich.OHWFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>OHWRCFRequestFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>

 

The user can now build and run the OHW help application.

EM specific instructions to get online help up and running after patching

1. In em.war file (inside em.ear) update web.xml to include the following servlet mapping:

 

<!-- Route the OHW-RC resources through the resource servlet, where resources is org.apache.myfaces.trinidad.webapp.ResourceServlet configured as shown in web.xml shown above. -->
   <servlet-mapping>
     <servlet-name>resources</servlet-name>
     <url-pattern>/ohr/*</url-pattern>
   </servlet-mapping>

2. Copy help pages from
oracle_common/modules/oracle.help_5.0/ohw-rcf-webapp.zip to
oracle_common/sysman/archives/applications/11_1_1_0_0_emcore.war

3. Bounce the server and open the OHW help application again. It will work this time.

 

 

 

Accessibility Issues

    Accessibility: 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.

    Accessibility: 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.

    Accessibility: 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.

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.

Viewing a page preview from the visual editor (8351673)

When viewing a page preview from the visual editor using the default browser users should:

  1. From the main menu, click Tools=>Preferences...=>Shortcut Keys
  2. Locate the JSP and HTML Visual Editor
  3. Preview in Browser and assign a key
  4. Click OK and push button to close preferences.

This option will now be keyboard accessible.

 

Message dropdown not accessible (8728885)

When working in a facelet and attempting to drop a JSF html message component onto the page, a dialog appears to allow the user
to specify the ID to which to attach the message. The workaround is to use the Property Inspector to change the 'for' property of h:message.


 

 

 

 

     

     

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065, USA
http://www.oracle.com

Worldwide Inquiries:
1-800-ORACLE1
Fax 650.506.7200

Copyright © 1997,2009, 2010, 2011 Oracle and/or its affiliates.
All rights reserved.