Uploaded image for project: 'MyFaces Core'
  1. MyFaces Core
  2. MYFACES-3010

2.0.3 REGRESSION: javax.faces.component._ClassUtils.convertToType

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.0.3
    • 2.0.4
    • General
    • None

    Description

      Hi guys,

      Thanks again for the great work you do on MyFaces and your fantastic JIRA response times!

      I attach a small app that comes from the Metawidget (http://metawidget.org) distribution. I had you do MYFACES-2935 for me for MyFaces 2.0.3, and my app was working great with the 2.0.3-impl-SNAPSHOT.jar and the 2.0.2-api.jar. However now that 2.0.3 is out for real I have tried to upgrade my app, and it fails. To reproduce, please:

      1. Unzip the attached app and deploy as an exploded WAR into Tomcat
      2. Run Tomcat and hit http://localhost:8080/addressbook-faces2
      3. In the Type dropdown, choose 'Business' and click Search

      You will see an IllegalArgumentException. Now:

      4. Stop Tomcat
      5. Inside the exploded WAR, rename myfaces-api-2.0.2.rename.me to myfaces-api-2.0.2.jar (and delete/rename myfaces-api-2.0.3.jar)
      6. Restart Tomcat and repeat steps 1-3

      This time you will see no such error.

      So something appears to have broken between myfaces-api-2.0.2.jar and myfaces-api-2.0.3.jar? Hopefully you can reproduce this and it is enough for you to debug the issue. The source code for the small app can be viewed here:

      http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/faces/addressbook/
      http://metawidget.svn.sourceforge.net/viewvc/metawidget/trunk/examples/src/java/org/metawidget/example/shared/addressbook/

      Of course, this could well be a case of 2.0.3 being stricter about something and therefore exposing a bug in my code. But my code worked in 2.0.2, JSF 1.2 and JSF 1.1, so hopefully not!

      Regards,

      Richard

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lu4242 Leonardo Uribe
            kennardconsulting Kennard Consulting
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment