[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4780) IllegalArgumentException: No enum const PropagationType.xxxx

Flavio Costa (JIRA) jira-events at lists.jboss.org
Wed Feb 16 09:51:14 EST 2011


    [ https://issues.jboss.org/browse/JBSEAM-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582653#comment-12582653 ] 

Flavio Costa commented on JBSEAM-4780:
--------------------------------------

That's true, this bug does not affect 2.2.1.Final.
The bug that actually does is this one: JBSEAM-4755 which eventually made me try to use a snapshot of Seam and discovering the bug introduced in JBSEAM-4774

> IllegalArgumentException: No enum const PropagationType.xxxx
> ------------------------------------------------------------
>
>                 Key: JBSEAM-4780
>                 URL: https://issues.jboss.org/browse/JBSEAM-4780
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>         Environment: Java 6u23
> JBoss 4.2.3.GA
> Linux
>            Reporter: Flavio Costa
>            Assignee: Marek Novotny
>            Priority: Blocker
>              Labels: Enum, PropagationType, nest, nested
>             Fix For: 2.3.0.ALPHA
>
>         Attachments: patch_propagtion_type.diff
>
>
> After fixing JBSEAM-4774 a new bug was introduced.
> If a user types *propagation="nested"* instead of *propagation="NESTED"* an exception like this is thrown: _IllegalArgumentException: No enum const PropagationType.nested_
> That's a show stopper, since the documentation, the examples and the community are already used to using the lowercase "version".
> The fix is simple, I'm attaching a patch.
> Again, that will break many apps and bring 2.2.1.Final adoption to a stop.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list