Table 1 Known Limitations in BEA Workshop Version 10.2
|
|
|
|
|
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 user imports a project including build directories such as .apt_src, all files in that directory might not get removed the first time a clean is performed. This only happens the first time, subsequent cleans correctly handle the generated directories.
Workaround: Manually delete the files in the .apt_src directory when performing a clean the first time after import. Once deleted, the new files that go into that directory are correctly handled by the clean action.
|
|
|
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.
Using the Run on Server action on artifacts in a web project that is associated with multiple EARs in the workspace can launch the browser to the incorrect URL. That is, it will use the URL associated with the last EAR with which is was associated.
To workaround this issue, you can either
a) close the EAR that is not to be used for the launch,
b) remove the web project from the EAR that is not used for the launch, or
c) manually update the URL in the browser to hit the correct EAR.
|
|
|
Lost JVMTI events (especially breakpoints) when debugging with JRockit
When debugging with the JRockit JVM you may experience performance problems and missed breakpoints.
Workaround: Update to JRockit 5.0 R27.1 or later.
|
|
|
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:
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:
Note that this situation is most likely to occur when using domains that were not created with support for "Workshop for Weblogic Platform.
Manually deploy the library using the weblogic.Deployer command. The form of the command is:
-adminurl t3://localhost:7001
-name weblogic-controls-10.0
-source %WL_HOME%/common/deployable-libraries/weblogic-controls-10.0.ear
-submoduletargets cgJMSServer@WlwRuntimeAppScopedJMS@WseeJmsServer
-library -libspecver 10.0
- WseeJmsServer is the name of the JMS Server to host the application-scoped
- targets is the development server
The command updates the library definition in config.xml. Therefore it only needs to be run once.
|
|
|
Buffered methods on ServiceControl may fail over JMS protocol
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:
The resulting error message will include text similar to:
Note: this only occurs when the transport protocol for the request is JMS.
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:
Note that the presence of the @TransactionAttribute will not change the transactional behavior of actions that occur within the calling application.
|
|
|
Servlet 2.5 Implementation In WebLogic Server 10.0 Can Break 9.2 Beehive Applications
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.
Platforms: WebLogic Server 10.0 or higher
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:
For each .war in the 9.2 .ear, modify the following section of the web-inf/weblogic.xml:
<wls:library-ref> <wls:library-name>beehive-netui-1.0</wls:library-name> <wls:specification-version>1.0</wls:specification-version> <wls:implementation-version>1.0</wls:implementation-version> </wls:library-ref>
<wls:library-ref> <wls:library-name>beehive-netui-1.0.1-10.0</wls:library-name> <wls:specification-version>1.0</wls:specification-version> <wls:implementation-version>1.0.1.1</wls:implementation-version> </wls:library-ref>
|
|
|
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
Due to a change in transaction scope from page flows which has been documented in
See the section labeled: 'Controls are Not Automatically Run Within the Scope of a Transaction'
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.
Workaround: There are several workarounds available:
1) If you do not want to use transactions (they were implicit in
8.x) the transaction interceptor annotations (inserted by the upgrader) can be removed from the control methods.
2) If you want to use transactions, create a JTA transaction in the page flow method and either commit or rollback once the calls to the JDBC control are completed.
|
|
|
Duplicate simple class names are not supported for web service controls with callbacks
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.
Workaround: When using web service controls (SerivceControl) with callbacks make sure that each control file has a unique un-qualified class name. Differing the package name is not sufficient.
|
|
|
Service control generation can produce incorrect callback method names
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.
For example, the following WSDL callback names:
will result in the generation of the following callback method names:
Note that the first character after a number or underscore has been capitalized.
When the method is invoked, the following error will result.
Workaround: Avoid callback method names with a lower case letter following an underscore or number.
|
|
|
Workshop startup.jar cannot be used to run in headless mode on Linux unless an additional system property is defined
The startup.jar provided with Workshop cannot be used to run in headless mode on Linux, unless the following system property is set to true:
Workaround: Launch workshop in headless mode with the system property m7.disable.swt.init set to true. Note that the DISPLAY system property must not be set for this workaround to succeed.
|
|
|
Issue with Hibernate JPA deployment on Weblogic Server 10.0
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
Platforms: Workshop 10.1 and later
Workaround: For EAR Projects - Modify weblogic-application.xml and add the following
For Web Applications - Add the web project to an EAR and then modify weblogic-application.xml as described above.
Note: Redeployment of the project requires a server restart.
|
|
|
After renaming project, old project is not undeployed from the server
If you rename a project that belongs to an EAR, the previous project name will not be undeployed from WebLogic Server.
Workaround: To remove the project from the server, undeploy and redeploy the application from WebLogic Server.
|
|
|
Problems deploying EJB project upgraded using command line upgrader
You may encounter problems deploying an EJB project that has been upgraded using the command line upgrade tool upgradeStarter.
Workaround: Upgrade the project using the IDE instead of the command line tool. To upgrade using the Workshop IDE.
|
|
|
Incomplete AppXRay database may be produced after upgrade
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.
Platforms: Workshop 8.1 and later
Workaround: To correct this situation clean and rebuild the workspace (by selecting Project > Clean).
|
|
|
ExceptionInInitializerError deploying web service on WebLogic Server 9.2
When deploying a web service to pre-MP1 versions of WebLogic Server 9.2, you may encounter a ExceptionInitializerError.
Platforms: Workshop 10.2 and WebLogic Server 9.2
Workaround: Implement one of the following solutions:
(1) Upgrade your WebLogic Server 9.2 installation to 9.2 MP1 or higher.
(2) Or add the following flag to both the workSpaceStudio.ini file and WebLogic Server’s start script for the VM.
|
|
|
Web application deployment descriptor graphical editor doesn't support <resource-ref> elements
Workshop’s graphical editor for deployment descriptors does not support <resource-ref> elements. The Deployment Descriptor Elements tree view (located above the source editor) and the Outline view do not support adding or editing <resource-ref> elements.
Workaround: Use source view to add and edit <resource-ref> elements.
|
|
|
Filter dispatcher warnings from JSF webapp deploy
The version of MyFaces bundled with Workshop logs warnings to the WebLogic Server console due to a bug in the MyFaces web.xml parser. This bug is tracked here:
http://issues.apache.org/jira/browse/MYFACES-1415
The warnings are harmless and result in no loss of functionality.
Workaround: These warnings can be ignored.
|
|
|
Some Workshop text fields do not support Ctrl+V paste
In the presence of the WebLogic Portal Eclipse plugins, some of the Workshop text fields do not support the Ctrl+V paste operation.
Workaround: Manually type text into these text fields.
|
|
|
Linux: Workshop JSP design view does not support drag and drop
On Linux, the Workshop JSP design view does not support drag and drop from the Design Palette.
Workaround: Drag-and-drop from the Design Palette onto the source view.
|
|
|
Minimal support for JSP XML syntax
The Workshop JSP designer does not support JSP's XML syntax and gives warnings when parsing XML JSPs. For example, use of an entity reference “&” for the character "&" will report a warning in the Problems view that deployment is prevented.
Workaround: These warnings can be ignored: JSP XML syntax does not hinder deployment of the application.
|
|
|
Projects upgraded from Workshop Studio 3.3 may require manual upgrade of Kodo license
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.
Create a new project that supports JPA/Kodo. For details, see http://edocs.bea.com/wlw/docs101/guide/ormworkbench/conAddingEJB3Support.html
Copy the license.bea file from the new project into the original project’s src folder.
|
|
|
Licensing concerns when Workshop Studio 10.2 and Workshop for WebLogic 10.2 are installed in same the BEA Home
If a user has both Workshop for WebLogic 10.2 and Workshop Studio 10.2 installed in the same BEA_HOME and either the Workshop Studio trial or full license expires, all Workshop functionality (including both Workshop Studio and Workshop for WebLogic) will be unavailable.
Platforms: Workshop for Weblogic 10.2 and Workshop Studio 10.2.
Workaround: Uninstall Workshop Studio 10.2 by performing the following:
Run uninstall, deselecting all components except Workshop Studio in the uninstall wizard. Launch the product again. The Workshop for WebLogic license will be used and Workshop for WebLogic functionality returns.
|
|
|
Workshop closes console when the server fails to start
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.
Workaround: Follow the procedure below:
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.
Platforms: WorkSpace Studio 1.1
Workaround: Launch WorkSpace Studio with -clean.
|
