5 Replies Latest reply on Jan 27, 2009 4:59 AM by estevaofreitas

    Support for Tomcat & Jetty

    thejavafreak

      Will there be an easy way to deploy WebBeans apps to servlet container like Tomcat and Jetty? It seems that deploying to JBoss itself requires a helluva libraries to be installed in the server classpath.


      Thanks

        • 1. Re: Support for Tomcat & Jetty
          gavin.king

          According to the spec, Web Beans is defined only for EE environments including:



          • full EE implementations

          • EE 6 Web Profile implementations

          • embeddable EJB Lite containers



          The spec doesn't say anything at all about supporting non-EE environments like Tomcat/Jetty. I do not know if the Tomcat/Jetty teams have plans to support the EE 6 Web Profile in future, but certainly there will be plenty of Web Profile implementations around for people to choose from if they want a small-footprint server.


          Now, in theory someone could go ahead and integrate the Web Beans RI with Tomcat or Jetty, which would probably not even be very hard to do, but this would not count as an official Web Beans implementation according to the spec.


          Personally, I don't know why anyone would want to do this, since an EE Web Profile implementation is simply a much better environment to work in than a simple Servlet engine.

          • 2. Re: Support for Tomcat & Jetty
            graben

            Personally, I don't know why anyone would want to do this, since an EE Web Profile implementation is simply a much better environment to work in than a simple Servlet engine.

            I think there are reasonable arguments to support servlet servers like Tomcat or Jetty. There many people outside writing simple webapps on top of Tomcat and co with frameworks like seam or spring. They does not need the whole range the spec does provide since they mostly do not base on EJB or other EE Resources. And since webbeans is related to seam and seam runs on Tomcat why shouldn't webbeans do either? Or is seam3 planned to cut Tomcat support?

            • 3. Re: Support for Tomcat & Jetty
              thejavafreak

              Benjamin Graf wrote on Jan 01, 2009 10:20:


              Personally, I don't know why anyone would want to do this, since an EE Web Profile implementation is simply a much better environment to work in than a simple Servlet engine.

              I think there are reasonable arguments to support servlet servers like Tomcat or Jetty. There many people outside writing simple webapps on top of Tomcat and co with frameworks like seam or spring. They does not need the whole range the spec does provide since they mostly do not base on EJB or other EE Resources. And since webbeans is related to seam and seam runs on Tomcat why shouldn't webbeans do either? Or is seam3 planned to cut Tomcat support?


              But even Seam is highly dependant to embeddable jboss and it's only workable on Tomcat.

              • 4. Re: Support for Tomcat & Jetty
                pmuir

                Joshua Partogi wrote on Jan 08, 2009 02:30:



                Benjamin Graf wrote on Jan 01, 2009 10:20:


                Personally, I don't know why anyone would want to do this, since an EE Web Profile implementation is simply a much better environment to work in than a simple Servlet engine.

                I think there are reasonable arguments to support servlet servers like Tomcat or Jetty. There many people outside writing simple webapps on top of Tomcat and co with frameworks like seam or spring. They does not need the whole range the spec does provide since they mostly do not base on EJB or other EE Resources. And since webbeans is related to seam and seam runs on Tomcat why shouldn't webbeans do either? Or is seam3 planned to cut Tomcat support?


                But even Seam is highly dependant to embeddable jboss and it's only workable on Tomcat.


                No, Seam runs without embeddable jboss in Tomcat.

                • 5. Re: Support for Tomcat & Jetty
                  estevaofreitas
                  First of all, I wanna thanks all the Seam's developers, you guys are doing a fantastic work.

                  I'm working now in two different projects, at both I use Seam + Hibernate + JSF + Tomcat, and this combination had interested many others programmers I work because it's clean, have a small memory footprint and it's very easy find a good and cheap hosting service to deploy the application. In addition, if I need just to build a simple Content Manager System to a very simple web site, so I'll have to learn and to use the EJB specs?

                  For me it's like kill a fly with a cannon.

                  P.S. I hope you forgive my english.