Thanks Jeremy for identifying the issue and providing a fix, and Andriy
for looking into it.
Agree with Andriy that this fix will not work and actually will cause
error in other screens when doing an update.
Actually this is a more general issue about how the console provide
error message in dealing with stalled elements, and not just for cluster
itself. There are 2 use case that the error message can be improved:
1. Retrieve and display inform for a deleted object, when user click on
a stalled tree node.
2. Update a deleted object. This is the case where user is already in
the info page and the object got deleted by other before the Save button
is pressed.
Currently, depending on the object type, the error msg maybe
informative, or just suggest checking server.log
We need to look at how to provide a general solution to deal with all
object type. I opened up
http://java.net/jira/browse/GLASSFISH-18429 to track this.
thanks
Anissa.
On 2/28/12 8:58 AM, Andriy Zhdanov wrote:
> Hi Jeremy,
>
> It's not a good idea to add a special parameter to that general method.
>
> Adding a separate handler to validate the cluster name or making that
> input optional could be better.
>
> Note, gf.updateEntity is used in about 20 files in
> trunk/appserver/admingui, and it must not be just that.
>
> Thank you.
>
> On 02/28/2012 09:52 AM, Lv Songping wrote:
>> Dear Anissa Lam：
>> I have the pleasure to tell you that I found an unfriendly GUI
>> notification in glassfish. When a consumer saved the general attributes in
>> cluster after the cluster is deleted by other consumer, the JavaEE manage
>> console can't tell the consumer what's happened and how to deal with it.
>> I have arranged my idea and solution in attachment file, I wonder that
>> if you can accept my idea and change the code of glassfish V4.0.22. Wish
>> best regards.
>>
>> Yours sincerely
>> Jeremy Lv
>>