IBM® WebSphere® Studio Application
Developer Interim Fix
002
for WebSphere® Studio Application Developer, Version
5.1.2
This refresh contains fixes for problems in the following components:
EJB Deploy
- Error dialog appears and then
can be hidden.
During "Generate deploy code" processing, you may receive an error
message that can become hidden by other windows.
- ClassCast exception when using
converter to map boolean to int.
For an EJB 2.0 CMP that has a Boolean attribute mapped to an INTEGER in
the database, WebSphere Studio generates the mapping using
com.ibm.vap.converters.VapNumberToBooleanConverter. The generated code
causes ClassCastException in the CacheEntryImpl class.
- The command-line parsing for the
-rmic option fails.
The -rmic option on the command line provides incorrect results if more
than one option is specified. For example -rmic "keep g"
.
- When the CMR is set to be
returning a Set instead of a Collection.
For relationships returning a Set, the generated code causes a
ClassCastException.
Web Service
- JavaTM and WSDL Web
Service
emitters updated.
The Java and WSDL Web Service emitters have been updated to
match the Java2WSDL and WSDL2Java tools in WebSphere Application Server
version 5.1.0.4 with interim fix PQ88313 applied.
- Deserializing CDATA sections
from XML documents.
In xsd.bean.runtime.jar in plugin com.ibm.etools.ctc.xsd.bean,
the AnyType class was not deserializing (loading) CDATA sections from
XML documents into Apache/IBM® SOAP 2.3 Java classes
generated from
WSDL. This has been corrected.
XML Tools
- Incompatible method causes
an
exception.
The incompatible method
org.apache.xerces.dom.DocumentImpl.getEncoding() causes an exception
when using a Xerces version that does not provide the method.
- Generated Java Bean code is
read-only.
After generating Java Beans, the generated code may be made
read-only, for example when the code is checked-in to a version control
system. In this case, any subsequent attempts to generate the Beans
with the same name should not be allowed and notification about the
failure should be generated.
J2EE Tools
A memory leak that occurred when an Enterprise Application with
deployable information was created and subsequently deleted was fixed.
DATA Tools
Duplicate table constraint names generated during EJB top-down mapping.
Web Tools
- Attributes view shows
BODY tag
instead of CARD tag.
When the cursor is on the tag in the Page Designer
source page, the attribute view shows BODY tag attributes, not CARD tag
attributes, this does not allows for the modification of its attributes.
- Visualized custom tag
in the
wrong position.
When a custom tag has an absolute style position information,
Page Designer adds the visualized tag in the wrong position on the
design page.
- IME mode attributes
for DBCS.
The values for the IME mode attributes in All tab for DBCS
languages are not provided.
- Faces Client
Components drawer.
The following four components in the Faces Client Components
drawer on
the Palette cannot be dropped into a Free Layout Table in Free Layout
Mode:
- Data Grid
- Graph
- Tree View
- Web Service
- Graph component
- When a graph component is dragged from the Faces Client
Components drawer on the Palette and dropped onto a page, then
control-z key is pressed or Edit/Undo menu option is used, the page
generates a broken error. This
is because the graphDraw or surrounding tags were partially deleted.
After the fix, on Undo, the graphDraw tag alone is completely removed,
and the rest of the page is unaffected.
- When the size (height or width) of a graph is changed
using the
Attributes View, the image used to visualize the graph on the Design
view does not change in size. After the fix, the image on the Design
View scales to reflect the specified size.
- The default size of a graph appears too small when the
page is
run on a server. The fonts are hard to read.
- The graph does not expand to fill all available space.
For
example, if
the legend display was turned off, the space occupied by the legend
remained unused.
- The x-axis labels were very close to the x-axis. The
orientation
of
the y-axis title was horizontal.
- When there was a single data
point in a series, the formatting (locale-specific NL formatting or
other custom formatting) was not done on the x-axis labels.
- Group operation "MIN".
For Mozilla browser, the group operation "MIN" was not
working
as expected -- some data points were not plotted
- Client data created from a Java
bean.
If a client data is created from a Java bean that uses a
collection type such as List, some data cannot be bound to a component.
- Set selected object as root in
target component.
If a "Set selected object as root in target component"
snippet is
inserted for a Faces Client component using Quick Edit View, and the
snippet is modified by using Edit Snippet menu later, the snippet may
brake and a runtime error may occur.
- Perform build automatically on
resource
modification.
If the "Perform build automatically on resource
modification"
option is disabled on the Preferences page, sometimes Client Data View
fails to create a client data. This occurs in the event that a new Java
bean source is imported but has not been compiled.
After the fix, necessary Java bean source is automatically compiled and
client data is successfully created.
- Two browse buttons for the Open
and Close icons enabled.
On the Tree Note List tab of the Attributes view for
Tree, two
browse buttons for the Open icon and the Close icon are enabled even if
the icons are not specified. After the fix, the buttons are disabled
appropriately.
- JSF Web pages may stop working
after 16 page requests.
JSF Web pages may stop working after 16 or more page
visits
during a browser session. This is because of the way the JSF state
manager was storing server side representations of the viewed pages. On
the sixteenth page request the state manger deleted the oldest page
representation, if the oldest page file name is the same page as the
current page file name its server side representation was deleted
making the current page inoperable.
- Compile errors in generated
mediators.
Compile errors in generated mediators when the client
attribute
contained XML reserved characters or quotes.
- Errors in generated EMap.
Errors in generated EMap when the client attribute
contained xml
reserved characters or quotes.
- Back quote causes data
corruption.
Data corruption when client attribute contained a back
quote (it
was unnecessarily escaped by adding a back quote).
- Faces JSP Web project running on
a test server.
When a Web project with Faces JSPs is running on a test
server
and the Faces
configuration file changes, the server is restarted automatically to
pick up
the new changes. This may cause frequent restarts so a preference has
been added to the product under Window
> Preferences > Web
Tools > Faces > Server Behavior. Click the
auto-restart check box to deselect it. This will prevent server
restarts. Keep in mind that
to run properly the application should still be restarted manually
after editing is complete.
- Faces Portlet.
- Faces form-handling loses information in a JSR 168
Faces Portlet.
- Click-to-Action target action is not called for a Faces
Portlet.
- Quick Edit view generates
unnecessary code.
Quick Edit view generates unnecessary code for the
removed
scripted attribute, when the following occurs:
- Multiple attributes are
selected in the Page Designer source page.
- One of the selected attributes
is a scripted event.
- The attributes are deleted.
Documentation
A problem with the tutorial entitled "Displaying Dynamic
Information on Web Pages with JavaServer Faces." When beginning Module
2 of the tutorial without first completing module 1, the JSF data
objects will not connect to the sample database correctly. With this
fix, the tutorial explains how to correct this connection so you can
begin Module 2 without completing module 1 first. No functionality is
changed by this fix; it is a change to the documentation.