bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search

Release Notes

 Previous Next Contents View as PDF  

Resolved Problems

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.

Console

Change Request Number

Description

Release Fixed

068366

Fixed the Console context path in the Console so that when this field is no longer hardcoded.

7.0 SP1

069887

Fix problem where a load.mlet file was created by the server and created a myserver directory.

7.0 SP1

076739

Fixed problem where the object class, object hash code, and object to string fields are blank when viewing the JNDI tree for a local stateless session EJB deployment.

7.0 SP1

077126

Fixed problem that user is unable to configure the weblogic.xml param ConsoleMain Attribute for servlet monitoring in the Console.

7.0 SP1

081366

Fixed problem that prevents users from deleting a Machine object that has one or more configured servers.

7.0 SP1

082942

Fixed problem that caused a null pointer exception to be thrown when the user's password was changed in the Console and then continue was clicked.

7.0 SP1

083460

Updated WebLogic Server to reflect that Netscape is supported on HP_UX.

7.0 SP1

083578

Increased the size of the Max Message Size text field on the Server Protocols tab in the Console to display all digits entered.

7.0 SP1

084114

Fixed problem on the WebApp Monitoring tab in the Console that caused an exception to be thrown when monitoring the performance of Web applications.

7.0 SP1

CORE

Change Request Number

Description

Release Fixed

055987

Implemented timeout option for HttpURLConnection.

7.0 SP1

066230

Enabled users to set the name attribute, set in the config.xml file to match the domain name. If you manually edited the config.xml file and added a Log element to the domain with a FileName attribute that was not the same as the domain name, the server created and used a domain log with the same name as the domain.

7.0 SP1

074835

Added changes to WebLogic Server to accommodate changes in java.net.HttpURLConnection.

7.0 SP1

074888

Fixed problem that caused an Error 503 during an HttpSession fail over when the primary server is being shut down in a two-server cluster.

7.0 SP1

075321

Fixed problem that Operator role could not issue START command using the weblogic.Admin command. A NoAccessRuntimeException occurred.

7.0 SP1

077919

Fixed problem in the method replaceObject() that caused WebLogic Server to change the original object and the reference to LeasedRemoteReference if the object is of type StubInfo and the reference is LocalServerRef.

7.0 SP1

083485

Fixed problem that occurred when using t3 as the default protocol. This problem caused the t3 client to hang in JavaSocketMuxer. The fix ensures that the t3 client uses the correct incoming connection instead of bootstrapping to the default connection.

7.0 SP1

Deploy

Change Request Number

Description

Release Fixed

070498

Users can no longer delete application mbeans if they have not deleted the actual application.

7.0 SP1

080914

Enabled use of resource-descriptor with application scoped connection pools. This allows WebLogic Server to check if a JNDI name is defined in the resource-ref-name element, perform a lookup at the local level and if the DataSource exists, bind it into the comp/env.

7.0 SP1

081311

Fixed problem that caused a check on the DTD for the web-app.xml file to produced a SAXParseException of informational severity level instead of the appropriate warning severity level.

7.0 SP1

082195

Enabled weblogic.Deployer to allow an Administrator to successfully deploy all available member of a cluster, even if the cluster has some members that are not available.

7.0 SP1

082263

Fixed problem that caused weblogic.Deploy not to update a web app WAR file deployed from a Windows 2000 system to a server running on a Solaris system.

7.0 SP1

083179

Improved the WebLogic Server exception message that displays when the resource reference deployment descriptors in the web.xml and weblogic.xml of a web application have out of sync resource-ref and resource-description elements. Previously, an exception message displayed that did not contain the actual resource reference name that caused the problem.

7.0 SP1

EJB

Change Request Number

Description

Release Fixed

050001

Provided EJB-QL support for multi-byte characters that fixed problem with the EJB-QL where clause `=' and `IN' failed to handle fixed Kanji stings.

7.0, Platform Edition

057074

Fixed problem where the value for beans-in-use-number was greater than the beans-in-cache-number. This information displays in the monitoring section of the Console.

7.0 SP1

060965

