IBM® WebSphere® Studio Site Developer Interim Fix
002
for WebSphere Studio Site Developer, Version 5.1.1
This refresh contains fixes for the following problems:
Relational Database tools
There is no functional change to the Relational Database tools.
Processing overhead is decreased
since the DBSelect.execute() method explicitly checks for small vectors
instead of catching an ArrayIndexOutOfBounds exception when the vector
is too small.
Server tools
- J2C Reap Time Not Saved
In the WAS server configuration editor, the J2C reap team could be
modified, but
would not be saved correctly and the changes would be lost. This issue
has been
resolved.
- Create Tables and data sources
Generates Unnecessary Data Source
The create tables and data sources feature would incorrectly generate a
data source
when a CMP connection factory with the same JNDI name already existed.
This would
cause a failure at runtime because the generated data source and the
CMP connection
factory had the same JNDI name. Data sources are now only generated
when there is
no existing data source or CMP connection factory.
- Hot Method Replace Incorrectly
Disabled
The hot method replace in debug mode feature for WebSphere v5.0x was
incorrectly
disabled in some cases after applying fixes to the WebSphere server or
test
environment. This feature is now correctly enabled based on whether the
server
supports this feature.
Web service tools
Before the Web service wizards write Java™ files into a project,
the
wizards check to see if identically named files already exist before
overwriting them. In many Enterprise Applications, the Java
files the wizard is about to write may already exist in a different
project, module or JAR file. In v5.1.1 and prior releases, the wizards
are not sensitive to the existence of such Java classes, and will
proceed with writing Java files into the project. The Java files
generated by the wizard will effectively mask any Java classes with
the same name in other projects, modules and JAR files in the
Enterprise Application. This in turn can cause compilation and runtime
errors to occur in the application.
A new check box labeled "Do not overwrite loadable Java classes"
has
been added to the Web Services Code Generation preference page. When
selected, the Web Service wizards will not write any Java classes
to the target project that (a) do not already exist in the project
and (b) do exist in a project, module or JAR file that will be loadable
from the target project when the application is running on the server.
This check box applies only to JAX-RPC and WebSphere deployment Java
classes generated by the wizards.
By default, this new check box is not selected, preserving the
original
behavior of the tools. You must select this check box for the wizards
to
recognize Java classes in other projects, modules and
JAR files in the Enterprise Application. From the main menu, click Window > Preferences. Expand Web Services and click Code Generation.
XML Editor
- Content assist not available
within JSP tags
Attribute names were not proposed in content assist for any <jsp:
*="" |=""> tags, for example <jsp:usebean> or
<jsp:getproperty>. This has been fixed.
- As-you-type validation
incorrectly marks qualified attribute as
error
Attributes within a namespace were being marked as invalid. For
example, in <element ns:attr="value"> "ns:attr" would be marked
as
invalid. These attributes are no longer
marked as problems.
- Child elements without
corresponding schema definitions not
properly handled in "lax" mode
Children of an element without corresponding definitions in a schema
were being marked as errors, even if the element was supposed to be
processed in "lax" mode which allows this. This has been fixed.
Web tools
The following limitation has been fixed: Adding a page data object from
the Page Data view to the JSP Faces editor via drag/drop would not free
memory after the drop or when the editor closes.
J2EE Development
- Access intents
You may not be able to edit access intents that have been created or
edited in the WebSphere Application Assembly Tool.
- Null pointer exception
Null pointer exceptions are caused by exporting a WAR with no
extensions.