11 Replies Latest reply on Mar 25, 2008 8:37 PM by max.max.andersen.jboss.com

    Jboss tools or not Jboss tools

    anb1

      Is it safe to use Jboss tools to work with seam or should we stick to seam-gen ? They seem to be incompatible and I am under the impression that jboss tools is not up to date with seam.


      What is the best practice ? What works best ?

        • 1. Re: Jboss tools or not Jboss tools
          nickarls

          Incompatible in what way? Works fine with the latest production seam (2.0.1.GA) for me.

          • 2. Re: Jboss tools or not Jboss tools
            gavin.king

            JBoss Tools is definitely up to date with Seam; indeed it directly uses the seam-gen templates from your Seam dist. If you are developing in Eclipse, JBoss Tools is definitely the way to go.

            • 3. Re: Jboss tools or not Jboss tools
              samdoyle

              Gavin King wrote on Mar 11, 2008 04:08 AM:


              JBoss Tools is definitely up to date with Seam; indeed it directly uses the seam-gen templates from your Seam dist. If you are developing in Eclipse, JBoss Tools is definitely the way to go.


              If us NetBeans users could get something similar it would be great. Unfortunately it doesn't look like if it will be anytime soon if ever.

              • 4. Re: Jboss tools or not Jboss tools
                samdoyle

                Also JBoss Tools still doesn't work properly with GlassFish.

                • 5. Re: Jboss tools or not Jboss tools
                  anb1

                  Alright, thanks.


                  I got a bit mislead because each time I tried to create a new project deployment reported some errors ... but that might be just my configuration.

                  • 6. Re: Jboss tools or not Jboss tools
                    anb1

                    And what about using jboss tools with seam 2.1.0.A1 ? Is it possible ? I tried to install the tools nightly but again a fresh project just doesn't work (but now I can understand, both being unstable releases).


                    It is complaining about Could not instantiate  org.jboss.seam.security.identity ...

                    • 7. Re: Jboss tools or not Jboss tools
                      trouby

                      Seems like Seam's security module is under heavy modifications and developers probably don't have enough time to make a stable version in trunk on daily basis,



                      You better use more stable version of Seam if you don't want to get to these troubles,



                      Tools works fine with stable Seam 2.1 ver.


                      Asaf.

                      • 8. Re: Jboss tools or not Jboss tools
                        pmuir

                        Karl Robertson wrote on Mar 11, 2008 10:31 AM:


                        And what about using jboss tools with seam 2.1.0.A1 ? Is it possible ? I tried to install the tools nightly but again a fresh project just doesn't work (but now I can understand, both being unstable releases).



                        It does work, but you just can't create a project (JBIDE-1786). So, create a project using Seam 2.0 runtime and replace the JARS.

                        • 9. Re: Jboss tools or not Jboss tools
                          dengyin2000

                          If I create a ear Seam project using JBoss tool. The Seam project has errors. and I look the deploy folder, the layout of that project is not correct.

                          • 10. Re: Jboss tools or not Jboss tools
                            alartin

                            See this post:http://www.seamframework.org/Community/SeamgenNetbeansPlugin
                            . It is the only way for netbeans user so far.

                            • 11. Re: Jboss tools or not Jboss tools
                              max.max.andersen.jboss.com

                              deng yin wrote on Mar 18, 2008 03:38 AM:


                              If I create a ear Seam project using JBoss tool. The Seam project has errors. and I look the deploy folder, the layout of that project is not correct.


                              What do you mean ? More details please.


                              Any chance you are using WTP 2.0.2 and not WTP 2.0.1 ? WTP 2.0.2 introduced a bug in their ear deployment.