13 Replies Latest reply on May 7, 2008 5:51 PM by rob.stryker

    Do the JBoss Tools for SEAM work?

      I've created a SEAM project as specified by:

      http://docs.jboss.org/tools/2.0.0.GA/seam/en/html/create_new_seam.html

      However, whenever I attempt to run or build a module, this:

      "default,all,minimal,other - type your own here"

      is in the deploy path. I've verified the server and runtime in preferences, as well as console output...they're both looking in the right spot. The project is just not deploying in the right spot, the "default,all,minimal,other - type your own here" folder is being created and deployed to.

        • 1. Re: Do the JBoss Tools for SEAM work?
          maxandersen

          Where do you get that weird folder from ?

          I don't see that referenced anywhere in the docs...

          • 2. Re: Do the JBoss Tools for SEAM work?

            I don't know where it is coming from, but it's being created. I've re-installed Eclipse and JBoss Tools several times... same result. I am running OS-X 10.5

            • 3. Re: Do the JBoss Tools for SEAM work?
              maxandersen

              I just searched for the phrase "type your own here" in all of jboss tools sourcecode and it is nowhere to be found.

              I don't think you are using JBoss Tools....our AS adapter (the one under JBoss, a division of Red Hat) does not create "random" deploy folders like this unless the user typed in this exact phrase (which I doubt)

              • 4. Re: Do the JBoss Tools for SEAM work?

                I am pretty certain I am using JBoss tools :) Search the Eclipse directory.

                • 5. Re: Do the JBoss Tools for SEAM work?
                  maxandersen

                  search which eclipse directory ?

                  I'm telling you that snippet is not in jbosstools code.

                  It might be inside eclipse but then im pretty sure you are using wtp's generic jboss adapter and not ours..

                  • 6. Re: Do the JBoss Tools for SEAM work?

                    I'm using the JBoss adapter, as specified in the document. 'JBoss, a division of RedHat'/'JBoss AS 4.2'.

                    When I do a 'Publish' or 'Clean..' under 'JBoss Server View', 2 things occur:

                    1) 'default,all,minimal,other - type your own here' directory, at the same level as /server in the AS, is created. It has contains an empty 'deploy' subdirectory.

                    2) 15:38:38,772 ERROR [MainDeployer] Could not initialise deployment: file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/
                    org.jboss.deployment.DeploymentException: url file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/jboss-seam.jar could not be opened, does it exist?

                    • 7. Re: Do the JBoss Tools for SEAM work?
                      rob.stryker

                      You'll need to provide a screenshot of your server view. I simply do not believe you are using our server adapter because when creating a JBoss server, it does not allow you to provide your own configuration.

                      If your server installation folder has a default, minimum, and all configuration, It will list the three in a list viewer. Our server does not at any point allow you to "type your own', nor, as max said, is that string anywhere in our source code.

                      • 8. Re: Do the JBoss Tools for SEAM work?

                        I've completely removed JBoss AS, SEAM, JBoss Tools, etc.. etc.. and performed a clean install. Whatever was causing that issue disappeared.

                        I've new configured Ajax, XDocs, and Seam (2.0.1.GA) home. I create a new new project using the wizard, selecting "Seam 2.0 technology preview". When I publish I get:

                        "ERROR [MainDeployer] Could not initialise deployment: file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/
                        org.jboss.deployment.DeploymentException: url file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/jboss-seam.jar"

                        After manually copying the required JARs to the deployment directory (which is a problem?) I get:

                        "ERROR [[/HelloWorld]] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
                        java.lang.ExceptionInInitializerError"

                        • 9. Re: Do the JBoss Tools for SEAM work?

                          Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.

                          • 10. Re: Do the JBoss Tools for SEAM work?
                            rob.stryker

                            It sounds like you're using wtp 2.0.2, which has known incompatibilities with our last release.

                            Even in our current / upcoming release, we've had to provide a patched version of wtp because of it's errors.

                            • 11. Re: Do the JBoss Tools for SEAM work?
                              wiggy

                              hokay -

                              not entirely sure what you have going here - but i see in the error something i have experienced in windows.

                              Sometimes if you build a new seam project usingt the wizard (do a simple helloo world ear app) and have a look in the eclipse project earContent directory you will find a bunch of jar files that the builder puts there.

                              bizarely I find that when you deploy the ear (it deploys in exploded format if you use the jboss tools install ontop of eclipse) - it copies the ear structure into the jboss/server/default/deploy directory in exploded format (assumes you have accepted all the standard defaults when defining your jboss server and seam runtime config for the project when you first went thru the wizard.

                              however what i often find is that the jar files in your top level EarContent directory do Not get deployed to the server. Cant figure out why this does this. one of these jars in the jboss-seam.jar that your trace moans about.

                              If you then manually copy the jar files in explorer to the same place in the deploy directory - then the deployer detects the paste and it normally then successfuly deploys - at least it does for me.

                              however i've had another problem - where an app i have built has stopped copying the application.xml in the META-INF directory for the ear - and i have no easy past this - cant figure out why it doesnt deploy - its in the source folder in eclipse project.


                              as for your note



                              Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.



                              this is usually found in the commons-logging.jar which for me in the the server/defualt/lib directory. This is usually resolved at compile time by ensuring your server runtime libraries are added to the project in the eclipse build. - if you open the runtime library list in the package explorer (Left hand side) in eclipse.

                              check you have the right runtime library set configured for your eclipse project and check your default/deploy/lib directory has the commons-logging jar there.

                              i have not had a problem with logging myself



                              • 12. Re: Do the JBoss Tools for SEAM work?
                                wiggy

                                Rob - please expand on the wtp 2.02 problems with jboss tools -

                                i am having problems with deploy action to server in eclipse 3.3.2 and wtp 2.02 and jboss tools 2.01.

                                essentially my i have an application that used to work and deploy and now i deploy the application.xml doesnt get copied into the ear META-INF directory though its in the eclipse project file list.

                                I have a simple hello world app that deos deploy though - cant figure.

                                however quite often if i clean out the deploy directory - and intall on the server the seam jars in the top level ear EarContent directory dont get deployed - i have to do it by hand - very frustrating

                                • 13. Re: Do the JBoss Tools for SEAM work?
                                  rob.stryker

                                  We've recently (today) released jboss tools 2.1.0, which is targeted to wtp 2.0.2.

                                  However... we've had to patch wtp2.0.2 as it did not provide the functionality we required.

                                  Basically, when deciding whether or not to publish a .jar file in the EAR project, wtp tries to open it up and see what type of jar it is. However... if you told it jboss-seam.jar was an ejb, it would crap out while looking for an ejb-jar.xml file.

                                  Now, *I* know, and *you* know, that in jee5, these descriptors are not necessary. However wtp 2.0.2 does not seem to understand this, and instead just shits all over itself and refuses to even recognize the file as a library (for certain purposes).

                                  wtp came out with some patches at their patch site, which *still* didn't fix the problem. Rather than try to wait for them to fix it and roll us another build, we made our own patch zip. It's located at: http://repository.jboss.org/eclipse/webtools/patches/wtp-P-P20080506003122-20080506003122.zip

                                  However, since we've now just today released jboss tools 2.1.0, I suggest downloading that instead of just the patch ;)

                                  Good luck!

                                  relevent jiras: http://jira.jboss.com/jira/browse/JBIDE-1862
                                  several eclipse bugs linked there as well ;)