Hi Gail,
Following is my comment for the release notes. Most of that applies to
the Known Issues section.
This section really needs the initial evaluator to confirm
for you that the issue still exists, especially those filed many
months ago. I commented on a few which i know or i can try that out
myself. But there are still quite a few that needs to be looked at by
others.
pg 11. Update Tool Integration
This tool provides automated updates, and facilitates managing
add-on components
and related applications that are available for extending Enterprise
Server v3 functions.
UpdateTool in admin console will NOT provide updates. It allows you to
install additional components, which will then be available after
server restart. Installed Components and available updates will be
provided for "view" only. User cannot update or remove any components
when server is running. Thus , this operation cannot be preformed in
Admin Console. Even if using the standalone updatetool, server must
be stopped for this operation.
pg 12. Support for Scripting Languages
- jMaki: A framework for creating Ajax web applications
Support for these scripting languages is provided by components that
are available through
Update Tool.
I don't think there is any component specific for jMaki.
Please
confirm with other developer.
- pg 12. Enhancements to the appclient Utility
The -targetserver option is added to enable the server and port
number of the target to be
specified.
The above applies to cluster profile in v2, I think this sentence
should be removed.
-pg 21 Known Issues
It seems that a few of the older issues has been fixed. You may want
to confirm that.
Here is a few that i can no longer reproduce and could be removed.
pg 23. [JDK_Issue] Warnings in server.log during clicks in the
Administration Console GUI on
deployed samples (Issue 7206)
I have tried many applications including the 2 attached in the issue.
No longer see this warning.
pg 24. [JDK_Issue] Null pointer exception on server restart (Issue
8299)
I don't think this issue still exists. I never see this when i tested
out restart feature in GUI.
pg 24. Load average climbs to 2 or 3 every few days and stays there
until Enterprise Server is restarted.
For more information, see Issue report
(http://glassfish.dev.java.net/issues/show_bug.cgi?id=6819).
This issue is filed against 9.1peur2. Is this really an issue with
v3 now ?
Workaround tells user to add a JAR to classpath-prefix in domain.xml,
where classpath-prefix is not even supported in v3.
pg 25. At startup, Enterprise Server throws a null pointer
exception.
see Issue report
(http://glassfish.dev.java.net/issues/show_bug.cgi?id=9472).
I haven't seen an NPE during startup for a long time, is this still an
issue now ?
pg. 26. The command does not check that domain is not running
(Issue 6196)
I believe this has been fixed, and should be removed from the release
note.
I feel that there should be some 'separator' or 'heading' or more
spaces after the Workaround and the Description of the next issue.
The current layout gives me a feeling that Workaround continues until
the Description section.
thanks
Anissa
Gail Risdal wrote:
Hello,
The GlassFish v3 Release Notes are available for final review:
http://wiki.glassfish.java.net/Wiki.jsp?page=ReleaseNotes
Please review this document and return your comments to me no later
than COB Monday, December 7. Sooner would be even better.
Given the schedule, your comments should focus on changes that must
be made for the GlassFish v3 release. Enhancements must wait until
later.
If something must be changed or added, please provide the exact
content, description, location, URL, etc. I won't have time to search
for it or do a lot of follow up.
Thanks in advance,
Gail