Notes and Problems
The following sections describe levels of support, notes, and general problems in this release:
WebLogic Server 7.x Release Information
On June 28, 2002, BEA released WebLogic Server 7.0 Platform Edition. If you downloaded WebLogic Server before that date you have the WebLogic Server 7.0 version. WebLogic Server 7.0 Platform Edition is identical to WebLogic Server 7.0 with the following two major exceptions:
- WebLogic Workshop, a powerful integrated development environment, was added to WebLogic Server 7.0 Platform Edition.
- Also, in the Platform Edition , WebLogic Server no longer requires the download of a separate JAR file to enable Web Services.
These release notes are for WebLogic Server 7.0 Service Pack 1 (SP1). WebLogic Server 7.0 SP1 incorporates the features of both WebLogic 7.0 and WebLogic Server 7.0 Platform Edition.
Platform Support
See the Platforms Support Page for the most accurate and current information regarding platform support.
Standards Support
Standard
|
Version
|
HTTP
|
1.1
|
J2EE Connector Architecture
|
1.0
|
J2EE EJB
|
2.0
|
J2EE JDBC
|
2.0
|
J2EE JNDI
|
1.2
|
J2EE JSP
|
1.2
|
J2EE JTA
|
1.0.1a
|
J2EE JMS
|
1.0.2b
|
J2EE RMI
|
1.0
|
RMI/IIOP
|
1.0
|
J2EE Servlet
|
2.3
|
LDAP
|
2
|
SSL
|
3
|
X.509
|
3
|
WebLogic Server Changes Between Versions 7.0 and 7.0 SP1
The following changes in this release differ from WebLogic SErver 7.0:
Updating WebLogic Server 7.0 GA to 7.0 Service Pack 1
If you installed the stand-alone WebLogic Server 7.0 GA release (version 7.0.0.0) and did not upgrade to the version available with WebLogic Platform 7.0 (WebLogic Server version 7.0.0.1), you cannot use Smart Update to install Service Pack 1 (WebLogic Server 7.0.1.0). Instead you can use a package upgrade installer that you can download from the BEA Customer Support Web site at http://support.bea.com. For instructions, see Installing Service Packs and Rolling Patches with a Downloadable Installer" on page 6-7.
To see which version of WebLogic Server you have installed, open BEA_HOME\logs\log.txt (BEA_HOME/logs/log.txt on UNIX) in a text editor and look at the last entry in the log file. Each line in the log file represents an installation event for the current BEA home—an installation or an uninstallation. If the log entry indicates that the version installed is WebLogic Platform 7.0 SP0 or earlier, you cannot use Smart Update. If the log entry indicates that the version installed is WebLogic Platform 7.0.0.1 or later, you can use Smart Update to install Service Pack 1 (7.0.1.0).
Note: WebLogic Server and WebLogic Platform use the same installation framework. Therefore, installation log entries use the term WebLogic Platform to indicate an installation of either WebLogic Server or WebLogic Platform.
Migrating Domains Created Using the Configuration Wizard
The Configuration Wizard (introduced in WebLogic Platform 7.0) allows you to create new domains quickly and easily. If you created domains using the Configuration Wizard in WebLogic Platform 7.0, you need to migrate those domains for use with WebLogic Platform 7.0 Service Pack 1.
For most domains, migration is a three-step process:
- Upgrade the product JAR files in the domain directory. A migration script is provided for this purpose.
Note: You can also revert a domain to its pre-migration state.
- Update the domain to support Service Pack 1 changes. Depending on the domain template used to generate the domain, you may need to add or modify existing scripts or files.
- If you installed WebLogic Platform 7.0 Service Pack 1 into a new directory, separate from the WebLogic Platform 7.0 installation, update the domain startup scripts and configuration files to reference the new BEA_HOME directory location.
Note: If you upgraded your existing WebLogic Platform 7.0 installation, you can skip this step.
These steps are explained in detail in the following sections. You will need to repeat this process for each domain that you want to migrate.
Note: This section decribes how to migrate domains specific to WebLogic Server. For information about migrating other WebLogic Platform domains, see "Migrating Domains Created Using the Configuration Wizard" in the WebLogic Platform 7.0 Service Pack 1 Release Notes at the following URL:
http://e-docs.bea.com/platform/docs70/relnotes/relnotes.html#migration
Step 1: Upgrade Product JAR Files
To upgrade product JAR files for a domain that you generated using the Configuration Wizard to Service Pack 1, navigate to the BEA_HOME\weblogic700\server\bin directory and execute one of the following commands:
Windows: migrate.cmd domain mode
UNIX: migrate.sh domain mode
Note: You will be prompted to press any key to start processing.
The following table defines the command-line arguments.
Argument
|
Description
|
domain
|
Full pathname of the domain directory.
|
mode
|
Migration mode. The mode can be set to one of the following values:
upgrade: Upgrade the product JAR files in the domain directory, as required. The original product JAR files are saved as *.jar.orig. If the timestamp of an existing product JAR file is more recent than the timestamp on the corresponding SP1 installation product JAR file, the file is skipped. This is the default mode.
|
For example, the following command upgrades a domain called mydomain located in the default user projects directory (BEA_HOME\user_projects):
Windows: migrate.cmd c:\bea\user_projects\mydomain upgrade
UNIX: migrate.sh c:/bea/user_projects/mydomain upgrade
The following command reverts the changes made to mydomain during the migration:
Windows: migrate.cmd c:\bea\user_projects\mydomain revert
UNIX: migrate.sh c:/bea/user_projects/mydomain revert
Step 2: Update Domain to Support Service Pack 1 Changes
Depending on the domain template used to generate the domain, you may need to add or modify existing scripts or files to support WebLogic Platform 7.0 Service Pack 1 changes. Refer to the appropriate section below, based on the domain template used to generate the domain, for additional migration steps:
Note: Before adding or modifying any files, as described in the following sections, it is recommended that you backup the original files.
WebLogic Workshop Domain
For a domain that is based on the WebLogic Workshop template, perform the following steps:
- Modify the startWebLogic.cmd (Windows) or startWebLogic.sh (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH. The files for both commands are located in the following directory, by default:
BEA_HOME\user_projects\domain
The following sample excerpt from the startWebLogic.cmd script (Windows) shows the required updates in bold:
Before:
set PB_CLASSPATH=
%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF172.jar;
%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF172.jar
After:
set PB_CLASSPATH=.\;
%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF183.jar;
%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF183.jar
- Copy the following files from the BEA_HOME\weblogic700\samples\workshop directory to the BEA_HOME\user_projects\domain directory of your WebLogic Workshop domain. Be careful not to overwrite any files that may have been created using one of these filenames.
setWorkshopEnv.cmd
setWorkshopEnv.sh
startPointBaseConsole.cmd
startPointBaseConsole.sh
URLs.dat
WLS Domain
For a domain that is based on the WLS Domain template, you do not need to add or modify existing scripts or files.
WLS Examples
For a domain that is based on the WLS Examples domain template, modify the CLASSPATH definition in the startExamplesServer.cmd (Windows) or startExamplesServer.sh (UNIX) command to:
- Reflect the appropriate PointBase version (183 versus 172) in the JAR filenames.
- Add the BEA_HOME\server\lib\webservices.jar file.
The files for both commands are located in the following directory, by default:
BEA_HOME\user_projects\domain
The following sample excerpt from the startExamplesServer.cmd script (Windows) shows the required updates in bold:
Before:
set CLASSPATH=c:\bea\jdk131_03\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF172.jar;%POINTBASE_HOME%\lib\pbclient42ECF172.jar;%CLIENT_CLASSES%;%SERVER_CLASSES%;%COMMON_CLASSES%;%CLIENT_CLASSES%\utils_common.jar
After:
set CLASSPATH=c:\bea\jdk131_03\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF183.jar;%POINTBASE_HOME%\lib\pbclient42ECF183.jar;%CLIENT_CLASSES%;%SERVER_CLASSES%;%COMMON_CLASSES%;%CLIENT_CLASSES%\utils_common.jar;%WL_HOME%\server\lib\webservices.jar
WLS Petstore
For a domain that is based on the WLS Petstore domain template, modify the startPetStore.cmd (Windows) or startPetStore.sh (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH.
The files for both commands are located in the following directory, by default:
BEA_HOME\user_projects\domain
The following sample excerpt from the startPetStore.cmd script (Windows) shows the required updates in bold:
Before:
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF172.jar;%POINTBASE_HOME%\lib\pbclient42ECF172.jar;%SERVER_CLASSES%;%COMMON_CLASSES%
After:
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF183.jar;%POINTBASE_HOME%\lib\pbclient42ECF183.jar;%SERVER_CLASSES%;%COMMON_CLASSES%
Step 3: Update Startup Scripts and Configuration Files to Reference New BEA_HOME Directory Location (Non-Upgrades Only)
Note: This step is only required if you installed WebLogic Platform 7.0 Service Pack 1 into a new directory that is separate from the WebLogic Platform 7.0 installation. If you upgraded your existing WebLogic Platform 7.0 installation, you can skip this step.
The domain startup scripts (such as, startWebLogic) and configuration files (such as config.xml) define the full pathnames to files within the BEA_HOME directory. You need to search for and update these full pathnames to reference the new BEA_HOME directory location. In addition, you must update any custom scripts, such as build scripts, that define full pathnames to the files within the BEA_HOME directory to reflect the new BEA_HOME location.
Note: Many startup scripts set environment variables in your current shell, including variables that reference your BEA_HOME directory. After updating the BEA_HOME references in script files, you should open a new shell to ensure that the latest environment settings are used.
Deprecated Features
The following feature is deprecated in WebLogic Server 7.0 SP1.
The WebLogic jDriver for Microsoft SQL Server is deprecated and will be removed from a future release of WEbLogic SErver. BEA recommends that you use the JDBC driver available from Mocrosoft to connect to a Microsoft SQL Server database. See "Installing and Using the SQL Server 2000 Driver for JDBC from Microsoft" in Programming WebLogic JDBC.
Java Development Kit
A JDK provides a Java runtime environment (the Java Virtual Machine or JVM) and tools for compiling and debugging your Java applications. Your installation of WebLogic Server 7.0 includes the 1.3.1_02 JDK from Sun Microsystems.
WebLogic Javadoc
BEA uses the Javadoc tool to generate documentation for externally supported APIs. Javadoc is a tool from Sun used to document API of classes that have been declared within the public scope. A class declared within the public scope is visible to other classes outside of its own package. BEA uses a custom version of Javadoc that has been enhanced to distinguish between externally supported public classes and public classes that are intended for internal use only. However, Javadoc may generate indirect references to internal classes or methods in usage pages, inheritance trees, or in other supplemental lists. Such indirect references do not imply support for internal methods or classes. BEA supports only those APIs that are fully documented on the main Javadoc pages for the classes to which they belong. In other words, when you select a package in the upper left-hand frame, all externally supported classes within that package will appear in the lower left-hand frame.
HTML Pages and Netscape
If you already have a Netscape browser running when you start WebLogic Server, some HTML pages will not display. For example, if you select the About WebLogic Server page from the Start menu, and you have Netscape running and do not have Microsoft Internet Explorer, the screen may flash but the page will not display.
Clusters, DNS, and Multihoming on NT
Be aware of naming issues when using multihoming features on Windows NT in a cluster. For example, naming conflicts may occur if a cluster is running on a multihomed Windows NT machine and one of the servers in the cluster is bound to the same DNS name as the machine name. Attempts to contact that server using the DNS name in a URL may result in Windows NT converting that DNS name to any of the IP addresses of the multihomed Windows NT machine. In this case, the request may go to the wrong address. Avoid having DNS names that match your machine name.
Known Issues
The following sections describe known problems with this software release.
Administration Console Known Issues
Change Request Number
|
Description
|
066112
|
Deployment procedures using the Administration Console have changed since the 6.x release. For more information, see WebLogic Server Application Deployment.
|
069828
|
You can no londer edit the Web Services deployment descriptor using the Administration Console.
|
069927
|
Selecting Server --> Monitoring --> Process Output and selecting any of the view options does not display the output. If you select the "View Node Manager Output" while Node Manager is running, Node Manager will crash.
|
072844
|
Sometimes the Navigation Tree does not display when you use Netscape 4.7 to access the Administration Console.
|
073164
|
You cannot use the Administration Console to edit a domain other than the current domain of the Administration Server.
|
074296
|
The Administration Console allows you to create multiple WebLogic Tuxedo Connector Server Resources. Only a single resource is valid.
|
074339
|
Explanatory text for creating configuration objects is not displayed when using Netscape 4.7 to access the console.
|
074677
|
When you upgrade a domain created under version 6.x of WebLogic Server, the user "system" no longer explicitly grants access to the Administration Console. To access the console, a user must be a member of the Administrators Group.
|
074870
|
After you create a new machine in the console and add a server to the machine, a Null Pointer Exception sometimes occurs.
|
075235
|
When you try to add non-running servers to a Migratable Target, a Null Pointer Exception is generated.
|
082694
|
Policies set in the Console for JDBC Resources are not taking effect, an inappropriate JDBC Resource is being set by the code, and there is no way to set an Administration Resource for creating a new pool.
|
Domain Configuration Wizard Known Issues
Change Request Number
|
Description
|
074675
|
When you use the WLS Examples template and select a domain that installs managed servers, the wizard does not install the startmanagedweblogic.cmd script. It only installs startexamplesserver script, which boots the administration server.
|
EJB Known Issues
Change Request Number
|
Description
|
079550
|
The ejb-local-ref element in web.xml is not documented in the WebLogic Server EJB documentation However, the feature is implemented in WebLogic SErver 7.0.
|
080920
|
A security check is not performed. Policies set in the Console for JDBC Resources are not taking effect, an inappropriate JDBC Resource is being set by the code, and there is no way to set an Administration Resource for creating a new pool.
|
Examples and Pet Store Known Issues
Change Request Number
|
Description
|
068009
|
Due to Microsoft VB Scripting Versioning, Excel 2000 or later is required to run the ZeroClient jCom example.
|
071260
|
The password/username for the examples and Pet Store has been changed since WebLogic Server 7.0 Beta. Using installadministrator/installadministrator no longer works, use weblogic/weblogic instead.
|
073395
|
Pet Store has problems when multiple clients are using the same resources. Sun is working to address this problem.
|
074004
|
In the package-summary.html file in the SAMPLES_HOME\server\src\examples\security directory, the Security Examples Summary table makes references to the audit and cert samples. These samples have been removed from the the WebLogic Server distribution because they used APIs that are being deprecated in WebLogic Server 7.0.
Also, the descriptions of the SSLClient, JAAS, and Net samples should read as follows:
SSLClient: Demonstrates how to make outbound SSL connections and two-way SSL connections from a WebLogic Server that is acting as a client to
another WebLogic Server or application server.
JAAS: Demonstrates use of the Java Authentication and Authorization Service by validating username and password, and then, if valid, executing the stateless session Trader EJB.
Net: Demonstrates writing connection filters that implement the weblogic.security.net.ConnectionFilter and ConnectionFilterRulesListener interfaces. Connection filters allow you to reject or accept client connections to the WebLogic Server environment based on the client's IP address and protocol and the local and remote port numbers.
|
075340
|
The package-summary.html and javadocs of the ejb20/blobClob example are not up to date.
|
075940
|
The package-summary.html files for the following Web services examples incorrectly state that you can download the client JAR file from the Web service Home Page; currently no link to the client JAR file exists:
The example uses the client JAR file generated with the clientgen Ant task to invoke the Web service.
|
075942
|
The package-summary.html file for the Web service example examples.webservices.complex.statelessSession incorrectly states that the URL to access the sample Web service is
http://localhost:port/trader_service/TraderService
The correct URL is
http://localhost:port/webservice/TraderService
|
076048
|
The package-summary.html files for the Web service examples incorrectly state that you can access the Web service Home page for the WebLogic Web services before telling you to start WebLogic Server.
|
080288
|
There are problems with the RMI cluster example when using ant run to execute the client. The java call to the client includes incorrect quotation marks.
|
Installation Known Issues
Change Request Number
|
Description
|
074832
|
When installing on Windows using a package installer in an environment where %TEMP% or %TMP% have not been set, the installation program will then attempt to use %USERPROFILE% as the base path for the temporary installation directory, and may fail if %USERPROFILE% has a space in it (such as C:\Documents and Settings\user).
Workaround: Explicitly specify -Djava.io.tmpdir when invoking the installation program and encapsulate its value in quotes.
|
075066
|
When installing on Windows NT 4.0, if the value for the following registry key exceeds 260 characters, an entry for WebLogic Platform is not added to the Add/Remove Software control panel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\Uninstall\BEA WebLogic Platform 7.0\UninstallString
|
JMS Known Issues
Change Request Number
|
Description
|
075438
|
A message-driven bean (MDB) that is deployed on a distributed topic, and which is targeted to a server instance that is hosting two members of the distributed topic, is also deployed on all the members of the distributed topic.
This is the expected behavior because the MDB is pinned to the member destination name. Therefore, if a JMS server contains two members, there will be two MDBs deployed, one for each member.
|
075894
|
On the Administration Console, the Delete icon is missing on the Monitor Durable Subscriber table. Therefore, there is no way to delete a durable subscriber from a topic using the console.
|
Jolt Java Client Known Issues
Change Request Number
|
Description
|
075619
|
Jolt users will need to upgrade to Jolt Java Client 8.0.1 to enable BEA Tuxedo services for the Web using BEA WebLogic Server 7.0. The Jolt Java Client 8.0.1 is available from the BEA Product Download Center. Follow the link to BEA WebLogic Server 7.0 and select the Jolt Java Client 8.0.1 from the Modules for WebLogic Server list.
|
Node Manager Known Issues
Change Request Number
|
Description
|
068088
|
When using the Administration Console, your browser may cache info from the Machine->Monitoring->Log or Unix Machine->Monitoring->Log tab. This may cause older Node Manager status messages to appear in the Administration Console pages.
|
071591
|
Node Manager detects Managed Server failures by trying to initiate an HTTP connection. If Node Manager receives a connection failure, the connection exception can be observed in Node Manager output:
<Mar 19, 2002 2:30:04 PM EST> <Warning> <net> <000900> <Could not open connection java.net.ConnectException: Connection refused: connect
|
073078
|
When the Administration Server attempts to set up an SSL connection to Node Manager, it does not automatically search for certificate files in the Administration Server's root directory. If you store SSL certificate files in the Administration Server's root directory, make sure you configure the absolute path to the certificate files using the Connections->SSL tab in the Administration Console.
|
073182
|
The SHUTDOWN and FORCE SHUTDOWN commands do not cause Node Manager to terminate its health monitoring capabilities (if configured). This can lead to Node Manager immediately restarting servers that you SHUTDOWN or FORCE SHUTDOWN.
|
074230
|
Applications deployed to WebLogic Server should never make assumptions about the current working directory. File lookups should generally take place relative to the Root Directory obtained with the ServerMBean.getRootDirectory() method (this defaults to the "." directory). For example, to perform a file lookup, use code similar to
String rootDir = ServerMBean.getRootDirectory(); //application root directory File f = new File(rootDir + File.separator + "foo.in");
rather than simply:
File f = new File("foo.in");
If an application is deployed to a server that is started using Node Manager, use the following method calls instead:
String rootDir //application root directory if ((rootDir = ServerMBean.getRootDirectory()) == null) rootDir = ServerStartMBean.getRootDirectory(); File f = new File(rootDir + File.separator + "foo.in");
The ServerStartMBean.getRootDirectory() method obtains the Root Directory value that you specified when configuring the server for startup using Node Manager. (This corresponds to the Root Directory attribute specified the Configuration->Remote Start page of the Administration Console.)
|
075142
|
The Administration Server and Node Manager may simultaneously attempt to close a TCP socket, causing the following error message to appear in the Node Manager log file:
<Apr 18, 2002 5:32:55 PM EDT> <Error> <NodeManager@localhost:5555> <OutputHandler: done2 socket close failed, reason: java.net.SocketException: Connection reset by peer.>
This problem does not affect the operation of Node Manager or the Administration Server.
|
Security Known Issues
Change Request Number
|
Description
|
051215
|
There is a problem with the password prompt on Solaris. If you ctrl-c when prompted for the password, the shell window becomes unusable because everything will be written in invisible text.
|
061030
|
WebLogic parses the grant statements in deployment descriptors for EJBs, servlets, and resource adapters but does not expand system variables.
Workaround:
Do not use variables in the <security-permission> tag in EJB, servlet, and resource adapter deployment descriptors.
|
064593
|
The following command-line arguments used to control the SSL time-to-live and cache size are ignored in WebLogic Server 7.0:
-Dweblogic.security.SSL.sessionCache.size= sessioncachesize
-Dweblogic.security.SSL.sessionCache.ttl= sessioncachetimetolive
|
064837
|
Clients using SSL now must have a valid license. Please refer to the WebLogic Server security documentation for instructions on specifying the license's location.
Also, clients using SSL must perform trust checks on the certificates of servers that connect to it by default. Please refer to the documentation on how to specify trusted CA's.
|
066782
|
Statically loading JCE providers, or using Sun's JSSE implementation can cause interaction problems with SSL and WebLogic Server. You may see these errors:
<<java.security.NoSuchAlgorithm> Exception: Algorithm XXXXXX not available>>
or
<Unable to initialize the server: Fatal initialization exception Throwable: java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError: java.lang.SecurityException: class "com.rsa.asn1.b"'s signer information does not match signer information of other classes in the same package
Using Sun's JSSE implementation can cause conflicts with WebLogic's SSL implementation, which causes these errors. Remove the jsse.jar (that Sun's JDK 1.4 provides by default) from your JDK directory to resolve the conflict.
You may also see these errors if you are using JCE providers. Loading the providers dynamically rather than statically defining them in the java.security file may resolve the problem. Here's an example of a java.security policy:
security.provider.1=sun.security.provider.Sun security.provider.2=com.sun.rsajca.Provider
The sunJCE provider is specifically unloaded by WebLogic Server if it is found to be registered statically. If you require the sunJCE provider, load it dynamically.
|
066868
|
The API documentation for the getRealm() method on the weblogic.security.acl.Security class states that this method returns the WebLogic realm. The documentation should read as follows:
If you are running WebLogic Server 7.0 in Compatibility mode, the getRealm() method returns the WebLogic realm. If you are not running in Compatibility mode, this method returns Null.
|
067087
|
The security-permission-spec attribute cannot currently be added to your weblogic-application.xml, you are limited to using this attribute within weblogic-ejb-jar.xml and weblogic.xml.
|
067621
|
The TLS_NULL_WITH_NULL_NULL cipher suite is not supported and will be ignored. A warning message will be logged indicating that the cipher suite is not being used.
|
072145
|
On Windows systems, WebLogic Server responds in the following way when you set up connection filters that deny requests made from your local machine.:
After failing with localhost (IP address 127.0.0.1), the server automatically tries IP address 127.127.127.127. As a result, you see some type of message in your "muserver.log" for one of the first rules being blocked, but then the request is allowed because of the 127.127.127.127 not matching.
For example, if you try this client on your local machine:
java weblogic.Admin -url t3://fooserver:7001 -username system -password gumby1234 PING 1 1
And you have these filtering rules only:
localhost 127.0.0.1 7001 deny t3 fooserver fooserver 7001 deny t3
Then the above client will pass because you did not include the filtering rule:
fooserver 127.127.127.127 7001 deny t3
However if you specify the following client (specifying localhost:7001 instead of foo server:7001):
java weblogic.Admin -url t3://localhost:7001 -username system -password gumby1234 PING 1 1
And you specified the following filtering rules:
localhost 127.0.0.1 7001 deny t3 fooserver fooserver 7001 deny t3
Then the client will fail to connect because it matched the first rule.
Note: Normally you would not deny HTTP requests from your own machine on your own machine. Why? Because this would prevent you from accessing the Administration Console and making changes to connection filter rules or anything else.
|
072154
|
The MyListener class is implemented in the SSLSocketClient.java file. In the Class Summary table in the SSLClient Package-Summary.html file, the class is listed as SSLSocketClient.MyListener.
|
073187
|
There is a known issue with the TLS_RSA_WITH_DES_CBC_SHA cipher when your SSL license allows only export level cryptography. This situation causes a server that is configured to use that suite to fail to start SSL when you boot the server. An example of the error you will see upon failure is as follows:
<Apr 2, 2002 7:32:24 AM PST> <Emergency> <WebLogicServer> <000209><ListenThread.run() failed: java.lang.IllegalArgumentException: Export Restriction on suite: TLS_RSA_WITH_DES_CBC_SHA java.lang.IllegalArgumentException: Export Restriction on suite:TLS_RSA_WITH_DES_CBC_SHA at com.certicom.tls.TLSSystem.setEnabledCipherSuites(Unknown Source) at javax.net.ssl.impl.SSLServerSocketImpl.setEnabledCipherSuites(Unknown Source) at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:667) at weblogic.t3.srvr.ListenThread.run
If your server is configured to use specific cipher suites, to allow your WebLogic Server to start up remove the following from the cipher suites configuration setting:
TLS_RSA_WITH_DES_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA
|
073360
|
There is a known issue with the TLS_RSA_WITH_DES_CBC_SHA cipher suite. Using the cipher suite can cause a BAD_RECORD_MAC exception during SSL handshaking.
If your server is configured to use specific cipher suites, please remove this from the Ciphersuites configuration setting:
TLS_RSA_WITH_DES_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA
An example of the error generated when using this cipher suite with the https administration client:
Failed to connect to https://myhost:7902 due to: [https://myhost:7902: Destination unreachable; nested exception is: javax.net.ssl.SSLProtocolException: FATAL Alert:BAD_RECORD_MAC - A record was received with an incorrect MAC.; No available router to destination]
|
074716
|
The Administrator, Operator, Deployer and Monitor roles are only partially functional in this release. Adding someone to those roles will give them access to the appropriate administrative MBean operations but will not give them access to the Administration Console. To give a user access to both the MBean operations and the console add them to the Administrators, Operators, Deployers and Monitors groups. Furthermore, if you are running in compatibility mode you should make sure that the system user is in the Administrators group.
|
075658
|
There is a known issue regarding accecss control lists (ACLs) for JDBC connection pools when running in compatibility mode or when using File realm as the security realm. If your fileRealm.properties file includes an ACL that grants any permission on a connection pool, the shrink and reset actions will be disallowed for that connection pool, even if you include ACLs that explicitly grant shrink and reset permission.
|
080920
|
By default, roles and security policies cannot be set for an EJB or Web application through the Administration Console unless security constraints were defined in the deployment descriptor for the EJB or Web application.
Workaround:
Use the following command-line argument when starting WebLogic Server to override this problem:
weblogic.security.fullyDelegateAuthorization
No value is needed for this command-line argument; setting the argument is sufficient to turn it on. For example:
java -Dweblogic.security.fullyDelegateAuthorization weblogic.Server
This command-line argument does not work with EJBs or EJBs methods that use <unchecked> or <restricted> tags or Web applications that do not have a role-name specified in the <auth-constraint> tag.
|
081250
|
A disabled user account in the LDAP Active Directory Authentication provider still authenticates to WebLogic Server.
Workaround:
Modify the user filter to only return accounts that do not have the UF_ACCOUNTDISABLE bit set. For example:
Original Filter microsoft.user.filter=(&(sAMAccountName=%u)(objectclass=user))
Modified Text
microsoft.user.filter=(&(sAMAccountName=%u)(objectclass=user)(!userAccountControl:1.2.840.113556.1.4.803:=2))))
|
082106
|
If a user account becomes locked and you delete the user account and add another user account with the same name and password, the UserLockout attribute will not be reset.
Workaround:
See Protecting User Accounts.
|
083155
|
The array of Strings returned from the getValues() method in the weblogic.security.service.ResourceBase class does not support String array value types. Specifically, the JNDIResource "path" key and the EJBResource's "signature" key always return null. If you are using WebLogic 7.0 (without Service Pack1), you may also get a NPE when there are no non-null values in the array.
|
083242
|
After configuring a Realm Adapter Authentication provider in a security realm, WebLogic Server will not boot.
Workaround:
Before you configure the Realm Adapter Authentication provider, create an empty filerealm.properties file in the directory from which you boot WebLogic Server. When you configure the Realm Adapter Authentication provider, set the Control Flag to Optional. Reboot WebLogic Server.
|
083273
|
When the username/password combination for a domain is specified as weblogic/weblogic, the Administration Console pre-populates the username and password causing a potiental security risk.
Workaround:
Do not use the username/password combination of weblogic/weblogic in production.
|
WebLogic Server Known Issues
Change Request Number
|
Description
|
030981
|
The JDBC t3 Driver, which was deprecated in WebLogic Server 6.0, was removed from this release.
|
042781
|
The default location of server logs has been changed. The file name and location for log files is now as follows:
For a server log file, ./<SERVER_NAME>/<SERVER_NAME>.log
For a domain log file, ./<DOMAIN_NAME>.log
|
046154
|
When using LOBs with the WebLogic jDriver for Oracle, you must set the NLS_LANG environment variable on the client to the same as the character set used in the database.
In previous releases of WebLogic Server, when writing LOBs to the database, the database character set was used. In this release, the client character set is used to conform to Oracle recommendations.
|
059543
|
If you use the Administration Console to update an XML Registry by setting the DocumentBuilderFactory text field to NULL, then subsequently view the same XML Registry, the DocumentBuilderFactory text field is empty. It should contain WebLogic Server's default DocumentBuilderFactory, weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl.
|
060554
|
There are two new system properties that you can use to redirect your standard out and error logs to a file: -Dweblogic.Stdout="weblogic_stdout.log" -Dweblogic.Stderr="weblogic_stderr.log"
|
060953
|
WebLogic Server dynamically makes security changes to the config.xml file after startup. To make sure the updated config.xml is written to disk, either wait 5 minutes for the config.xml to be written to disk at its regular interval or perform a controlled shutdown of WebLogic Server to force the config.xml file to be written to disk.
|
062673
|
The JTA RMI interceptors in WebLogic Server 7.0 reject incoming and outgoing requests if the source or destination is a pre-7.0 server and the local server only supports t3s.
|
063635
|
If you deploy an exploded Web application, copy the Web application to a different directory, and deploy it again with a different name and from a different source, the second deployment will fail.
|
063799
|
Calling getLogFileName on VirtualHostMBean returns an incorrect path.
|
064427
|
Windows only supports paths that are 250 characters or less. If the path to your applications is longer than that WebLogic Server may have trouble.
|
064754
|
If you are migrating from WebLogic Server 6.1, the SHUTDOWN command currently no longer accepts the parameters <seconds> and <lock message>. If you used either of these two parameters, they will not function when you start WebLogic Server 7.0 with WebLogic 6.1 scripts.
|
064837
|
In order for SSL (Secure-Sockets-Layer) to work for migrating WebLogic 6.1 customers, two new changes need to be made to allow existing WebLogic Server 6.1 applications to work from a java client:
- -Dbea.home=<installdir> needs to be added to the client command line.
- The CA (Certificate Authority) needs to be in the keystore.
|
065070
|
There is a known issue with the logging of WebLogic Server jCOM error messages. COM warnings are incorrectly logged as errors, as in this example:
<Error> <COM> <210000> <IOXIDResolveropNum 5 invoked. This method is not implemented.>
|
065299, 067642
|
The Java HotSpot(TM) Server VM is not yet supported on WebLogic Server 7.0. Use the certified client version of this VM.
|
066581
|
WebLogic Server has its own version of javax.management.timer.Timer, called weblogic.management.timer.Timer. If you use the WebLogic class and instantiate it, you will have timers that use the WebLogic thread pools and honor the user identity when executing their listeners.
|
066723
|
Managed Server discovery is off by default when you are in development mode. To turn it on, add -Dweblogic.manager.discover=false to your command line argument that starts WebLogic Server.
|
067078
|
The built-in XML parser incorrectly returns an error when attempting to parse an XML document whose DOCTYPE declaration contains only a root tag name.
|
067087
|
WebLogic Server currently does not provide a means to set security permissions within a weblogic-applications.xml file.
|
067814
|
If you wish to use an LDAP browser to view the embedded LDAP server on WebLogic Server, try using the following input:
host: localhost port: 7003 Anonymousbind LDAP Version 3
|
067868
|
When using the HotSpot JVM the server can hang when running large deployments. To alleviate this problem, try setting your -XX:MaxPermSize to a higher figure.
|
068186
|
If you install WebLogic Server version 7.0 on a multi-homed, Windows 2000 system, configured servers will incorrectly resolve each IP address to the common DNS name for the system itself. For example, consider a multi-homed Windows 2000 machine named "MyWin2KMachine" and having IP addresses:
192.168.1.105 192.168.1.106 192.168.1.107
If you install multiple WebLogic Server instances on the system using IP addresses 192.168.105, 192.168.1.106, and 192.168.1.107 for the servers' Listen Address attributes, all servers will yield the common DNS name, "MyWin2KMachine," when resolving their IP addresses. This can lead to conflicts when accessing resources on remote servers. To address this problem, use either one of the following workarounds:
192.168.1.105 MyWin2KMachine1 192.168.1.106 MyWin2KMachine2 192.168.1.107 MyWin2KMachine3
If the machine's IP addresses have names registered with a DNS server, use those externally-available DNS names instead of IP addresses when configuring servers' Listen Address attributes. For example, configure servers using MyWin2KMachine1, MyWin2KMachine2, and MyWin2KMachine3 rather than using 192.168.105, 192.168.106, and 192.168.107. Note that this problem does not affect other software platforms, including Windows NT.
|
068228
|
When you are not running in compatibility mode and you use the command line Administration tool, you may be prompted for a `guest' password. The default password for "guest" is "guest".
|
068247
|
The JSPs included with WebLogic Server 7.0 are not being pre-compiled before they are accessed for the first time. If you are deploying precompiled JSPs, WebLogic Server may recompile them to the /wlnotdelete/ directory.
|
068361
|
If you are migrating a 1.1 EJB from Bean Managed Persistence to Container Managed Persistence, selecting the bean and checking "Container-managed persistence" should generate Advanced and Automatic Key Generation options, but does not.
|
069278
|
When using the command line to create a connection pool, in the properties string you can only escape the double quotes on platforms where the shell removes one set of quotes. On platforms where the quotes are not removed during this process, you should use only one set of double quotes. You can also repeat the property argument for each connection property, which eliminates the need for quoting a string of properties. For example:
-property Property user=scott -property Password tiger -property URL jdbc:weblogic:oracle:ora817
|
069572
|
A 7.0 server with a network channel configured communicating with a 6.x WebLogic Server may have additional channel information on the wire truncated. The impact of this is as follows: a 7.0 server binds an object to a 6.1 JNDI tree, and another 7.0 server looking up the RMI object will not see the entire channel information from the RMI stub.
|
069602
|
The JTA implementation in WebLogic Server was updated to comply with the JTA specification version 1.0.1a, including minor changes to the Transaction.commit() and TransactionManager.setTransactionTimeout(int) methods.
|
070429
|
There is currently no way to re-boot with the last known good COMMO configuration.
|
070747
|
The WebLogic jDriver for Informix was removed from the release. Use the JDBC driver from Informix available at http://www.informix.com/evaluate/.
|
071338
|
If you use the webLogic.Deploy tool and mistakenly add strings of unnecessary characters, they might be read in as real data.
|
071954
|
In previous versions, the weblogic.management.Admin class had the static method, getActiveDomain(). In Weblogic Server 7.0, getActiveDomain() is no longer static. In its place, use Admin.getInstance().getAdminMBeanHome().getActiveDomain();
For an example of how to use this alternative API, see Determining the Active Domain and Servers in Using WebLogic Server JMX Services.
|
072646
|
When using Netscape version 4.75 or older on Windows 2000, file associations may not be converted correctly from the same used for Internet Explorer. This results in the following behavior when opening About WebLogic Server 7.0, About Examples, and About Pet Store from the Windows Start menu:
|
072940
|
If your config.xml file does not have the <SecurityConfiguration> element set, or is missing the credential and name attributes within that element, your server tries to create this attribute. If your config.xml file is writeable, your java client caches the value of this credential in its local JVM memory space. Then, for the lifetime of the JVM, the java client uses this credential. However, once the JVM gets re-started, it is denied access because it does not have the credential. In order to avoid this, simply save your config.xml file once, when it has the credential already set.
|
072993
|
When deploying to multiple Managed Servers you may encounter problems if any of your jar files and war files have the same name.
|
073395
|
There is a problem with Sun's Pet Store application when you try to run it with more than one client and use an Oracle database.
|
073647
|
Currently only users in an Administration role can use the AdministrationPort.
|
073737
|
If you restart an Administration Server for an active domain, the Administration Server can fail to discover its Managed Servers. This occurs with the following configuration:
A multihomed machine running a Windows operating system, in which the Administration Server and one or more processes use the same listen ports (but on different IP addresses). It is caused by a limitation of the Windows operating system. If a restarted Administration Server does not discover its Managed Server, commands that you issue to a domain via the Administration Server will fail. For example, a Managed Server that starts in Managed Server Independence (MSI) mode can fail to respond to shutdown commands after the Administration Server regains control.
|
073793
|
You cannot deploy an application with untargeted modules if you have not set URIs for the untargeted modules in your config.xml.
|
074296
|
In some situations, the Administration Console allows users to create more than one WebLogic Tuxedo Connector WTCResources MBean. Only one WTCResources MBean is allowed for a given WTCServer MBean configuration. Users may need to remove the extra configuration and restart the WebLogic Tuxedo Connector.
|
074452
|
If your JVM is throwing errors and WebLogic Server is under heavy load, try increasing your java memory heap .For example, modify the command that starts WebLogic by adding the following: MEM_ARGS="-XX:MaxPermSize=128m -Xms512m -Xmx512m"
|
074969
|
You may encounter problems deploying EJBs without JNDI names. BEA recommends that users continue to deploy their EJBs with JNDI names as was done in earlier releases of WebLogic Server.
|
075413
|
There is a known problem with memory leaking when you are attempting to do T3/IIOP server to server interop. A patch that fixes this problem is available at Dev2Dev.
|
075892
|
There is a known JCA problem where connection requests are failing with a weblogic.management.NoAccessRuntimeException. A patch with a fix is available at Dev2Dev.
|
076149
|
If you plan to use JTA for distributed transactions in a clustered environment, do not use "localhost" as the ListenAddress for a server or cluster. Doing so will cause migration of the Transaction Recovery Service to fail and may cause transactions to fail as well. Instead, use the IP address or DNS name of the server or cluster for the ListenAddress.
|
076584
|
There is a known issue with jCOM. The classes generated by com2java extend com.bea.jcom.RemoteObjRef; however, com.bea.jcom.RemoteObjRef was not repackaged correctly and is still in the original com.linar.* package.
If you wish to compile the generated classes, do the following:
Edit the generated *.java files to replace all instances of com.bea.jcom.RemoteObjRef with com.linar.jintegra.RemoteObjRef.
In the classes that implement com.linar.jintegra (com.bea.jcom.RemoteObjRef) replace getJCOMDispatch() with getJintegraDispatch().
|
076988
|
The original release of WebLogic Server 7.0 did not include the mod_wl_20.so shared object that is needed for the Apache plug-in. This binary is included in WebLogic Server 7.0, Platform Edition and later versions.
|
078647
|
There were intermittent problems with the embedded LDAP server when redpoying applications that later on, usually after a restart, were causing WebLogic Server to fail. These problems were fixed with the release of WebLogic Server 7.0 Platform Edition.
|
WebLogic Tools Known Issues
Change Request Number
|
Description
|
064893
|
The following deployment descriptor elements cannot be edited in WebLogic Builder:
ejb-jar.xml
weblogic-cmp.xml
|
065250
|
WebLogic Builder may fail to access a database on a server if the driver classes for the database are not on the client.
|
065760, 065769
|
WebLogic Builder imposes the Unicode Transformation Format UTF-8 on the XML files it writes. WebLogic Builder does not provide an option to save XML files to other formats.
|
066466
|
WebLogic Builder does not provide the option to cancel operations.
|
066668
|
On Linux, WebLogic Builder's file browser opens at root instead of current directory.
|
068152
|
The operations Add, Edit, and Delete can be slow in the EJB elements of WebLogic Builder.
|
068165
|
In the Add dialog in Resource Links, in the WebLogic Settings, J2EE Links, WebLogic Builder incorrectly offers a selection of application scoped data resources.
|
068620
|
Table columns may not resize properly in WebLogic Builder.
|
069568
|
WebLogic Builder cannot map multiple roles to a method in EJB method permission.
|
070968
|
WebLogic Builder does not detect classes added to modules unless you close and re-open the module.
|
071833, 072541
|
WebLogic Builder support for RARs does not include generation of deployment descriptors.
|
072700, 074591
|
If you use WebLogic Builder's deployment dialog boxto undeploy an application, application the dialog will not show the undeployment. This dialog may also report that applications whose deployment has failed are deployed.
|
073597
|
WebLogic Builder sets initial-beans-in-free-pool and max-beans-in-free-pool values for entity beans.
|
073715
|
WebLogic Builder may not be able to display multiple RDBMS XML files.
|
073975
|
WebLogic Builder incorrectly allows you to add a transaction without specifying a method or a transaction attribute.
|
074021
|
The scrollbars in WebLogic Builder may not necessarily indicate when offscreen controls exist.
|
074210
|
Optimistic concurrency strategy does not work in WebLogic Builder.
|
074247
|
In WebLogic Builder, adding a finder with a duplicate method name may update the original finder instead of adding the new one.
|
074322, 074856
|
In WebLogic Builder, cancelling an edit action may not work.
|
074535, 074570
|
WebLogic Builder may have problems generating XML files for a bean that contains a recursive relation, possibly treating a CMR field as a CMP field.
|
074566
|
Finders or CMP values modified through WebLogic Builder's BeanGrid/Edit (like include-update) may not be represented in the individual panels.
|
074620
|
In WebLogic Builder's Relations wizard, when you check the bi-directional box, CMR field type is enabled even if the relation is 1-1, and the wizard doesn't allow you to leave the field blank.
|
074622
|
In editing a CMP field using the WebLogic Builder's pop-up dialog, if you set column type to OracleCLOB and then click on the CMP tree node, the column type change doesn't show up on the CMP panel.
|
074634, 074955, 074972
|
Using WebLogic Builder's Relations wizard to edit the relations of a CMP with multiple relations already configured results in an exception.
|
074639
|
When you edit a Finder method name using WebLogic Builder's editing panel, the change doesn't propagate to XML. When you edit using the Finder pop-up dialog, the change does not propagate to XML or to the editing panel.
|
074728
|
WebLogic Builder improperly does not allow changing a method to a local method.
|
074754
|
Editing some transaction attributes may cause WebLogic Builder to create duplicate descriptors.
|
074766, 074773
|
WebLogic Builder cluster settings and allow-concurrent-calls setting for stateful session beans may not work.
|
074775
|
It is recommended that you set the enable-call-by-reference element explicitly in WebLogic Builder.
|
074961
|
If you use WebLogic Builder to generate web.xml descriptors, it creates a security-role "guest" which pertains to the pre-7.0 security protocol.
|
075005
|
Specifying an invalid drive when opening a component (type bogusDrive
in the textbox, press enter and select open) in WebLogic Builder causes a NullPointerException.
|
075006
|
In some circumstances WebLogic Builder will not properly construct one-to-many relations.
|
075521
|
The search function in WebLogic Builder help will return duplicate results for some search terms.
|
075034
|
Using WebLogic Builder to add idempotent methods may cause an IllegalArgumentException.
|
075046
|
WebLogic Builder may fail to show that a finder method has been deleted.
|
075119
|
WebLogic Builder does not necessarily enforce the filling out of required fields, which may result in bogus deployment descriptors.
|
075129
|
If you switch a stateless session bean to stateful, WebLogic Builder may not show that the module is dirty.
|
075228
|
WebLogic Builder may throw an assertion error if you delete a transaction or permission method.
|
075586
|
If you want to use WebLogic Builder with the WebLogic Server Examples Server or examples, you should run setExamplesEnv (located at %SAMPLES_HOME%\server\config\examples) before starting WebLogic Builder, so that files needed to run the PointBase database server will be added to the classpath. If you do not, you will get database error messages.
|
075753
|
Some descriptor elements may pass through WebLogic Builder validation and then be found to be in error by ejbc.
|
075924
|
In some cases, WebLogic Builder may not properly generate descriptor files for nested WAR files in EARs.
|
075936
|
WebLogic Builder may generate an illegal value for the element <estimated-bean-size>.
|
075936
|
WebLogic Builder may generate an illegal value for the element <max-cache-size>.
|
WebLogic Tuxedo Connector Known Issues
Change Request Number
|
Description
|
067275
|
Load balancing and fail over not supported with WebLogic Tuxedo Connector in a cluster using RMI over IIOP.
|
070255
|
Integer array object passed by value from Tuxedo to WebLogic Server throws weblogic.utils.AssertionError.
|
WebLogic Web Services Known Issues
Change Request Number
|
Description
|
067031
|
The following files are missing from the webserviceclient.jar file, causing SOAP attachment processing to fail when using the client JAR file to invoke a Web service and manipulate the SOAP attachment:
com/sun/activation/registries/MailcapFile com/sun/activation/registries/MailcapFile.class com/sun/activation/registries/MailcapParseException.class com/sun/activation/registries/MailcapTokenizer.class com/sun/mail/handlers/text_plain.class com/sun/mail/handlers/text_xml.class com/sun/mail/util/ASCIIUtility.class com/sun/mail/util/LineOutputStream.class javax/activation/ActivationDataFlavor.class javax/activation/CommandMap.class javax/activation/DataContentHandler.class javax/activation/DataHandler.class javax/activation/DataSourceDataContentHandler.class javax/activation/MailcapCommandMap.class javax/activation/MimeType.class javax/activation/MimeTypeParameterList.class javax/activation/MimeTypeParseException.class javax/activation/ObjectDataContentHandler.class javax/activation/UnsupportedDataTypeException.class javax/mail/Header.class javax/mail/MessageAware.class javax/mail/MessageContext.class javax/mail/MultipartDataSource.class META-INF/mailcap.default META-INF/mimetypes.default META-INF/javamail.default.providers META-INF/javamail.default.address.map META-INF/javamail.charset.map META-INF/mailcap
If you need to process a SOAP attachment, the workaround to this problem is to extract the needed classes from the weblogic.jar file and add them to the webserviceclient.jar file.
|
067190
|
WebLogic Web services do not support XML Schemas that contain complexTypes and elements with the same name.
|
072268
|
WebLogic Web services do not support XML Schemas that contain complexTypes that inherit from simple types.
|
072519
|
The servicegen Ant task does not support the useServerTypes attribute of the client child element and the typeMappingFile attribute of the service child element.
|
072890
|
The command line version of the servicegen Ant task does not support the following options that correspond to the Ant task attributes:
-overwrite -contextURI -includeEJBs -excludeEJBs -generateTypes
The command line version of the clientgen Ant task doe not support the following options that correspond to the Ant task attributes:
-autotype -overwrite
|
073357
|
SSL is not supported for J2ME client applications.
|
073390
|
The clientgen Ant task does not work correctly when generating a client JAR file from a WSDL that uses the https protocol.
|
073564
|
The clientgen Ant task does not handle the WSDL URL substitution correctly when the build.xml file contains a target that invokes another Ant task.
|
073661
|
WebLogic Web services that are described with an invalid web-services.xml file incorrectly deploy on WebLogic Server, although they are not accessible by client applications trying to invoke them.
|
073899
|
When generating a SOAP fault, WebLogic Web services adds extra non-CDATA characters.
|
074234
|
The default policy for Web services is not correctly set to anonymous.
|
074547
|
When generating the WSDL to describe the service,WebLogic Web services do not generate a service-specific <soap:fault> element.
|
074810
|
WebLogic Web services do not correctly deserialize XML that contains an array of objects with integer multi-ref.
|
074891
|
When using the UDDI Directory Explorer, you cannot remove all the URLs that are listed for a private registry.
|
075286
|
The SSLAdapterFactory class is not catching the NoClassDefFoundError exception at runtime.
|
075617
|
The clientgen Ant task does not correctly create the Web service-specific client JAR file for a WSDL that imports its portType definition from a separate file.
|
075624
|
The clientgen Ant tasks does not correctly handle WSDL files that import an XML Schema.
|
075663
|
WebLogic Web services do not correctly handle SOAP arrays of schema types which map to byte[].
|
075946
|
The invocation of a Web service operation that has security restrictions is rejected when invoking it from the Web service Home page using https, even when using the correct username/password.
|
077585
|
The clientgen Ant task returns an error when attempting to create a client JAR file from a WSDL file that contains an XML Schema that does not specify a target namespace.
|
083493
|
The messages and multicomponent examples in the Web Services examples package do not contain the code needed to generate a downloadable client.jar file.This omission does not affect the functionality of the example which work with the provided client.
|
XML Known Issues
Change Request Number
|
Description
|
70547
|
When using the XML Streaming API on Solaris, some character references do not resolve to the same character as on NT.
|