-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
b:inputText null object not working till 3rd level #851
Comments
BootsFaces tries to read the JSF303 annotations. That's only possible if the field is not null. Do you really need it to be null? |
Thanks for the information, that makes sense. So no bug but a feature? |
I wouldn't call the bug a feature, but it's caused by a feature. Until now, we got away with it. If more people vote for avoiding the NPE, we'd certainly do so. |
If EL can handle this, I think we should try to mimic it. I haven't read
the EL spec thorougly but I think it specifically says it ignores those
null pointer exceptions. So people might righfulu rely on it.
I'd vote for fixing it too.
El mié., 30 de agosto de 2017 20:04, Stephan Rauh <notifications@github.com>
escribió:
… I wouldn't call the bug a feature, but it's caused by a feature. Until
now, we got away with it. If more people vote for avoiding the NPE, we'd
certainly do so.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#851 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACAucIIKnxMebQHZ4DK4jJAVkCCtK65Uks5sdaQ7gaJpZM4PFipu>
.
|
Great @stephanrauh thanks! |
Hi,
please see the following example:
The "terminologyToEdit" is null.
With h:inputText it is working fine. It also works if I remove the last field, but sure, that is not what I need:
But it seems to be dependent on the level of accessing fields.
The following exception is thrown:
Regards,
Tobias
The text was updated successfully, but these errors were encountered: