bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Server > Release Notes > Resolved Problems |
Release Notes
|
The following sections describe problems that were resolved for the release of WebLogic Server 7.0 Service Pack 1:
WebLogic Server 7.0 Service Pack 1 Solutions
The following sections describe problems that were resolved for the release of WebLogic Server 7.0 Service Pack 1.
Revised RMI-IIOP example to update the out of date information for ejb cppclients. Changed the DefaultGIOPMinorVersion="1" in the server mbean to DefaultMinorVersion='1' in the iiop mbean. |
||
Fixed typo in the JMS sample example where in the Configure WebLogic Server section of the examples instructions, after step 10, -appsdir was missing from the JAR name. |
||
Completed a security provider example and posted it to BEA's online dev2dev Online for WebLogic Server at dev2dev. |
||
Fixed problem where the default URL in the PointBase Console is incorrect. The default URL is missing a colon after the server. |
||
Fixed problem where the instructions for WebLogic Server Petstore reference the incorrect directory for the Petstore EAR files. |
||
Fixed problem that caused a fatal initialization exception during Examples server start-up when the examples-dataSource-demoPool datasource is changes to oraclePool. This problem occurred when running the EJB examples. |
||
Upgraded PointBase files to fixed the problem that caused the PointBase server to hang when doing a CLOB update with multi-byte character set data in the application data. |
||
Included the WebServices examples in the WebLogic Server product distribution. |
||
Fixed problem that caused errors and exceptions in the wtc.tBridge example. Updated the javadocs to provide instructions on setting the JMS server before running the example. |
Internationalized the WebLogic Builder menus, actions, and documentation including the AppFrame and MainAppFrame menus and actions in the Console. |
Fixed the problem that caused an XAException to occur when an EJB executing an SQL statement is followed by an RMI call inside the same transaction. |
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |