[jira] Updated: (TRINIDAD-1499) Regression issues with jsp tag class generation from move to jsr276 metadata

["Bill Baggett (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/TRINIDAD-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Baggett updated TRINIDAD-1499:
-----------------------------------

    Status: Patch Available  (was: Open)

> Regression issues with jsp tag class generation from move to jsr276 metadata
> ----------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1499
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1499
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.2.10-plugins 
>            Reporter: Bill Baggett
>
> In the move to the new jsr-276 metadata we missed a couple things with the generation of the jsp tag classes.
> First, we needed to check for the deprecated metadata element in the new structure because this is used in the jsp tag class generation.
> Second, the move from <mfp:literal-only>true</mfp:literal-only> to <fmd:value-expression>PROHIBITED</fmd:value-expression> wasn't handled in all cases.  I had previously made a fix that checked for either the old way or the new way.  The problem is that there were a couple places that I missed (ie jsp tag class generation).  Instead of making a check for the old way and the new way in each place, I decided to put the fix at a lower level.  There were 2 parts to this.  First, undo the check I had made for the old way and the new way.  Second, in the digester bean handler for the new way, I just set the property corresponding to the old way.  That makes it transparent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.