[ 
http://issues.apache.org/jira/browse/MYFACES-159?page=comments#action_63930 ]
     
Rob Decker commented on MYFACES-159:
------------------------------------

I think throwing a fatal exception in an app under any circumstances that isn't 
fatal just isnt' right. A runtime exception is fatal in servlet container. It 
just gets thrown up and handled by the servlet container or caught by the app 
developers catchall error page(s). I don't see anything fatal about a node no 
longer in a tree in a stateless environment like http.

That said, a hook is a good idea for letting the developer set a method where 
they can add their own message or not. But the message bundles let you do that 
as is. Just set the message to empty.

What could a component user do in a method hook? Stop the tree layout from 
continuing or not? I don't know enough about jsf to add anything really useful 
to that idea.

> Deleted tree2 nodes cause fatal exception
> -----------------------------------------
>
>          Key: MYFACES-159
>          URL: http://issues.apache.org/jira/browse/MYFACES-159
>      Project: MyFaces
>         Type: Bug
>     Versions: 1.0.9 beta
>  Environment: All
>     Reporter: Rob Decker
>     Assignee: sean schofield

>
> If a node gets deleted between the time it is clicked on and when the server 
> processes
> the request I get this error:
>  
>  java.lang.IllegalArgumentException: Node with id 0:1:1. Failed to parse 0:1:1
>  
> Basically the node's child was deleted and the index of the child list is no 
> longer
> valid. It was valid when the tree was displayed. This gets thrown from
> TreeModel.getNodeById() when an IndexOutOfBoundsException is thrown by the 
> child list.
> This should be handled more gracefully, like by adding a faces context 
> message, "The selected item no longer exists.", and the processing of the 
> rest of the tree nodes should continue. The end user can choose whether or 
> not to show the messages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to