Hi Again Volker, Sorry for the delay, something not very explainable (to me) happened:
I was trying to make the exception more verbose about: on wich path it occurs etc.. so I copied the source of ValueBindingImpl to my project and added some text to the exception: Surprisingly, my systematically reproduceable bug stopped to occur. I've searched for other occurences of ValueBindingImpl in my classpath and there wasn't any, other than the one in the jar. The only explanations that remain to me are that the class compiled in the jar was maybe compiled with a different compiler, wich may result in secondary effects (but I've never seen sth like this problem) The other explanation is even more absurd: class loaders are different (in the jar and in the app), but to my knowledge, this can cause differences in finding a class and it has no effect on finding fields of a detected class (even though Adress.class was not found, I don't think the NoClassDefFound was catched and base set to *null*). So I only confirm this exception is really strange. The first reaction should maybe be to compile ValueBindingImpl in the project as I did and see what happens next. Regards, Zied 2007/6/19, Volker Weber <[EMAIL PROTECTED]>:
Hi Zied, > adress is infact a declared managed bean in faces config (at a moment I > thougth there is a conflict with a request attribute with the same name, but > the code is now working so the problem isn't there). This could be the problem. If the value of the request attribute is null this may be the reason. If there is a request attribute 'adress' there is no further lookup in session or application scope, even when the value is null (afaik). Regards, Volker
-- Zied Hamdi zatreex.sourceforge.net
