|
This refresh contains fixes for the problems listed under the
following components:
Web Service
Previous fixes
from ifix 002,003,005
1. 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.
2. Deserializing CDATA sections from XML documents.
In xsd.bean.runtime.jar in plug-in 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.
3. Errors in the Task
view and various problems at runtime.
When creating a skeleton Web service from WSDL, the wizard neglects to copy
XSD files referenced by schema directives to your Web service project. The
absence of these XSD files from the project result in errors in the Task
view and various problems at runtime.
4. Includes any Web
service code generation (for example Java2WSDL and WSDL2Java) defects fixed
by WebSphere Application Server cumulative fix
5.1.0.5.
5. WSDL validator incorrectly reports the schema as invalid.
This fixes the problem where "<" or ">"
is used in an inline schema in a WSDL document and the WSDL validator incorrectly reports the schema as invalid.
New fixes for
ifix006
6. Compilation errors in generated code
during top down scenario: If
you create a Web service top down from WSDL and XML Schema, then change the
schema, then recreate your Web service, the wizard
will not regenerate the Java beans and skeleton for your Web service. The
wizard will, however, regenerate fresh deployment files, resulting in
compilation errors due to the old Java beans and skeleton falling out of
synchronization with the new deployment files. The wizard has been fixed to
regenerate all the Java classes, including the deployment, bean and
skeleton classes. Important: With the application of this fix, the wizard
will replace your previous skeleton class and any business logic within it
by a fresh skeleton (provided you have enabled file overwriting). To help
protect against the loss of your business logic, your previous skeleton
class will be copied to a backup file before it is overwritten. The backup
file is stored in the same folder as your skeleton, and is named after your
skeleton .java file but with the additional suffix ".bak". At most one such backup is produced.
7. The Java and XML code generators in the
Web services GUI tools in WebSphere Studio
Application Developer have been upgraded based upon the Java2WSDL and
WSDL2Java emitters from WebSphere Application
Server 5.1.1 Cumulative Fix 1 (5.1.1.1) amended with a few additional
emitter fixes:
IMPORTANT NOTES: This
upgrade applies to the Web services wizards and related tools found in the
graphical user interface only. This upgrade does not apply to the
command-line tools found in the WSAD bin/ directory (WSDL2WebService,
WSDL2Client, etc). After applying this upgrade, the code generated by the
Web services tools may not compile against WebSphere
Application Server v5.0.2, which is the level of the v5.0 Unit Test
Environment (UTE) in WSAD. Should this occur, apply WebSphere
Application Server 5.0.2 Cumulative Fix 8 (5.0.2.8) to your UTE and to any
other installed v5.0.2 servers as necessary. Further details about WAS
v5.0.2.8 and v5.1.1.1 cumulative fixes are available at this site:
8. New “noWrappedOperations"
option: The WSDL2Java tool included with WebSphere
Application Server features a "-noWrappedOperations"
option used to trigger generation of request and response beans for
top-level complexTypes and complexType
elements referenced by WSDL operations. This option has not previously been
available to users of WebSphere Studio
Application Developer. It is now available via Windows -> Preferences
-> Web Services -> Code Generation -> Generate Java from WSDL
using the no wrapped style.
XML Tools
Previous fixes
from ifix 002,003,005
1. Incompatible method
causes an exception.
The incompatible method org.apache.xerces.dom.DocumentImpl.getEncoding() causes an exception when you use a Xerces version that does not provide the method.
2. Generated JavaBean™ code is read-only.
After generating JavaBeans, the generated code might 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.
3. The defect causing
attributes with namespace to be underlined as errors (red squiggles) in an
XML file based on a DTD is fixed.
4. XML Catalog is not
working as expected when multiple levels of imported schemas are involved.
For example, Schema A imports Schema B from the Internet (URL reference).
Schema B is redefined in the XML Catalog and points to a local file Schema
B'. Schema B' imports Schema C which is on the Internet. Schema C is
redefined in the XML Catalog to be Schema C'. With this fix, Schema C' is
used or loaded, and not Schema C.
New fixes for
ifix006
5. WSDL editor doesn’t and XSD docs:
This fixes the problem in which the WSDL editor doesn't import XSD
docs in the inline schema import.
6. Migration issue from WTE 5.1.0.3 to WTE
5.1.1:
This fixes the following problem. When migrating to WTE 5.1.1 from
WTE 5.1.0.3 we run into a problem with the xsdbeans.jar
we got from WSAD 5.1.2. The runtime error is due to no existing method getEncoding in class.
7. WSDL Validation:
This fixes the following problem related to WSDL validation. When
validating a WSDL document there may be some spurious WS-I warnings or
errors that appear in the task view. These usually pertain to authenticity
of the types or QNames within the description.
This fix eliminates spurious messages such as: A wsdl:types element contained a data type definition
that is not an XML schema definition. An XML schema import element
references something other than an XML schema definition. A QName reference that does not refer to a schema component, is using neither the target namespace of this
WSDL nor the target namespace of a directly imported WSDL component. A QName reference that is referring to a schema
component, uses a namespace not defined in the targetNamespace
attribute on the xs:schema
element, or in the namespace attribute on an xs:import
element within the xs:schema element.
Strut Tools
New fixes for ifix006
Exception thrown
during headless Ant build:
This fixes a problem in which an InvocationTargetException
(caused by a NullPointerException) is thrown
during a headless Ant build.
J2EE Tools
Previous fixes
from ifix 002,003,005
1. A memory leak that
occurred when an Enterprise Application with deployable information was
created and subsequently deleted is fixed.
2. The following
problem during export is fixed:
It is not a recommended practice to use a different folder for your source
folder and for your output folder; however, it is supported. Prior to this
fix, if you used separate source and output folders and there were files in
the source folder that were not in the output folder, then the export
failed with an error dialog.
New fixes for
ifix006
3. Binary projects fail to load in the
dependency editor: Before
this fix binary projects were failing to load and
show in the dependancy editor, the problem was if
the archive was not indexed it would fail to find the Deployment
Descriptor, the fix was to reindex the archive on
failure.
4. Static fields in EJB beans that load
resource bundles interrupt deploy: This fixes
the problem when an EJB bean has a static field which loads a resource
allowing deploy to finish successfully. e.g. static ResourceBundle
resource = resourceBundle.getBundle("com.text.textresource", Locale.getDefault());
5. Problems with "headless Ant"
tasks:
The runAnt.bat and runAnt.sh
have been fixed. getProjectData
(with new J2EE natures), projectGetErrors (gets
error message). J2ee Export InvocationTargerExceptions
now display the underlying cause. New importProject,
importProjectSet, workspacePreferences,
etc complete Ant AutomatedBuild example (see the
docs\index.html). complete JACL AutomatedDeploy
example (see the docs\index.html)
6. Utility java project problems:
When a java project using a Websphere jre was added to a EAR project
as a Project Utility through the Application Editor the utility java
project was getting 2 jre's showing up on its
java build path instead of one. The old jre on
the utlity project was not getting removed adding
it to the EAR. With this fix there will be only one jre
of the ear showing up on the utility java project.
7. Server Targeting problems:
When a java project using a Websphere JRE
is created and added to a EAR with the same Websphere
server target as a Project Utility using the Application Editor, the java
project was not getting the WebSphere server
container set on it. With this fix the Java project will get both the
server target classpath containers set on it.
DATA Tools
Previous fixes
from ifix 002,003,005
1.
The problem of duplicate table constraint names
generated during EJB top-down mapping is fixed.
2.
You can now connect to and work with a DB2® z/OS®
Version 8 database.
3.
When Application Developer is connected to a Microsoft®
SQL Server database, if you import a table from the Data Explorer view to
the Data Definition view, non-NULLABLE table columns that are not primary
keys are changed to NULLABLE.
4.
A null pointer exception no longer occurs when you are
editing a z/OS Java™ SP from Data Explorer, and you edit and save the WLM
Environment field in the build page of the editor. The WLM environment
field should be read-only when browsing from the Data Explorer view.
5.
In the build page of Stored Procedure editor, bind options
were not set properly when importing a z/OS V8 Java SP that was NOT built
using DNSTJSPP. This is now fixed.
Web Tools
Previous fixes
from ifix 002,003,005
1. 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 allow for the modification of its attributes.
2. 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.
3. Missing values for
IME mode attributes for DBCS.
The values for the IME mode attributes in All tab
for DBCS languages are not provided.
4. Faces Client Components
cannot be dropped.
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
5. Graph component
problems:
§
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.
6. Group operation
"MIN" not working as expected.
For Mozilla browser, the group operation
"MIN" was not working as expected -- some data points were not
plotted.
7. Some client data
created from a JavaBean cannot be bound.
If a client data is created from a JavaBean that
uses a collection type such as List, some data cannot be bound to a
component.
8. Error when using
"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 might
break and a run-time error may occur.
9. Perform build
automatically on resource modification option problem.
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 JavaBean source is imported but has not been compiled.
After the fix, necessary JavaBean source is
automatically compiled and client data is successfully created.
10. 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.
11. 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, and
if the oldest page file name was the same page as the current page file
name, its server side representation was deleted making the current page
inoperable.
12. Compile errors in
generated mediators.
Compile errors occurred in generated mediators when the client
attribute contained XML reserved characters or quotes.
13. Errors in generated
EMap .
Errors occurred in generated EMap when the client
attribute contained XML reserved characters or quotes.
14. Back quote causes
data corruption.
Data corruption resulted when client attribute contained a back quote (it
was unnecessarily escaped by adding a back quote).
15. Frequent restarts
when Faces JSP™ Web project is 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-->references
--> Web Tools --> Faces --> Server Behavior. Click the
auto-restart check box to clear it. This prevents server restarts. Keep in
mind that to run properly the application should still be restarted
manually after editing is complete.
16. JavaServer™ Faces checkbox and radio button
problems:
This fixes the problem with the JavaServer Faces
(JSF) Checkbox and RadioButtonGroup components
where setting the "required" attribute to true had no affect when
the page was submitted. It is now checked on the server.
17. Page Designer
problems:
Objects in the Design view of Page Designer previously could not be
selected. For example, if you had a SELECT tag in a page, you could not
click any object laid out below the tag. This is now fixed.
18. Faces Portlet problems:
§
Faces form-handling loses information in a JSR 168
Faces Portlet.
§
Click-to-Action target action is not called for a
Faces Portlet.
19. 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.
New fixes for
ifix006
20. JSF attribute problem:
This fixes the following
problem for input and output components, if a user binds the value field on
the Basics page of the Attributes view to an Integer object, the Format
page is not updated accordingly.
21. Page designer
sometimes generates a page with an error:
This fixes the following problem. In the Page Designer, changing
alignment of the TABLE tag by the Attributes View sometimes generates a
page with an error.In XHTML pages, the align
attribute of the DIV tag is invalid, but you can add a DIV tag with an
invalid align attribute into a page as a parent of the TABLE tag by the
Attributes View.
22. Problems with JSF currencySymbol attribute:
This fixes the following problem. When a JavaServer
Faces (JSF) inputText field is configured with a
number converter that has the currencySymbol
attribute set it will fail validation on the server if the currency symbol
does not match the locale of the server. When a JavaServer
Faces inputText component is configured with a
client side number validator and a Japanese currencySymbol is specified validation will fail.
23. JSF with client
side validator problem:
This fixes the following problem. When a JavaServer
Faces inputText component is configured with a
client side number validator the decimal point is
not handled correctly.
24. JSF Required
Attribute not working:
This fixes the
following problem. When a JavaServer Faces RadioGroup and Checkbox component has its
"Required" attribute set it is not honored.
25. JSF selectOne problems:
This fixes the
following problem. When using a JavaServer Faces selectOne component a validation error is reported if
nothing is selected.
26. JSF error when
using Option button:
This fixes the
following problem. When configuring a JavaServer
Faces inputText and setting the converter options
through the Options button an error and possibly an application lockup may
occur when pressing ok.
27. JSF null pointer
when using select component:
This fixes the following problem. When adding select items to a JavaServer Faces select component a null pointer error
may be reported.
Documentation
Previous fixes
from ifix 002,003,005
1. A problem with the tutorial entitled
"Displaying Dynamic Information on Web Pages with JavaServer
Faces" is fixed:
When you begin Module 2 of the tutorial without first completing
Module 1, the JSF data objects do 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.
New
fixes for ifix006
2. Navigation fixes to support WSADIE
navigation:
This fixes the Information Center navigation to
enable WebSphere Studio Application Developer
Integration Edition to add documentation to the existing navigation
structure.
EGL
New
fixes for ifix006
1.
New fixes to EGL:
This fixes various problems in EGL Debugger, EGL generation/runtime,
and VA Generator to EGL migration.
2.
After installing the IFix, copy the following files into the "<install_directory>\bin" directory, replacing
the older version of the file that already exists in the \bin directory: eglbatchgen.jar from "<install_directory>\wstools\eclipse\plugins\com.ibm.etools.egl.batchgeneration_5.1.2.1"
VAGenMigJava.exe from
"<install_directory>\wstools\eclipse\plugins\com.ibm.etools.egl.vagenmigration_5.1.2.1\database"
VAGenMigST.exe from "<install_directory>\wstools\eclipse\plugins\com.ibm.etools.egl.vagenmigration_5.1.2.1\database"
If you are migrating from VisualAge Generator, you must reinstall the Stage 1
Migration Tool that runs on VisualAge Generator
Developer as follows:
If you use VisualAge
Generator on Java, do the following:
Make sure VisualAge
Generator on Java is shut down.
Run the self-extracting file
VAGenMigJava.exe and point to your VAGen install
directory. You can find
VAGenMigJava.exe in <install_directory>\bin
Add the migration feature as
described in Chapter 4 of the VisualAge
Generator to Enterprise Generation Language Migration Guide. You do not need to delete the old
version of the migration feature -- just add the new version.
If you have previously run
migrations, clean out the migration database by running setupTables.bat
as described in Appendix G, section "Resetting the migration
database".
If you use VisualAge
Generator on Smalltalk, do the following:
Make sure VisualAge
Generator on Smalltalk is shut down.
Run the self-extracting file
VAGenMigST.exe and point to your VAGen install
directory. You can find
VAGenMigST.exe in <install_directory>\bin
Add the migration feature as
described in Chapter 5 of the VisualAge
Generator to Enterprise Generation Language Migration Guide. You do not need to unload the old
version of the migration feature -- just load the new version.
If you have previously run migrations, clean out the migration
database by running setupTables.bat as described
in Appendix G, section "Resetting the migration database".
|