[MYFACES-4028] Custom Taglib with composite components and JSTL

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 2.1.17, 2.2.9
• Assignee: Leonardo Uribe
• Reporter: Christian Beikov
• Created: 28/Jan/16 13:46
• Updated: 18/Feb/16 08:52
• Resolved: 15/Feb/16 23:37

Description

I tested this on Wildfly 10.0.0.CR5 with both, MyFaces 2.1.17 and 2.2.9 but I suppose this issue is not specific to my environment.
The example project can be found on Github: https://github.com/beikov/myfaces-composite-jstl-issue

I think the essential problem is, that a composite component passes an EL expression to a custom tag which then uses the expression in a JSTL Tag.
I don't know if it's just illegal to do something like this, or if there is an actual bug, but if it is the former, I'd expect an exception.

Depending on whether the property "org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS_PRESERVE_STATE" is enabled the behavior is different.

When enabled, the converter that is attached to the composite component will be considered for state saving which in this case leads to a converter without state when restoring and finally leading to a converter exception on postback.

When disabled, the first postback request just seems to do nothing, but then, it seemingly works as expected.

Issue Links

• is related to: MYFACES-3883 c:forEach with PSS enabled fails when add multiple rows
• is related to: MYFACES-4026 Composite Component cc.clientId not usable in custom tag