7 Replies Latest reply on Aug 28, 2006 8:05 PM by smokingapipe

    JBoss Seam don´t work.

    ajanoni

      I have been try to put seam examples to work but everthing don´t work.
      I just read the start guide and tryed to deploy example applications in jboss and tomcat, using java 5 and i have no success.

      I lost 2 days trying understand and make it run because i´m working in a new project, but i thing it´s a immature framework and i will have a lot of problems when I put it in production.

        • 1. Re: JBoss Seam don´t work.
          sjmenden

          ajanoni, follow the directions in the following link exactly.

          http://labs.jboss.com/portal/jbossseam/gettingstarted

          Most likely you had the same problems I had at first also, I downloaded the regular installer that is linked from the main jboss.org downloads site. You actually can't use SEAM with this installer, and you need the JEMS installer.

          Hope that helps.

          • 2. Re: JBoss Seam don´t work.
            mzeijen

            I think it is immature to begin ranting about a framework being immature before you even ask help or just read the neccesay documentation. I can't believe it costed you 2 days. You probably didn't look on the forum or on the wiki. I got SEAM running within half an hour.

            I even succeeded to setup an eclipse project structure within 2 hours. This includes hot-deploy and debugging.

            Just because you are frustrated doesn't mean that it is the fault of the software.

            I do agree that the documentation could be a bit better with some stuff that create frequent problems. But just take 5 minutes to look in the forum and you will probably find the solution.

            • 3. Re: JBoss Seam don´t work.

              Even if you have to fight to get it working it is well worth it.

              • 4. Re: JBoss Seam don´t work.
                smokingapipe

                Make no mistake, Seam is HARD to set up. Documentation is lacking. But it is worth it. It is the first truly object-oriented web application system I've ever seen.

                • 5. Re: JBoss Seam don´t work.

                   

                  "SmokingAPipe" wrote:
                  Make no mistake, Seam is HARD to set up. Documentation is lacking. But it is worth it. It is the first truly object-oriented web application system I've ever seen.


                  It is a bit hard if you did not work with JSF and EJB3 before ( like me )
                  When it start working it is nr. 1 :-)

                  ciao Nicola

                  • 6. Re: JBoss Seam don´t work.
                    gringalet

                    you can surf this url if you are a chinese:)

                    http://www.jdon.com/jive/thread.jsp?forum=16&thread=28188&message=19398705&redirect=true&hilite=true&q=booking


                    • 7. Re: JBoss Seam don´t work.
                      smokingapipe

                       

                      "nicola9000" wrote:
                      It is a bit hard if you did not work with JSF and EJB3 before ( like me )
                      When it start working it is nr. 1 :-)


                      Right, exactly. I had never used JSF or EJB3 before. I have used Hibernate and I really liked it, and EJB3 is very similar to Hibernate in concept (and uses a lot of Hibernate code).

                      What I didn't like about Hibernate was the Session management stuff. The only good way to do it in Hibernate is to have the Session controlled by a filter so entities could stay attached as the page renders. And there were other problems. EJB3 + Seam solves all that, and also adds a ton of other cool features. It's just non-trivial to get it set up.

                      What would be great would be a stand-alone application framework file set, that has everything ready to go. All the examples that come with Seam have build.xml files with stuff like include="../../build.xml", which makes them pretty hard to use in a new project.

                      I'm trying to put together a generic app framework that has all the stuff I need, plus login and authorization filters, and the Tomahawk components, and it's stand-alone ready to build. That would be a tremendous help in getting people started on it.