7 Replies Latest reply on Mar 22, 2006 4:43 PM by Gavin King

    Troubleshooting exceptions due to bad annotations

    Andrew Apprentice

      I have a bug that is resulting in:

      SEVERE: Error Rendering View[/conference/index.xhtml]
      java.lang.IllegalArgumentException: create method not found
       at org.jboss.seam.Component.callComponentMethod(Component.java:1127)
       at org.jboss.seam.Component.callCreateMethod(Component.java:1107)
       at org.jboss.seam.Component.newInstance(Component.java:1096)
       at org.jboss.seam.Component.getInstance(Component.java:1044)
       at org.jboss.seam.Component.getInstance(Component.java:1027)
       at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:43)
       at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:134)
       at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
      Caused by: java.lang.NoSuchMethodException: $Proxy202.begin()
       at java.lang.Class.getMethod(Class.java:1581)
       at org.jboss.seam.Component.callComponentMethod(Component.java:1116)
       ... 54 more

      Is there any "easy" way of trying to determine what I screwed up? I wrote several classes without testing then just slapped a page view on these beans, so it isn't easy to tell which session bean I have a bug in.

      The most helpful part seems to be the caused by section, but the "$Proxy202" isn't helpful at all.

      Any ideas on how to track this down?