Ids Braam wrote:
> >>it, rather then devicing work-arounds.
> >
> >  <mm:node number="asfd" notfound="skip">
> >     Should be skipped
> >  </mm:node>
> >
> >Did work as expected, in my MMBase. So I don't know what you mean.
> >
> 
> Here it did generate an exception. And then it didn't execute the body. So 
> the notfound did work, but the number attribute generated an exception 
> even when I used the notfound attribute. But odd that it didn't do this 
> there, must be something else. Thanks.
> 
> One thing could be the problem, the number attribute that is refferd to 
> was just deleted. I just tried this, and the wierd thing is, if you 
> removed the node (using <mm:deletenode/>) and then you try to get the node 
> jou just deleted it generates an exception. When the node wasn't deleted 
> earlier in the session it doesn't generate this exception, it could be 
> that this is because tomcat caches to much. A restart of tomcat fixes the 
> problem. But that's not really an solution (restarting tomcat every time 
> we remove a node ;) ). Don't know what causes the problem at the moment, 
> tomcat or MMBase. If I find out I'll let you know.


That at least would be a bug which I would believe to exists. 


Michiel


-- 
Michiel Meeuwissen                  mihxil'
Mediacentrum 140 H'sum                [] ()
+31 (0)35 6772979         nl_NL eo_XX en_US



_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to