11 Replies Latest reply on Oct 12, 2006 10:43 AM by sonja löhr

    Eclipse Getting Started Guide

    sonja löhr Newbie

      Hi!
      Because the sticky thread about the Getting-Started Guide doesn't pop to the front ... Could someone please give me a hint where i am wrong if jboss-seam.jar is not included in the samle.ear / blank.ear after publishing?
      Please see the Getting-Started-Guide thread!

      Thanks a lot!!

        • 2. Re: Eclipse Getting Started Guide
          sonja löhr Newbie

          Hi, Andreas!

          No, it doesn't work for me, since jboss-seam.jar is nowhere in the classpath if it is not included in the sample.ear - now I get the NoClassDefFound Errors for SeamListener and so on.
          May the reason be that Seam itself (and seam-gen inside) on my system is not located inside the workspace and you published it automatically through eclipse?
          Would it be a good idea to put jboss-seam.jar somewhere in /server/default/lib?

          • 3. Re: Eclipse Getting Started Guide
            sonja löhr Newbie

            I now started the n-th trial (I'm quite quick now ;-) with jboss-seam.jar in server/default/lib. "sample" did not work because parse errors with processflow config files, but I got the "blank" app deployed successfully.
            The start page came up, ok. But I had to again add the Module-dependency on jboss-seam.jar (the one you suggested to remove) to get the Seam Component (MySfsb in the example) be resolved properly.

            But I still don't understand why the publishing process does not pick up jboss-seam jar (and jbpm-xxx.jar) into the ear file while it is present in nearly every directory ...

            Since I don't like to be tied to eclipse to build my project anyway, I wonder whether I could feed the "publish" process with a custom buid.xml I may use outside eclipse as well? Unfortunately, seam-gen only packages a build.xml for the "non-wtp"-Structure. Perhaps someone has already done something like that?

            Greets.
            sonja

            • 4. Re: Eclipse Getting Started Guide
              james.williams Novice

               

              "japplicoon" wrote:
              I now started the n-th trial (I'm quite quick now ;-) with jboss-seam.jar in server/default/lib. "sample" did not work because parse errors with processflow config files, but I got the "blank" app deployed successfully.
              The start page came up, ok. But I had to again add the Module-dependency on jboss-seam.jar (the one you suggested to remove) to get the Seam Component (MySfsb in the example) be resolved properly.

              But I still don't understand why the publishing process does not pick up jboss-seam jar (and jbpm-xxx.jar) into the ear file while it is present in nearly every directory ...

              Since I don't like to be tied to eclipse to build my project anyway, I wonder whether I could feed the "publish" process with a custom buid.xml I may use outside eclipse as well? Unfortunately, seam-gen only packages a build.xml for the "non-wtp"-Structure. Perhaps someone has already done something like that?

              Greets.
              sonja


              What version of eclipse are you using? Is it 3.2 with callisto and the exact plugins mentioned in the guide, or is it something else?

              I have not tested seam-gen with JBossIDE 2.0-Beta1 or any other combination of eclipse+plugins yet, so I suspect this is an eclipse wtp quirk. Let me know what you're using and I'll do some digging.

              • 5. Re: Eclipse Getting Started Guide
                sonja löhr Newbie

                Hi!
                It is eclipse 3.2 with all plugins from the tutorial.
                The only difference could be that jboss-seam and seam-gen is not inside my workspace.
                I inspected the build file the publishing process seems to use and copied jboss-seam into nearly every reasonable directory to see when it will be picked up, but it never did ...
                Do you all have jboss-seam.jar in the .ear file?

                • 6. Re: Eclipse Getting Started Guide
                  james.williams Novice

                  seam-gen pulls jboss-seam.jar from its parent directory. So, it should be in the EAR. If it's not, its likely the ant script can't find jboss-seam.jar because you didn't unzip seam-gen.zip into the same folder you extracted "jboss-seam-1.0.1.GA" to. So, a sanity check move would be to make sure that the directory above seam-gen, includes "jboss-seam.jar". Does your directory structure look like this?

                  -jboss-seam-1.0.1.GA
                  -"jboss-seam.jar" and all other files in the root folder for Seam
                  -seam-gen

                  James

                  • 7. Re: Eclipse Getting Started Guide
                    james.williams Novice

                     

                    "james.williams@jboss.com" wrote:
                    I meant to say, does your directory structure look like this?


                    -jboss-seam-1.0.1.GA
                     -"jboss-seam.jar" and all other files in the root folder for Seam
                     -seam-gen
                    


                    • 8. Re: Eclipse Getting Started Guide
                      sonja löhr Newbie

                      You are right, the two jars were somehow missing in the EarContent directory, but if I now create a "new-wtp-project", they get copied to EarContent (and therefore in the ear file). I don't know what I could have changed in the meantime (I slightly customized the files in seam-gen), but it is up and running now!
                      Uff - thank you.

                      • 9. Re: Eclipse Getting Started Guide
                        sonja löhr Newbie

                        But another question on that:
                        I do not really look behind the structure and the build inside eclipse, so has anyone written a build.xml that honors the wtp-project structure?
                        I'm just used to deploy, undeploy, clean, ... in the shell, and such build.xml would also be a great help for me to understand what is going on there in eclipse.

                        • 10. Re: Eclipse Getting Started Guide
                          james.williams Novice

                          No one has written a build script that does deploy/undeploy, etc... for the WTP structure. I was going to do it, but I decided to lobby the JBossIDE guys to include seam-gen in a real eclipse plugin, so that it could be pointy-clicky the right way.

                          Having said that, if you feel there's value in deploy tasks with the WTP structure and you want to script it, I'll add it to seam-gen. If not, I may write it anyway, but it'll be awhile.

                          Good to here you're up and running!

                          James

                          • 11. Re: Eclipse Getting Started Guide
                            sonja löhr Newbie

                             

                            "james.williams@jboss.com" wrote:
                            I was going to do it, but I decided to lobby the JBossIDE guys to include seam-gen in a real eclipse plugin, so that it could be pointy-clicky the right way.

                            Yes, that would be the best way.
                            Is the plugin-version described in the seam-getting-started in the end equivalent to the jbossIDE bundle one can download?


                            "james.williams@jboss.com" wrote:

                            Having said that, if you feel there's value in deploy tasks with the WTP structure and you want to script it, I'll add it to seam-gen. If not, I may write it anyway, but it'll be awhile.

                            Guess I first need a really good tutorial on all that WTP-stuff. Now that I successfully converted my project to the wtp structure, I first have to figure out the cool things I can do with it - hoping to find any ;-)
                            But it would be great if some day you would provide a custom build file!

                            Thank you again and
                            Bye!






                            James