2 Replies Latest reply on Mar 27, 2006 8:29 AM by eekboom

    Better error message when component isn't found?!

    eekboom Newbie

      I get a stacktrace that indicates (I think) some misconfiguration with my @In and @Name annotations.
      However I have no indication what name is looked up and why (from what other component).
      Would it be possible to get a better error message here?

      Caused by: java.lang.NullPointerException
      at org.jboss.seam.Component.forName(Component.java:1011)
      at org.jboss.seam.ejb.SeamInterceptor.getSeamComponent(SeamInterceptor.java:61)
      at org.jboss.seam.ejb.SeamInterceptor.aroundInvoke(SeamInterceptor.java:34)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:589)
      at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:120)
      at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:62)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
      at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
      at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
      ... 41 more