Closed raelianer closed 9 years ago
Oleg, WDYT? I would close it, our showcase is designed with the configs in our web.xml. I would not change it to work in cases when the user changes our web.xml.
I can not imagine that client side validation leads to PropertyNotFoundException
. By the way, AFAIK, primefaces.CLIENT_SIDE_VALIDATION
is not set in our showcase too .
Please check your log file. It probably have other exceptions. Thomas, I would close this issue too.
The showcase runs until I change the setting, so I think it has something to do with this issue. As I wanted to use the primefaces extensions with spring security and other things, I had to find out if it works. Therefore I used the showcase examples. I just wanted to let you know about this behaviour. Maybe you wanna add a line to the showcase to tell users that they should not change the setting. I don't even know if it's a showcase problem or a problem of the component. I'm not expecting anything, just thought maybe you wanted to know about this.
I can look into this later if I have time. Thanks for reporting.
Will check this before we release the next version 3.1.0. Timeline should work of course, independent from primefaces.CLIENT_SIDE_VALIDATION setting.
Hmm.. That's true. It is due to p:inputText. It works with non PF components, e.g. h:inputText.
I have to look deeper into this. Thomas, do you have an idea?
sure. CSV needs to resolve the annotations on the referenced ValueExpression. If a variable resolves to null in the whole expression, it's not readable. Currently thats by design in PF - a solution would be to catch the NPE but CSV wouldn't work for this field as we can't extract the constraints... So, whats better? ;)
Understood. Would it solve the problem if we use rendered on the input field to check if some objects are null?
Also checking constraints is only important for BV. So PF could catch NPE if no BV is used.
Thats how it's done. But the stacktrace is from a different point. It's done for BV and !=BV to lookup the converter.
I added to all input components
rendered="#{not empty editServerTimelineController.event}"
in detailsDialog.xhtml and the problem was gone. You can do the same in the future when you have primefaces.CLIENT_SIDE_VALIDATION = true.
Just wanted to note that
leads to this error when trying to open the website of the showcase:
(primefaces extensions 3.0.0 - showcase revision b9054309cc)
Update: my bad - setting to true not to false leads to the error
full stack traces: