Oracle JDeveloper 10g is a complete and integrated development environment
for standards-based SOA applications. The Oracle JDeveloper 10g Release 3 (10.1.3)
version adds many new features including a new look and feel, a greatly improved
coding environment with extensive refactoring options, support for the latest
Java standards (J2SE 5.0, J2EE 1.4, EJB 3.0), and visual JSF development. A
visual and declarative approach and the improved Oracle Application Development
Framework (Oracle ADF) work together to simplify application development and
reduce mundane coding tasks, offering developers unparalleled productivity regardless
of their choice of technology stacks and deployment platforms.
Oracle JDeveloper (10.1.3.1.0) extends the IDE features from the previous release
by adding integrated SOA development tools to provide an Integrated Service
Environment workbench. In particular, BPEL (Business Process Execution Language)
and ESB (Enterprise Service Bus) tooling is now fully integrated into JDeveloper.
In addition, JDeveloper's core IDE features for EJB 3 and JPA (Java Persistence
API) have been extended, and made fully up to date with the final EJB 3 specification.
Incompatibility between internal CVS client and CVSNT server
(5362113)
In some cases binary files can become corrupted when using JDeveloper's internal
CVS client against a CVSNT server. The workaround is to use CVSNT's client within
JDeveloper. This can be configured on the Versioning |CVS panel of IDE preferences.
Deployment Issues
EJB web service fails to deploy to JDeveloper's embedded
server (5132396)
JDeveloper may exceed the length of the path names permitted by Windows when
you compile an EJB session bean with a web service annotation. The path name
JDeveloper generates for the web service class file is concatenated from three
elements: the path to the application-deployment folders (set by system and
not editable), the path to the web service source folder (also set by system),
and the path to the class file specified by its package name (set by user and
must be as short as possible).
For example, the following path would be created for a web service class file,
where the user-specified portion of the path name is based on the package name
com.oracle.myapp.ejb.webservice.test.
oracle.j2ee.ws.common.tools.api.SeiValidationException: Interface
<classname>.SessionEJBBeanPortType: The class could not be loaded from
the class path.
You can workaround this limitation by shortening the name of the package you
enter when you create the EJB session bean. For example, instead of com.oracle.myapp.ejb.webservice.test,
as shown in the above example, the package name com.oracle.myapp
will result in a legal class path length.
ADF web application with EJB3 model project dependency
fails to deploy (5237303)
When you deploy an ADF web application WAR file to Standalone OC4J you may
encounter the following error due to multiple persistence unit definitions resulting
from an EJB3 model project dependency:
DeployerRunnable.run[application1:ejb3_mdnav_adffaces] - Multiple persistence
units with name "model" are defined at the same scope.oracle.oc4j.admin.internal.DeployerException:
[application1:ejb3_mdnav_adffaces] - Multiple persistence units with name "model"
are defined at the same scope.
To avoid this error, update the ViewController project settings to remove the
dependency on the Model project before deploying the ADF web application to
Standlone OC4J.
Deploying JDeveloper deployment profiles to archive files
on the file system
When deploying JDeveloper deployment profiles to an archive file the default
behavior is to deploy the archive as standard J2EE. In order to deploy an archive
to a file for a specific application server platform to incorporate platform
specific descriptor handling, the user must set the Target Connection in the
Deployment Profiles - Platform page. The Target Connection can only be set to
something other than the default (J2EE) after creating an application server
connection in the connection navigator.
Database Issues
Entity created only for first table in entity beans from
tables in Oracle Lite (5251201)
Oracle Lite version 10.2.0.2 does not support standard JDBC metadata for column
definitions, resulting in an inability to create EJB entities. We expect this
to be fixed in Oracle Lite 10.2.0.3.
Modeling Issues
Refactoring context menu and UML (4463153)
From the App Navigator context menu the refactoring submenu is visible for
navigator packages containing UML artifacts. However, refactoring the package
will NOT cause UML artifact to be refactored, though Java and other types will
be refactored as expected.
Java modeler accessibility (4541424)
The Java Modeler's popup code editor is not currently accessible when using
JAWS screen reader. The workaround is to invoke 'Go To Source' instead of 'Edit'
for Java elements on the diagram, which will invoke the main code editor.
Toplink Issues
Importing tables with multibyte characters (5254287)
When importing database tables named with multibyte characters, you must change
the JDeveloper encoding to UTF-8.
In 10.1.3.1 the lifespan of an entity's Persistence Context is strictly tied
to the lifespan of its associated transaction, since by default, a PersistenceContext's
type is PersistenceContextType.TRANSACTION.
This requirement was relaxed in 10.1.3, and some applications were found to
be dependent on this requirement not being met.
To operate under the stricter requirement in 10.1.3.1, EJB 3.0 Stateless Session
beans migrated from JDev 10.1.3 and interacting with web clients may need to
be changed to Stateful Session beans.
to allow web clients to perform additional operations on entities returned from the (newly Stateful) Session bean.
Running EJB 3.0 applications (5524015)
EJB 3.0 runtime is different 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
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.
Web Services Issues
Top-down SOAP 1.2 services changed to SOAP 1.1
after editing (5499466)
If you create a web service top-down from a WSDL that contains SOAP 1.2 bindings,
then modify that service in the web service editor, the bindings are changed
to SOAP 1.1.
The workaround is in the Web Services Editor dialog, manually deselect SOAP
1.1 Binding and select SOAP 1.2 Binding instead.
Top-down service with one-way operations changed
to two-way methods after editing (5499473)
If you create a top-down web service that has one-way operations, then use
the Web Service Editor to change the service or invoke Regenerate Web Service
from Source, the one-way operations are changed to two-way operations.
The workaround is in the Web Services Editor dialog, manually check the Create
One-Way Operations From Void Methods checkbox.
Top-down web services generated with enumerated
types fail validation (4740097)
When you generate a top-down web service a WSDL with enumerated types, subsequent
changes made to the service in the Web Service Editor cannot be committed due
to an error in validation.
Deleting Init Param or Header in a web service
handler causes an error (4696318)
If you have created a web service handler that uses an Init Param and/or a
Header, and you subsequently edit the handler to remove the Init Param or the
Header, JDeveloper displays an error message.
The workaround is to remove the handler, then recreate it without the initial
parameter.
Web service proxy fails when running with reliability
settings (4644877)
When you run a proxy to a web service that has reliability enabled you may
find that it fails, and on examination with the HTTP Analyzer the SOAP message
returned from the server has an empty body. This can occur because the default
value of Expiry Time on the Operation Settings tab of the proxy reliability
wizard is 1 second.
The workaround is to increase the expiry time to 2 seconds or more.
'Invoke' button not present in EM for testing EJB3.0
web service on external OC4J (4769395)
If you deploy an EJB3.0 web service to external OC4J, and try to test it from
Oracle Enterprise Manager, the Invoke button is not always present. There is
no workaround.
Invalid web service endpoint in generated proxy
for multi-port WSDLs (4867854)
When you create a proxy to a web service with more than one port, the proxy
may be generated with an invalid endpoint for the web service.
The workaround is to examine the WSDL to find the correct endpoint URL, and
paste this into the generated proxy class.
Runtime exception when more than one web service
exists in a project (4861145)
If you create two or more web services in a project that use the same mapping
file, you will get a runtime exception.
The workaround is:
For bottom-up web service generation, specify a serviceName argument value
that does not already exist for the second web service.
For top-down web service generation, make sure the web services are each
in a different WAR for deployment so that the same deployment descriptor is
not used.
JavaServer Faces (JSF) Issues
In JSF 1.1_02 pages under /WEB-INF fail to load
JDeveloper 10.1.3.1 upgrades to the JavaServer Faces reference implementation
version 1.1_02. This maintenance release of the JSF runtime from Sun introduces
a new restriction preventing the processing of any JSF page located in the ./WEB-INF
directory (or subdirectory thereof). If your JSF applications contain pages
in the WEB-INF directory, you will need to move those pages to another directory
under the web root other than WEB-INF for them to function correctly. If your
JSF pages use ADF Model data binding, after moving the JSP/JSPX pages from ./WEB-INF
(or subdirectory) to a new directory under your web root, you will need to reflect
the change in the "path" value inside the <pageMap> section
of your DataBindings.cpx file. For example, if your page previously had a "path"
value of "/WEB-INF/page/Test.jspx" and you moved this Test.jspx page
to ./public_html/page/Test.jspx -- where ./public_html is the HTML root directory
of your view controller project -- then you must edit the value of the path
and change it from "/WEB-INF/page/Test.jspx" to "/page/Test.jspx".
Miscellaneous Issues
SOA Suite documentation
Please refer to the Oracle Application Server documentation library for the
most up-to-date documentation available for BPEL Process Manager and Enterprise
Service Bus.
Using JAZNMigrationTool with JDeveloper
The JAZNMigrationTool provides a way to migrate the contents of one store to
another that can then be loaded to the LDAP directory. The command to be used
is:
Below is an example of migrating all users, roles, and JAAS policies from embedded-oc4j\config\system-jazn-data.xml
to j2ee\home\config\system-jazn-data.xml
set CLASSPATH=JDEV_HOME\j2ee\home\jazn.jar;%CLASSPATH%
JDEV_HOME\jdk\bin\Java oracle.security.jazn.tools.JAZNMigrationTool -w welcome
-sf JDEV_HOME\jdev\system\oracle.j2ee.xxxx\embedded-oc4j\config\system-jazn-data.xml
-df JDEV_HOME\j2ee\home\config\system-jazn-data.xml -dt xml
Note that JDEV_HOME should be the directory where they install JDeveloper.
XXXX represents the final build number.
For more information see Java JAZNMigrationTool -help.
Running ADF installer against Application Server 10.1.2
instance (4897250)
When running the ADF installer within JDeveloper (Tools--> ADF Installer)
against an Application Server 10.1.2 instance, the user may encounter the error
"Cannot finish the installation" even if the server is shut down.
In addition to stopping the Application Server instance, the user must also
shut down the Application Server Control Manager(EM) service before running
the ADF Installer against the Application Server 10.1.2 instance.
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.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065, USA http://www.oracle.com
Bookmark
