This document contains information on the following subjects:
This release of BEA Workshop provides numerous issues fixes and improved performance to enhance the development experience.
Workshop now supports the Tuxedo Control, which allows your applications to connect to Tuxedo services.
Workshop is now integrated with the WorkSpace Studio launcher at BEA_HOME/workSpaceStudio_1.1/workSpaceStudio/workSpaceStudio.exe.
Workshop Studio bundles Adobe Flex Builder 2 and Flex Charting as a third party add-on (for Windows only).
Features of Adobe Flex Builder 2 include:
To install Adobe Flex Builder 2 into Workshop Studio see Installing Adobe Flex 2.
Note that Adobe Flex Builder 2 and Flex Charting are only supported on Windows.
For more information on platform support, including hardware and software requirements, see the Supported Platforms web site.
To comply with the Eclipse Public License, BEA has made source code for derived work available for download at
http://www.oracle.com/technology/community/welcome-bea/index.html
When you install WebLogic Portal 10.2, required patches are installed automatically. If you uninstall any of these patches and need to reinstall them, use the information in the table below in conjunction with the Smart Update utility to reinstall and apply the patches. For detailed information on using Smart Update, see Installing Patches and Maintenance Packs Using Smart Update on e-docs.
Table 1 lists the known limitations found in Workshop for WebLogic.
The first time you run Project > Clean after importing a project, Workshop for WebLogic may not clean all of the files from the .apt_src directory
|
|
When a web service or other artifact is in a web project that is part of more than one EAR, the Run on Server can produce the wrong URL.
|
|
Invocation of buffered Control methods will fail at runtime if deployed (via the IDE) to a server with more than one JMS Server
The IDE will auto-deploy required Workshop libraries when deploying an application. The use of @MessageBuffer on Control methods creates a dependency on application-scoped JMS resources in the weblogic-controls library. If the weblogic-controls library is deployed (by the IDE) to a server with more than one JMS server, the library will deploy, but the application-scoped JMS resources will not be available. This is because the IDE depends on default sub-module targeting, and default sub-module targeting relies on the target containing exactly one JMS Server. A message similar to the following warns that there is an issue with the deployment:
<The JMS module named "WlwRuntimeAppScopedJMS" inside
Note that even though there is a warning message, the library is deployed to the server. This means that applications that are dependent on the library will also successfully deploy. However, invocation of buffered Control methods will fail at runtime with a message similar to the following:
"Failed to invoke end componentFailed to invoke methodMessage |
|
Buffered operations on a ServiceControl must be void. However the Message Exchange Pattern (MEP) in the underlying WSDL can be either request/response (with an empty response), or oneway (a request with no response).
In the case of a request/response MEP over JMS, the presence of @MessageBuffer will cause the request to deadlock and eventually timeout. The following warning message will generally be produced:
Potential blocking operation javax.xml.rpc.soap.SOAPFaultException: Failed to receive message java.io.IOException: Request timed out
Workaround: If you can influence the design of the target JWS, having the JWS operation annotated with @Oneway will direct that the underlying MEP be oneway, and will avoid this situation. If you can not influence the design of the target JWS, then the workaround is to add the TransactionAttribute annotation to the ServiceControl operation:
@MessageBuffer |
|
Description: An issue may surface when a 9.2 Beehive application is deployed on WebLogic Server 10.0. The symptom with this scenario is a java.lang.IllegalStateException being thrown. The underlying issue is with the javax.servlet.ServletException which changed from Servlet 2.4 to Servlet 2.5.
Workaround: Upgrade the application to use Beehive 10.0 libraries (which work with either Servlet 2.4 or Servlet 2.5). If the 9.2 application cannot be compiled in 10.0, then manually updating the deployment descriptors in the 9.2 application EAR to use the 10.0 Beehive libraries will resolve this issue. For example:
|
|
Users who upgrade an 8.x application to a 9.x/10.x application may experience issues when making multiple method calls to a JDBC control from a single page flow method
http://download.oracle.com/docs/cd/E13226_01/workshop/docs92/ws_platform/upgrading/conChangesDuringUpgrade.html
Users who upgrade an 8.x application to a 9.x/10.x application may experience issues when making multiple method calls to a JDBC control from a single page flow method. The crux of the issue is that when the first call is made to the JDBC control a new transaction is created by our transaction interceptor. When that call returns the transaction is either committed or rolled back.
On the next call to the JDBC control a new transaction is created, but the JDBC connection being used by the control cannot be used in another transaction (it has been associated as a resource of the first transaction).
The behavior in 8.x page flows was for the JDBC control to release its JDBC connection after each method invocation. The transaction scope for a control method being invoked from a page flow was to start a transaction at the beginning of the control method invocation, and end the transaction on the return of the method. If the control rolled back the transaction, all operations performed within that transaction would be rolled back as well.
|
|
When multiple web service controls, with callbacks, have identical class names (ignoring package name) an error will occur in jwsc. This error will appear in the publish step in the ide, during the usable step in exported ant scripts, or when exporting an ear file from the ide. In previous versions of Workshop the exported ant scripts would incorrectly report that the assemble step had succeeded even though this condition was present. This was because the ant script did not attempt to run jwsc on garnered java files.
|
|
Service control generation based on WSDL callbacks named with underscores and numbers can result in incorrect callback method names. This will occur if a lower case letter follows an underscore or number.
a_b a_B javax.xml.rpc.JAXRPCException: SOAPFaultException - FaultCode |
|
Workshop startup.jar cannot be used to run in headless mode on Linux unless an additional system property is defined
|
|
Hibernate JPA projects created in Workshop 10.1 or imported from Workshop Studio 3.x fail to deploy on Weblogic Server 10.0. The below workaround will help Hibernate JPA projects deploy but redeployment will require a server restart
<prefer-application-packages> |
|
After upgrade from Workshop version 8.1.x to 10.2 or migration from 9.2 through 10.0 to 10.2 the initial build of the upgraded application may produce an incomplete AppXRay database for web projects that have the AppXRay feature enabled. In this case the user may notice that the App Xaminer view does not show all dependencies correctly.
|
|
When deploying a web service to pre-MP1 versions of WebLogic Server 9.2, you may encounter a ExceptionInitializerError.
(2) Or add the following flag to both the workSpaceStudio.ini file and WebLogic Server’s start script for the VM.
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 |
|
The Kodo license bundled with Workshop Studio 3.3 release has expired, so older applications which have the license file at <Project_Home>/src/license.bea need a manual upgrade.
Platforms: Applies to JPA/Kodo applications upgraded from Workshop Studio 3.3 to Workshop 10.1 and later.
|
|
Licensing concerns when Workshop Studio 10.2 and Workshop for WebLogic 10.2 are installed in same the BEA Home
|
|
When WebLogic Server fails to start in Workshop, the Console view may be closed making it difficult to monitor the errors associated with the failure to start.
1. In the Server view, double-click the server instance to open the Server Overview. 2. In the section Startup and Deployment, uncheck Launch WebLogic server in Eclipse Console. 3. Start WebLogic Server using the start up script located at <domain_home>\bin\startWebLogic.cmd|.sh. 4. To view the errors associated with the start up failure consult the command shell console output. |
|
WorkSpace Studio About Box may stop displaying plugin and configuration details after a BEA Product is removed from the BEA Home directory
After uninstalling a BEA product from your BEA Home directory in which you have other products installed, the Plugin Details and Configuration Details buttons in the WorkSpace Studio IDE about box (Help > About BEA WorkSpace Studio) may stop working. This is due to the fact that under some circumstances empty plugin directories may still be present after the plugins are removed and the IDE expects to locate, but can not find, plugin details in those directories.
|
|
When attempting to launch WorkSpace Studio, the following error is returned:
/bea/jdk150_11/jre/bin/java: symbol lookup error: /bea/tools/eclipse_pkgs/1.1/eclipse_3.2.2/eclipse/configuration/org.eclipse.osgi/bundles/104/1/.cp/libswt-mozilla-gtk-3236.so: undefined symbol: _ZN4nsID5ParseEPKc
|
Table 2 lists the resolved problems in Workshop for WebLogic.