7 Replies Latest reply on Apr 9, 2006 2:00 PM by mirko27

    Report: CVS Version of Seam

    mirko27

      Well, I must say that nothing works. Entitymanager (@PersistenceContext and Seam`s own) does not get loaded. I mean there is component but it`s not injectable. In the end I got exceptions related to portlets(I do not use one).

      Downloaded old seam from jboss page and everything works perfectly.
      So as you can see Seam did instead increase development time :D
      Anyway, hope that this helps and problems get solved. (Gavin please keep stable version of seem in CVS also)

        • 1. Re: Report: CVS Version of Seam
          mirko27

          This old seam jar has downcomes...
          No Faces support. Some transaction exceptions...
          It`s driving me nuts. Last two weeks I have been solving mysterious exceptions instead of coding (or scripting because it`s very easy).

          Gavin can you upload something for me? something stable that just works...

          • 2. Re: Report: CVS Version of Seam
            mirko27

            By no faces support i ment facesmessages. FacesContext does not have method addmessages.

            • 3. Re: Report: CVS Version of Seam
              sunfire

              Hi mirko27,

              can you please be a little more specific about what does not work, maybe provide specifc cases/traces and maybe provide some information about the version you are useing (myfaces, facelets, ejb3, jboss).
              Since I am also useing a quite recent CVS version and everything works for me, well I don't use Seam managed EntityManager but CMP works.
              @PersistenceContext is not a Seam annotation but EJB3 and Seam has little toto with it - so maybe check your EJB3 environment. If you are useing Jboss CR2 with the CVS ejb3 tag it won't work since Gavin is useing the standalone EJB3 releases which has not been released yet.
              For the portlet exception I'd say this is due to the few last CVS commits wich introduced some portlet changes. Try to include the portlet-api-lib.jar into your classpath and the exception should go away. I also had the portlet exception when my SFSB got passivated and it went away after I resolved the indirect reference to the portlet api.

              Hope it helps, Thorsten

              • 4. Re: Report: CVS Version of Seam
                sunfire

                btw: if you want to use the facesmessages change your import from org.jboss.seam.core.FacesContext to javax.faces.context.FacesContext. This way it works for me just fine.

                • 5. Re: Report: CVS Version of Seam
                  mirko27

                  Yeah, I did get it work. I have no time(deadline) for testing this portlet and so on stuff, but I did find (from harddrive) working version of latest jboss-seam.
                  Could you help me out with this SelectManycheckbox issue? This would be lovely.


                  Thanks for helping.

                  • 6. Re: Report: CVS Version of Seam
                    gavin.king

                    Fixed now.

                    You know you can use CVS to checkout a snapshot from any date/time, right?

                    • 7. Re: Report: CVS Version of Seam
                      mirko27

                      Didn`t know actually. Thanks. Did you get my e-mail Gavin? And please look at that JTA Transaction thread that I posted.