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

Bug with o:validateBean and composite components #342

Closed
ghost opened this Issue Jan 21, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@ghost

ghost commented Jan 21, 2017

Hi Bauke, I've opened pull request #341 which solves a problem with o:validateBean when it's value attribute references a composite component attribute, e.g.:

<o:validateBean value="#{cc.attrs.controller.entity}" .../>

Within the ValidateBean tag handler, the ValueExpression evaluation returns null, then ValidateBean continues down a path as if the value attribute was never specified.

My limited understanding is that UIComponent "visitation" needs to happen in order to resolve #{cc...} expressions.

@ghost ghost changed the title from Bug with o:validateBean and composite compoonents to Bug with o:validateBean and composite components Jan 21, 2017

@BalusC BalusC closed this in 5f3ec34 Jan 21, 2017

@BalusC

This comment has been minimized.

Show comment
Hide comment
@BalusC

BalusC Jan 21, 2017

Member

It's available in today's 2.6-SNAPSHOT. I will extend the ValidateBeanIT on this later.

Member

BalusC commented Jan 21, 2017

It's available in today's 2.6-SNAPSHOT. I will extend the ValidateBeanIT on this later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment