b:message doesn't support composite components

[NicolaIsotta]

If a have a composite component with an implementation like this:

<cc:implementation>
	<b:inputText id="input" value="#{cc.attrs.value}" .../>
</cc:implementation>

And I add a message for the input element in a page:

<ezcomp:myinput id="field1" .../>
<b:message for="field1:input"/>

I get this exception:

javax.faces.FacesException: Invalid search expression: field1:input The subexpression input doesn't exist, or it can't be resolved.

h:message works instead.

[stephanrauh]

Looks like a difficult one!

[stephanrauh]

For some reason unknown, b:message only checked its children and the root component for field1:input. Now I've added a bit more flexibility. b:message now also checks it's parent. In my test case, that's the form. Hope that works for you, too!

I've uploaded the new snapshot of BootsFaces to Maven Central. As usual, see #369 on how to get it.

[stephanrauh]

I'll close this issue so we can include it into the 1.0.2 version.

[NicolaIsotta]

It's working in the snapshot version.

[stephanrauh]

THX! We're currently preparing the 1.0.2 version, so I'm very glad you reported back in time.