Fixed the parser to allow spaces around the `=' symbol in an EJB QL query.

7.0 SP1

073297

Fixed problem that caused message-drivewn beans that attempted to reconnect to their destinations on failure. This causes the creation of a log message for every reconnection failure. Reconnection was tried every 10 seconds and this was causing the log file to be filled.

7.0 SP1

074781

Fixed problem that caused automatic table generation not to work with the PointBase database.

7.0 SP1

075219

Fixed problem that roles and policies were not enforced on EJBs.

7.0 SP1

075273

Fixed problem where the DDInit for a WAR file did not print or create a weblogic.xml file. It did print the web.xml file, but did not create it in the WEB-INF directory.

7.0 SP1

077104

Fixed problem that EJB 2.0 container-managed relationship (cmr) one to many relationships between read-only entity beans with Required transaction attribute generates IllegalStateException when trying to access the Collection.

7.0 SP1

077986

Fixed problem where wildcard "*" does not work in the EJB 2.0 ejb.jar.xml file for <unchecked/> of method-permission.

7.0 SP1

078297

Fixed problem that container-managed persistence (CMP) caching does not work as expected when setting the concurrency strategy to optimistic. Instead of updating what is in the cache, it seems that ejbLoad gets called on the second transaction and this means that the database is updated with the external change.

7.0 SP1

078350

Fixed problem where the query generation caused the CTS failure because the generated query was incorrect.

7.0 SP1

079086

Fixed the problem that caused a message-driven bean that uses an LDAP server for the JNDI information, to fail to deploy with a javax.management.MalformedObjectNameException.

7.0 SP1

079471

Fixed problem where SelectDistinct is not working with dynamic queries. Dynamic queries that have distinct in their EJB QL select clauses are returning duplicates. With Select Distinct, the EJB Container is suppose to weed out duplicate results.

7.0 SP1

080115

Fixed problem that produced a null value when the user printed the CMP Clob value.

7.0 SP1

080783

Ensured that the EJB marks and handles the Global Security Roles. When a role-name element is ti be assigned globally named principals then the global-role element should be defined in a security-role-assignment stanza in the weblogic700-ejb-jar.xml file.

7.0 SP1

081807

Fixed problem that occurred because ejb.Deployer hard wired the replicatebindings to true on the context object before binding home to the JNDI tree. Therefore, when WebLogic Server tried to send announcements to other nodes in the cluster a NameAlreadyBoundExcedption occurred.

7.0 SP1

081817

Provided a bean-level option to set the dispatchPolicy in the weblogic-ejb-jar.xml file.

7.0 SP1

082406

Fixed problem where when using Weblogic Serve with a Sybase database and a Sybase XA Driver the driver throws an implicit conversion error when the CMP field of an EJB is binary.

7.0 SP1

082451

Fixed problem where third party JAR files for message-driven beans are not properly loaded and a ClassNotFoundException occurred in situations where the JMS provider is not WebLogic specific.

7.0 SP1

082749

A new tag has been added to the weblogic-rdbms20-persistence-700.dtd in WLS 7.0 SP1, called use-select-for-update that enforces pessimistic concurrency on a per bean basis.The description of the flag is::

<!--

Specifying "true" for this flag will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database. This is different from the transaction isolation level of TRANSACTION_READ_COMMITTED_FOR_UPDATE in that this is set at the bean level as opposed to at the transaction level.

Valid values are "true", "True", "false" or "False"

Default: False

Used in: weblogic-rdbms-bean Since: WLS 7.0 SP1

-->

<!ELEMENT use-select-for-update (#PCDATA)>

7.0 SP1

Examples

Change Request Number

Description

Released Fixed

073117

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.

7.0 SP1

074373

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.

7.0 SP1

075073

Completed a security provider example and posted it to BEA's online dev2dev Online for WebLogic Server at dev2dev.

7.0 SP1

077817

Fixed problem where the default URL in the PointBase Console is incorrect. The default URL is missing a colon after the server.

7.0 SP1

078175

Fixed problem where the instructions for WebLogic Server Petstore reference the incorrect directory for the Petstore EAR files.

7.0 SP1

079455

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.

7.0 SP1

080073

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.

7.0 SP1

080501

Included the WebServices examples in the WebLogic Server product distribution.

7.0 SP1

082913

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.

7.0 SP1

Internationalization

Change Request Number

Description

Release

Fixed

063067

Internationalized the WebLogic Builder menus, actions, and documentation including the AppFrame and MainAppFrame menus and actions in the Console.

7.0 SP1

JDBC

Change Request Number

Description

Release

Fixed

082964

Provided the following WebLogic Server support for Oracle 9.2:

  • WLS jDriver support for Oracle 9.0.1
  • WLS jDriver support for Oracle 9.2 (already certified)
  • Existing Oracle provided thin driver bundled in WLS for Oracle 9.0.1
  • New Oracle provided thin driver bundled in WLS for Oracle 9.2 (Pending Oracle approval)

7.0 SP1

JMS

Change Request Number

Description

Release Fixed

063743

Fixed problem where message-driven beans of type Object are not acknowledging the object messages.

7.0 SP1

075514

Fixed problem on the WebLogic Messaging Bridge tab in the Console where the IdleTimeMaximum attribute label was shown "In Milliseconds;" it should have been shown in the correct measurement of idle time as "In Seconds".

7.0 SP1

077814

Fixed problem that caused a memory leak with weblogic.jms.backend.BEMessageReference when the client runs.

7.0 SP1

079855

Provided documentation to tell users that they cannot configure their own General Bridge adaptor. The instructions say that users with non-JMS messaging products need to obtain a third-party OEM vendor or need to contact BEA Professional Services to obtain access to non-JMS source or target destinations.

7.0 SP1

080078

Fixed the problem that allowed a JMS message's redelivery limit to remain unchanged after the message failed to be delivered to the correct destination.

7.0 SP1

JTA

Change Request Number

Description

Release Fixed

059175

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.

7.0 SP1

JTS

Change Request Number

Description

Release Fixed

064301

Fixed the problem that caused a distributed in-doubt transaction to be created when an application was abruptly killed. However, when the application was restarted, the distributed in-doubt transaction continued to exist and had to be manually resolved by the DBA.

7.0 SP1

Miscellaneous

Change Request Number

Description

Release Fixed

067750

Added a check to determine if application scoped pool names and global pool names duplicate each other.

7.0 SP1

068158

Updated the SNMP MIB Reference documentation to provide description of new WebLogic Server SNMP mbeans and attributes.

7.0 SP1

067987

Marked all references to File T3 as deprecated in the WebLogic Server documentation.

7.0 SP1

072268

Provided support for complexType inheritance from simple types.

7.0 SP1

072949

Checks for an exception message to interpret if a failure is genuine or a false negative from the native layer. The problem is that the Node Manager tries to do a forceShutdown command on a Managed Server that can result in a error being reported back to the user and a misleading message being written to the Node Manager log.

7.0 SP1

073988

Fixed the problem that caused the Node Manager not to resume monitoring managed servers that were hosting migratable services.

7.0 SP1

074006

Fixed problem that caused some mbeans attributes to have the same oid.

7.0 SP1

075521

Fixed search problem in the online help by deleting a duplicate file that caused the wrong file to display during some searches.

7.0 SP1

075538

Provided documentation that covers the specific Server states that the Node Manager defines as follows

Node Manager defines its own, internal Managed Server states for use when restarting a server. You may observe these states when working with Node Manager in a domain:

  • FAILED_RESTARTING—Indicates that Node Manager is currently restarting a failed Managed Server.

  • ACTIVATE_LATER—Indicates that MaxRestart restart attempts have been made in current RestartInterval, and Node Manager will attempt additional restarts in the next RestartInterval.

  • FAILED_NOT_RESTARTABLE—Indicates that the server is Failed, but Node Manager cannot restart it because the server's AutoRestart or AutoKillIfFailed attribute is set to False.

FAILED_MIGRATABLE—Indicates that the server is Failed, but Node Manager cannot restart it because the server's HostsMigratableServices attribute is set to True.

7.0 SP1

078782

Fixed problem where the Connector descriptor code did not obey the encoding for the weblogic-ra.xml file. Instead, it was reading the data in the default encoding for the JMV. Now, the encoding specification in the XML header is handled appropriately for deployment descriptor files and RAR files.

7.0 SP1

079462

Ensured that details in application-scoped pools is handled in the weblogic-application.xml file. This fix ensures that if local properties are absent that global properties are used. Otherwise, if driver, url, and connection properties are not present in the jdbc-connection-pool stanza of the weblogic-application.xml, the definitions in JDBCDataSourceFactopry are not necessarily used.

7.0 SP1

079831

Fixed problem that the 7.0 message catalog DTD did not include loggable attributes as the DTD was not updated to accommodate this feature. This was not a problem for the message catalog parser, but was an issue for the generic XML editors.

7.0 SP1

080016

Fixed problem that occurred when deploying an application while starting a WebLogic Administration Server, if the application is targeted to a virtual host, which is targeted to a Managed Server and an Administration Server.

7.0 SP1

080249

Fixed problem that caused the WebLogic Server 7.0 Administration Server, when set as an NT Service, to be unable to talk to the Node Manager.

7.0 SP1

080257

Fixed problem that caused a NegativeArraySizeException to occur when the first line of an HTTP request was not formatted properly.

7.0 SP1

081377

Fixed problem that occurred when loading classes via the context class loader during deployment.

7.0 SP1

081625

Included PointBase 4.3 in WebLogic Server.

7.0 SP1

082081

Fixed problem that caused the weblogic.Admin SERVERLOG command line utility to fail when t3 is used.


082093

Fixed problem with WebLogic Server and the NSAPI plugin that caused several calls to be made to the application server for each call arriving in proxy.

7.0 SP1

082096

Fixed problem that occurred when Idempotent is set to OFF that caused the IIS proxy plugin to attempt one retry for all POST requests after r

7.0 SP1

082939

Fixed problem with ISAPI plug-ins so that it works with different session ID formats.

7.0 SP1

083151

Fixed problem with weblogic.Builder that caused the command line ddinit for EAR files not to work.

7.0 SP1

083174

Fixed problem that caused the latest IIS Plugin not to work when adding new values to the session. For example with the IIS, the method KeepAliveEnabled=true does not failover properly.

7.0 SP1

083643

Improved performance problem with the NSAPI Plugin when trying to read post data. Problems occurred with distinguishing between \0 and 0 in the post data.

7.0 SP1

RMI/RMI-IIOP

Change Request Number

Description

Release Fixed

073691

Implemented tracing feature for RMI-IIOP.

7.0 SP1

074790

Fixed the problem that caused AccessControlExceptions when using RMI-IIOP inside Applets.

7.0 SP1

076974

Fixed problem where weblogic.rmi.ReplyOnError.execute fails when there is no request.

7.0 SP1

079387

Fixed problem where subcontext is broken in RMI-IIOP. Looking up a subcontext in JNDI causes the root context to display instead.

7.0 SP1

079439

Fixed problem where strings passed via Any's are encoded incorrectly. This problem occurs when you pass a String to a remote function that has a declared type of Object, Serializable or Externalizable.

7.0 SP1

079454

Fixed problem where the interop listBindings is completely non-functional.

7.0 SP1

079645

CORBA protocol exceptions such as OBJECT_NOT_EXIST are being mapped erroneously to RMI-IIOP java.rmi.MarshalException.

7.0 SP1

079648

Fixed problem that caused no IOR to be defined for TransactionFactory which caused users to be unable to get the OTS TransactionFactory from a client.

7.0 SP1

080239

Fixed problem that caused the IDL Package names to not be mangled properly.

7.0 SP1

080259

Fix problem that caused the component type for boxed RMI sequences to generate wrong sequence of valuetypes.

7.0 SP1

080306

Fixed problem where under some circumstances, valuetype exceptions were missing their inherited base classes.

7.0 SP1

081923

Fixed RMI/IIOP stub code generation problem that caused an IncompatibleClassChangeError. The generated stubs were not handling the ensuing RemarshalException correctly.

7.0 SP1

083018

Fixed problem where WebLogic Server cannot unmarshal Any's method types using indirect typecodes.

7.0 SP1

Security

Change Request Number

Description

Release Fixed

069969

Created a new algorithm to allow WebLogic Server to load trusted CAs. Previously, if users did not configure trusted CAs, WebLogic Server loaded a default trusted CAs from the JDK cacerts file.

7.0 SP1

070307

Fixed the server failure problem caused when the user starts a server that is configured for two-way SSL.

7.0 SP1

071894

The default keystone now logs a informational message if it has a private key or root CA keystore configured, but the file does not exist or is not present in the specified location.

7.0 SP1

072902

Modified the algorithm for loading trusted certificates.

7.0 SP1

073082

Fixed the problem caused when using CertGen to generate certificates on Solaris adds the domain name extension on the common name field in the certificate. Once the HostNameVerification is enabled on Solaris, it fails due to a mismatch in the hostname.

7.0 SP1

073665

Fixed problem that caused a ProtocolException when tunneling https through the iPlanet Proxy Server.

7.0 SP1

073941

Enabled the default keystore to log error messages.

7.0 SP1

074102

Fixed problem that caused the Administration Console to no longer uses a default cookie name.If you tried to load the console through another Web application you were not be able to access it with a single sign-on unless you configured your Web Application to have the same cookie as the console: ADMINCONSOLESESSION. Consequently, this caused a cookie name conflict between the console and the WebApp's single signon (SSO) mechanism.

7.0 SP1

074612

Fixed problem that caused SSL not to start when WebLogic Server is started because the cacert file specified in the jdk directory is missing and the location of the trusted cacert file is specified on the command line.

7.0 SP1

075172

Fixed problem caused when SSL handshake fails to find the CA certificate in the configured root KeyStore.

7.0 SP1

075901

Fixed problem of how the Console handled lists when displaying users while the embedded LDAP was loaded with 50000 users.

7.0 SP1

076409

Fixed the problem that caused an NTSocket Muxer crash. This problem surfaced when using a Perl script that created connections to the server. The script caused the web server to crash.

7.0 SP1

078249

Fixed problem that caused nested groups in LDAP V2 Realm to no longer work.

7.0 SP1

078797

Fixed problem where when the EJB Container checks for Method Permissions on all methods (except those that are not excluded or unchecked), user is denied execution permission on a method on which no Security Restrictions are set.

7.0 SP1

078887

Provided a way to disable anonymous login to the embedded LDAP server so that anonymous login is prohibited.

7.0 SP1

080072

Fixed problem that caused the 7.0 version of WebLogic Server with a 7.0 SSL configuration that included the private key keystore, alias, and password specified in the config.xml file to default to the 6.x SSL configuration.

7.0 SP1

080490

Fixed problem where the DefaultKeyStore provider doesn't support non JKS JDK Keystores.

7.0 SP1

080508

Updated WebResource to enable support for fine-grain servlet security.

7.0 SP1

083125

Fixed problem that caused the weblogic.security.service.URLResource class to behave differently on Windows than it did on other platforms. On Windows, this class converted the contextPath and URI to lower case. This happened because the contextPath and URI were case insensitive in Windows.

To change the default behavior , you had to set one of the following flags:

  • -Dweblogic.security.URLResourceCaseMapping=on
  • -Dweblogic.security.URLResourceCaseMapping=off
  • -Dweblogic.security.URLResourceCaseMapping=os

If you set the flag to on, the contextPath and URI always mapped to lower case. If you set the flag to off, the contextPath and URI never map to lower case. If you set the flag to os, the contextPath and URI mapped to lower case on Windows.

You would only have needed to set this flag when you were running a domain on a combination of Windows and non-Windows machines. In this case, setting the flag to on corrected the problem across platforms, although it made non-Windows systems case insensitive.

7.0 SP1

Servlets and JSPs

Change Request Number

Description

Release Fixed

042655

Fixed error in the time format in the extended log format of the access.log file.Time now displays in GMT.

7.0 SP1

074096

Fixed problem that caused there to be no mbean access in the servlet's <init> method as it is executed as an anonymous user. Two new elements were added to the weblogic.xml deployment descriptor file to be used instead of run-as identify.

7.0 SP1

074843

Upgraded WebLogic Server so that JSP request time attributes used to output an empty string when the expression was null now output the string null.

In previous versions of WebLogic Server, JSP request time attributes (<%= expr %>) output an empty string when the expression was null. Now it outputs the string "null". The JSP specification mandates that the expressions default must be "null."

However, we have introduced a new flag in weblogic.xml called printNulls which is true by default meaning that "null" will be the default output. Setting the flag to false makes sure that expressions with "null" results are printed as "", which was the earlier behavior.

Configuring the printNulls tag in weblogic.xml:

<weblogic-web-app>
<jsp-param>
<param-name>printNulls</param-name>
<param-value>false</param-value>
</jsp-param>
</weblogic-web-app>

Also, you can compile from weblogic.jspc with:

-noPrintNulls

This will also show "null" in jsp expressions as "" (an empty string).

7.0 SP1

075805

Implemented a way to set the current Subject of an HttpSession by adding a new runAs method to weblogic.servlet.security.ServletAuthentication.

7.0 SP1

076330

Fixed problem in which the server was unable to load a Web Application class from a JAR file which had a period in its name.

7.0 SP1

077823

Updated the plug-in information in the Administration Guide and the using Plug-ins Guide to reflect updated plug-in parameter information.

7.0 SP1

077944

Fixed problem with JSP tag where JSP2XmlOutputter calls dequote() incorrectly which causes parse errors.

7.0 SP1

078725

Fixed problem where the HttpClusterServlet decoded the chunk transfer encoded response.

7.0 SP1

079924

Provided the ability to define dispatch policy at the web-app level by adding new element, wl-dispatch-policy, to the weblogic.xml file.

7.0 SP1

080445

Fixed problem that caused WebLogic Server not to recognize WeblogicPluginEnabled=true in the server section of the config.xml file. This caused the incorrect client machine address to be passed in the header.

7.0 SP1

080608

Fixed problem that caused weblogic.servlet.security.ServletAuthentication weak string to always return FAILED_AUTHENTICATION.

7.0 SP1

080613

Updated WebLogic Server to allow special characters in quoted string values; previously commas in a cookie's quoted value did not work.

7.0 SP1

080772

Fixed problem that caused UnsupportedEncodingExecption if user had extra quotes around the charset.

7.0 SP1

081484

Fixed problem where session attributes were lost when using HttpSessionListener with the PersistentStoreType specified as replicated.

7.0 SP1

081521

Fixed problem that caused CGI scripts, called from a JSP, not to work in a WAR or EAR file.

7.0 SP1

082156

Fixed problem where the isRequestedSessionIdValid() always returns the value, true which means that the request session ID is valid, even if you changed the session ID in the URL.

7.0 SP1

082310

Fixed problem that prevented users from deleting or overwriting JSPs, with a "page contentType" directive, in exploded WAR files. The solution was to ensure that the inputstream in the JSP Parser was closed after it was used.

7.0 SP1

082461

Fixed problem that caused FileServlet not to work. Ensured that WebLogic Server does not prepend the SERVLET_PATH to the PATH_INFO used to construct the desired filename if a docHome parameter is specified.

7.0 SP1

082636

Fixed problem that caused the empty auth constraint does not restrict access in fullSecurityDelegation mode.

7.0 SP1

083200

Fixed problem that prevented WebLogic Server from filtering nonProxyHosts correctly. WebLogic Server now honors both http.nonProxyHosts and nonProxyHosts.

7.0 SP1

083517

Fixed problem that caused HttpClusterServlet not to proxy requests to SSL even when the SecureProxy is enabled.

7.0 SP1

083654

Fixed performance problems by improving the of performance of Servlets and JSPs that use multibyte charsets as content type.

7.0 SP1

Tools

Change Request Number

Description

Release Fixed

074535

Fixed problem in weblogic.Builder that caused the DDinit not to recognize recursive relations.

7.0 SP1

074535

Fixed problem in weblogic.Builder that caused the DDinit not to recognize recursive relations.

7.0 SP1

074570

Fixed problem in weblogic.Builder that caused the DDinit to mistake cmr fields for cmp fields.

7.0 SP1

074620

Fixed problem in weblogic.Builder that caused the CMP field type to be enabled when the Bi-directional field on the Wizard is checked even though the relationship is one-to-one.

7.0 SP1

074629

Fixed problem in weblogic.Builder that caused an Illegal DatasSource dialog box to display when user pressed the cancel button on the Connect to Server dialog box for any browse action.

7.0 SP1

074689

Fixed problem in weblogic.Builder that caused checking the create duplicate environments field to generate incomplete XML.

7.0 SP1

074764

Added the set cache-type field, missing from the tuning panel for stateful session beans to the Session Advanced panel.

7.0 SP1

074773

Fixed problem that prevented the XMLElement generator from generating XML code for stateful session EJBs with allow-concurrent-calls specified.

7.0 SP1

074995

Fixed problem in weblogic.Builder that occurred when user deleted a relations, the XML was removed but the module was not marked as modified. When the module was closed, user was not prompted to save the change.

7.0 SP1

075034

Fixed problem in weblogic.Builder where on the EJB|Tuning|Cluster panel, adding a new Idempotent method caused a java.lang. IllegalArgumentException.

7.0 SP1

075521

Fixed problem in weblogic.Builder online help where several searches on various topics displayed an incorrect page.

7.0 SP1

075537

Fixed the problem in weblogic.Deployer where servers added to a cluster in a running domain were not deployed on the new clusters in the server.

If you added a server to a cluster and restarted the managed servers, Web applications previously targeted and deployed to the cluster were not automatically deployed on the added server.

7.0 SP1

075672

In weblogic.Builder, removed the Methods Are Idempotent checkbox because methods-are idempotent is deprecated. Developed a way to add idempotent methods for stateless session EJBs. Idempotent methods can now be specified on the Cluster panel.

7.0 SP1

075937

Fixed problem where weblogic.Builder wrote illegal values for the EJB deployment descriptor, max-cache-size.

7.0 SP1

077171

Fixed problem in weblogic.Builder where the DDinit sets the wrong version for the container-managed persistent (cmp) descriptor.

7.0 SP1

078747

Fixed problem where weblogic.Builder cannot open the ejb11_container_managed.jar file.

7.0 SP1

WebServices

Change Request Number

Description

Release Fixed

069027

Fixed problem that prevented dynamic from working with the wsdl client to invoke WebServices with complex datatypes.

7.0, Platform Edition

073539

Fixed broken links on the WebServices Home page where an extra "/" was accidently added.

7.0 SP1

075634

Fixed problem where the generated stub fails to handle the doc/lit with echo"Struct.

7.0 SP1

076677

Fixed problem that prevented dynamic from being used with the wsdl client to invoke WebServices with complex datatypes.

7.0, Platform Edition

077849

Fixed problem that caused multi-byte strings to be corrupted by WebServices when using an English environment.

7.0 SP1

078313

Fixed connection problem that occur intermittently when the stub client interop to.net service fails.

7.0 SP1

078442

Fixed problem caused by accessing the home page through HTTPS for a Web service generated both with and without the protocol=https in services generation causes an authentication login dialog to display.

7.0 SP1

078804

Fixed the problem where the Web Services Stateless Session example uses the not public API import weblogic.ejb.GenericSessionBean.

7.0 SP1

079620

SOAP messages are now compliant with RFC2376.

7.0 SP1

079984

Disabled the feature that checked for the presences of webservices.jar file in the WebServices examples.

7.0 SP1

080154

Fixed problem that caused an authentication screen to pop up when using HTTP protocol and an array of int or string in the method signature.

7.0, Platform Edition

080264

Fixed problem that caused the SOAP response not to have the required utf-8 contentType in the HTTP header.

7.0 SP1

080961

Obtained a fix for a bug in the XML parserXerces 1.3.1, in the org.xml.sax.helpers.AttributesImpl.removeAttribute() call.

7.0 SP1

 

Back to Top Previous Next