7 Replies Latest reply on Oct 29, 2002 10:03 AM by Greg Turner

    Jboss is so hard to use and i am thinking choose another App

    qfjiang Newbie

      is JBoss so week, it can't match Weblogic and other server,the document is so lesss,i finding i made the wrong decision,..........
      my god, let jboss die!

        • 1. Re: Jboss is so hard to use and i am thinking choose another
          Juha Lindfors Master

          well what do you expect from a product that was built with communist ideals?

          • 2. Re: Jboss is so hard to use and i am thinking choose another
            prabhakar chaganti Apprentice

            It is also an opensource project that encourages your participation unlike the other ones you mention. It is certainly challenging to learn, but will be well worth your time !!!

            -prabhakar

            • 3. Re: Jboss is so hard to use and i am thinking choose another
              Joel Vogt Master

              Judging from your previous posts, you had a few small problems and these were answered. I doubt it is jboss that is your biggest problem.

              • 4. Re: Jboss is so hard to use and i am thinking choose another
                Alexander Petty Newbie

                What a foolish comment "qfjiang" has made.

                I have written all forms of j2ee java applications and by far the easiest container to use and deploy on is JBoss.

                Websphere, being the J2EE app container I have the most experience with (not including JBoss), is riddled with bugs and promises from IBM that the next version will be better. (Although I gotta give to IBM for Eclipse and WSAD for that matter)

                Once an aplication is deployed on WebSphere it, for some reason, consumes enormous amounts of RAM forcing you to use clustering if your application has even a light degree of usage load.

                If you think its confusing handcoding deployment descriptors, try using Websphere's Application Deployment Wizard. Invariably you will find that your application did not deploy properly, and since most WAS users know little about the innards of J2EE deployment (and handy tools like ANT and XDOCLET) they are left only with the choice to call IBM at $300.00 per call for tech support which amounts to your company essentially paying to report a bug that should have caught during IBM's beta testing.

                All things considered, Ill go with JBoss everytime I can. It fairly lightweight, very stable, highly customizable, very friendly (as long as you conceptually understand J2EE and are comfortable manipulating xml based conf files), and free. When you need support, there is a global community of developers ready to help you in the spirit of the brotherhood of nerds.

                If something doesnt work and you really want to figure out why. Just look under the "hood" and read the container source code. Maybe you can find the problem, if there is one.
                And if you really want to, you can even pay JBoss Group $300 a call for tech support.

                Ok. I just had to get that off my chest.

                Hey "qfjiang", go use WebSphere or BEA, I dare you. I'll bet you find them to be even less easy for you to learn.

                -Alex

                • 5. Re: Jboss is so hard to use and i am thinking choose another
                  Alexander Petty Newbie

                  What a foolish comment "qfjiang" has made.

                  I have written all forms of j2ee java applications and by far the easiest container to use and deploy on is JBoss.

                  Websphere, being the J2EE app container I have the most experience with (not including JBoss), is riddled with bugs and promises from IBM that the next version will be better. (Although I gotta give to IBM for Eclipse and WSAD for that matter)

                  Once an aplication is deployed on WebSphere it, for some reason, consumes enormous amounts of RAM forcing you to use clustering if your application has even a light degree of usage load.

                  If you think its confusing handcoding deployment descriptors, try using Websphere's Application Deployment Wizard. Invariably you will find that your application did not deploy properly, and since most WAS users know little about the innards of J2EE deployment (and handy tools like ANT and XDOCLET) they are left only with the choice to call IBM at $300.00 per call for tech support which amounts to your company essentially paying to report a bug that should have caught during IBM's beta testing.

                  All things considered, Ill go with JBoss everytime I can. It fairly lightweight, very stable, highly customizable, very friendly (as long as you conceptually understand J2EE and are comfortable manipulating xml based conf files), and free. When you need support, there is a global community of developers ready to help you in the spirit of the brotherhood of nerds.

                  If something doesnt work and you really want to figure out why. Just look under the "hood" and read the container source code. Maybe you can find the problem, if there is one.
                  And if you really want to, you can even pay JBoss Group $300 a call for tech support.

                  Ok. I just had to get that off my chest.

                  Hey "qfjiang", go use WebSphere or BEA, I dare you. I'll bet you find them to be even less easy for you to learn.

                  -Alex

                  • 6. Re: Jboss is so hard to use and i am thinking choose another
                    Alexander Petty Newbie

                    What a foolish comment "qfjiang" has made.

                    I have written all forms of j2ee java applications and by far the easiest container to use and deploy on is JBoss.

                    Websphere, being the J2EE app container I have the most experience with (not including JBoss), is riddled with bugs and promises from IBM that the next version will be better. (Although I gotta give to IBM for Eclipse and WSAD for that matter)

                    Once an aplication is deployed on WebSphere it, for some reason, consumes enormous amounts of RAM forcing you to use clustering if your application has even a light degree of usage load.

                    If you think its confusing handcoding deployment descriptors, try using Websphere's Application Deployment Wizard. Invariably you will find that your application did not deploy properly, and since most WAS users know little about the innards of J2EE deployment (and handy tools like ANT and XDOCLET) they are left only with the choice to call IBM at $300.00 per call for tech support which amounts to your company essentially paying to report a bug that should have caught during IBM's beta testing.

                    All things considered, Ill go with JBoss everytime I can. It fairly lightweight, very stable, highly customizable, very friendly (as long as you conceptually understand J2EE and are comfortable manipulating xml based conf files), and free. When you need support, there is a global community of developers ready to help you in the spirit of the brotherhood of nerds.

                    If something doesnt work and you really want to figure out why. Just look under the "hood" and read the container source code. Maybe you can find the problem, if there is one.
                    And if you really want to, you can even pay JBoss Group $300 a call for tech support.

                    Ok. I just had to get that off my chest.

                    Hey "qfjiang", go use WebSphere or BEA, I dare you. I'll bet you find them to be even less easy for you to learn.

                    -Alex

                    • 7. Re: Jboss is so hard to use and i am thinking choose another
                      Greg Turner Apprentice

                      Alexspetty,

                      So nice to see someone post on the JBoss forum that gets it. I am so tired of reading the naysayers comments, "it hard, the docs have poor grammer, etc" Whine, whine. Thanks for your post.