7 Replies Latest reply on Dec 8, 2006 8:20 AM by Sean Radford

    Seam 1.1 CR1, IceFaces & Tomahawk...

    Marcin buojk Newbie

      Is this posible to use together Seam 1.1 CR1, IceFaces and Tomohawk components together?

      What about tomahawk filter implemented in web.xml U say?
      If that is posible, can U tell me how to implement Tomahawk together seam->IceFaces?

        • 1. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
          None None Master

          I have Seam working nicely with Tomahawk. I'm using Seam 1.1 and Tomahawk 1.1.5 snapshot, and also Tomahawk Sandbox 1.1.5 snapshot. It's cool! There are some bugs but it is working.

          I was going to also add Icefaces to the mix but I thought that would be asking for a mess. At some point I'll try it because IF looks so cool, but not yet.

          • 2. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
            None None Master

            I have a question on this: I tried to use Tomahawk with Seam with Tomahawk 1.1.0 (?) and it did work, but conversations didn't work, because Tomahawk's components didn't maintain the conversation ID. I didn't really need conversations in the app I was working on so I just made everything Session scoped. That is not ideal and isn't really the Seam Way.

            With this new version of Tomahawk and Seam, will conversations work?

            • 3. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
              Gavin King Master

               

              I tried to use Tomahawk with Seam with Tomahawk 1.1.0 (?) and it did work, but conversations didn't work


              ie. it didn't work

              because Tomahawk's components didn't maintain the conversation ID


              Don't use Tomahawk. How many times do I have to say it? This stuff is just broken.

              I didn't really need conversations in the app I was working on so I just made everything Session scoped.


              In another thread you are complaining that Seam is broken because you get LIEs. Has it occurred to you that you are getting LIEs because you decided to use session scope for everything instead of conversations?

              With this new version of Tomahawk and Seam, will conversations work?


              I am absolutely not going to waste time trying to get that broken crap to work. There are much better JSF component libraries out there, which are *not* so broken and fragile.

              • 4. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
                None None Master

                Ah, well, thank you. That's quite a decisive answer. Now it's time for me to:

                grep t: *.jsp


                and

                rm tomahawk.jar


                Fortunately at this stage of my app that won't be a big deal. Later I'll add the Icefaces components, if you think those are a good fit with Seam. They sure look good.


                • 5. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
                  jk;l jkl; Expert

                   

                  "gavin.king@jboss.com" wrote:
                  Don't use Tomahawk. How many times do I have to say it? This stuff is just broken.

                  ...

                  I am absolutely not going to waste time trying to get that broken crap to work. There are much better JSF component libraries out there, which are *not* so broken and fragile.


                  Thanks for pointing out that Tomahawk is not the ideal option to use...I was going to start using it soon enough were it not for this warning.

                  What are the better JSF component libraries out there? Could you please name the ones you recommend in terms of their reliability, as well as their fit with JBoss/Seam?

                  Thanks.

                  • 6. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
                    Pete Muir Master

                    Trinidad, Icefaces both come up regularly as good (os) component sets.

                    • 7. Re: Seam 1.1 CR1, IceFaces & Tomahawk...
                      Sean Radford Novice

                      I couldn't get IceFaces to work acroos redirects that I was using as part of my jBPM page flows though.

                      Regards.