1 2 Previous Next 21 Replies Latest reply on Jun 24, 2009 9:32 AM by ssilvert Go to original post
      • 15. Re: Seam Conversations and JSFUnit.
        djn
        djn May 4, 2009 8:09 AM (in response to djn)

        Just a quick update.

        The new snapshot does not solve the issue I encountered here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=152468

        I thought my sample app reproduced that case, but apparently not, since all tests in that app now pass.

        I will try to look into why this is the case.

        Regards,
        ./Daniel

          • Actions
        • 16. Re: Seam Conversations and JSFUnit.
          ssilvert
          ssilvert May 4, 2009 8:28 AM (in response to djn)

          OK. If you can update your sample app to reproduce the problem then I'll look at it right away.

          Regards,

          Stan

            • Actions
          • 17. Re: Seam Conversations and JSFUnit.
            djn
            djn Jun 22, 2009 5:21 AM (in response to djn)

            Hi again.

            I haven't forgotten about this issue, I've just been really busy. Updating the sample app was not as easy as I had hoped, but now I have something that demonstrates the issues I'm having with JSFUnit.

            Are you still interested in investigating this issue?

            Regards,
            ./Daniel

              • Actions
            • 18. Re: Seam Conversations and JSFUnit.
              ssilvert
              ssilvert Jun 22, 2009 9:13 AM (in response to djn)

              Certainly. Please send me your app to reproduce.

              Thanks,

              Stan

                • Actions
              • 19. Re: Seam Conversations and JSFUnit.
                ssilvert
                ssilvert Jun 23, 2009 4:05 PM (in response to djn)

                I figured out what is happening. I'm gathering all the client ID's and I call UIData.getRowCount(). A4J's UIDataAdaptor tries to make an EL call to get that information and it ends up trying to create a bunch of Seam entities that can't be created while the test thread is running.

                So I've changed the code to ignore the error and go on, which is fine in this case. That gets us past the errors your were seeing.

                So now I can run your tests and I get this:

                javax.naming.NameNotFoundException: EntityLoaderEJB not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.blipsystems.blipzones.util.EntityLoader.getEntityLoaderLocalEJB(EntityLoader.java:32)
at com.blipsystems.blipzones.jsfunit.report.ReportEditTest.testNewReportRendered(ReportEditTest.java:58)


                I think this is a problem in your test or it is something you can work around.

                I've uploaded a new snapshot for you to try out. Please let me know how it goes.

                Stan

                  • Actions
                • 20. Re: Seam Conversations and JSFUnit.
                  djn
                  djn Jun 24, 2009 9:09 AM (in response to djn)

                  Hi.

                  I've just tried the new snapshot and indeed, ignoring the error makes my testcases pass. Thank you for the fix. If I bump into other issues, I will let you know :-)

                  The exception you are seeing is a leftover from when I tried to reproduce the issue in the sample application.

                  Regards,
                  ./Daniel

                    • Actions
                  • 21. Re: Seam Conversations and JSFUnit.
                    ssilvert
                    ssilvert Jun 24, 2009 9:32 AM (in response to djn)

                    That's good. The fix has been committed.

                    https://jira.jboss.org/jira/browse/JSFUNIT-215

                      • Actions
                    1 2 Previous Next