Re: [JBoss-user] novice

[Norman Rupp]

Title: RE: [JBoss-user] novice

Well, Paul.  It's good that you've come to the open source EJB platforms.  Regarding JBoss, Marc Fleury and Rickard Oberg are INCREDIBLY active developers, and are leading the charge for EJB engines.  We have found that JBoss is getting faster, easier to use, and much more solid with every release.  They release to new specifications in a VERY timely fashin, so you'll be on bleeding edge with JBoss, (and in the world of EJB that can save WEEKS of headaches).  I'm not sure what the deal was with Enhydra, but JBoss comes optionally packaged and configured to run Jakarta-Tomcat, Sun Microsystems implemetation of the Java Servlet 2.2 specification (so you know that when the servlet spec changes, you'll get support from the JBoss crew).  Also, the user groups are very good, and since it's open source, you can just download the source code to figure out why the heck your JDBC Realm object isn't working the way it should.   All in all, I've found that using JBoss with the myriad of useful tools in the Jakarta project (Ant, Struts, Tomcat, Xerces, Junit) is a very good way to remain on the ball, up to date, in the know, and as close to the Sun as possible during development.   I hope this helps.   If I recall, we looked at Enhydra before we settled on JBoss. (back when they were still EJBoss...)  The CTO decided on JBoss (can't tell you his reasoning, but it's been working very well for us, and a little peer pressure never hurt anyone)   Hope this helps.   ~Norman Rupp Web Developer Hypothermic, LLC ----- Original Message ----- From: Paul McLachlan To: [EMAIL PROTECTED] Sent: Monday, June 04, 2001 12:51 AM Subject: RE: [JBoss-user] novice Hi Norman, I too am a novice and have been given the task of evaluating jBoss and jonas/enhydra. Do you  feel jBoss is a better platform. I would like to know why one is better than the other because we would prefer using one of these openSource products rather than weblogic or one of the other expensive ones. Regards, Paul. -----Original Message----- From: Norman Rupp [mailto:[EMAIL PROTECTED]] Sent: Monday, 4 June 2001 12:28 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] novice Boris, First of all, welcome to JBoss / Tomcat land.  You're going to like it here. The first thing that you should know is that all of your applications are going to use port 8080, and the rest should just be left alone.  When you map a context to a web application (you do that in the ejb-jar.xml file in your application's META-INF directory , NOT in any files in the Tomcat directory), it will automatically use the 8080 port.  The other stuff is most likely for something completely different, most likely intended for use by the container. The JBoss application comes with a database called Hypersonic SQL.  I suggest that you use it.  As far as I know, your system will automatically use the Hypersonic Database unless you specify otherwise in the jaws.xml file in your JBoss directory. The classpath issues are a mess.  Your third problem is the definition of an imperfectly thought out application structure, and not enough reliance on build tools such as Ant. (go to jakarta.apache.org to learn more about Ant.) What I suggest you do for your first sample application is to purchase a copy of O'Reilly and associates Enterprise Java Beans (ISBN: 1-56592-869-5), Java Server Pages (ISBN: 1-56592-746-X), and maybe their Java Servlet Programming (don't have the ISBN for that one handy).  These books come with very good sample applications, and have much MUCH more documentation for their sample apps than do the online ones.  I know they're pricy, but they're worth it. I could write an entire site on the importance of using Ant to manage your application developing environment, as well as some of the techniques we employ to manage the constantly changing technology for this.  AS SOON as you figure out JBoss 2.2.2, they'll be releasing the 2.3 version of the JSP API Specification, and there will be another round of upgrading and headaches, and you should try to plan for this. I'll give you a couple of pointers.  I can't elaborate in novel fashion, but you're free to write me back with more of your questions. 1.  Use Ant for compiling, building (i.e. file and directory maintainence within your development tree and application directory... automates problems like the one you're having with the proprietary classpath issues), testing (I suggest using Junit Enterprise Edition for this), database maintenence, repair, and most importantly deployment (a very time consuming process). Ant, once properly configured (a skill in itself) will reduce the time of compilation and deployment from potentially several hours to less than 20 seconds on a stout PII 400 codestation. 2. Don't sweat the vendor-specific jars and stuff.  This becomes much easier to deal with as you gain skill with ant.  We'll talk again soon. ~Norman Rupp Web Developer, Hypothermic LLC ----- Original Message ----- From: "Boris Garbuzov" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, June 03, 2001 6:54 PM Subject: [JBoss-user] novice > Hello to Jboss and Tomcat experts. I just installed the > JBoss-2.2.2_Tomcat-3.2.2 product and curious about some questions. Can > anybody give me a couple of words or useful links? > 1. Dedication of ports 8082 and 8083. The former gives me some kind of > administrative page and the latter - empty body page for any given > context. > 2. Does the product go with any default DB engine or I am responsible > for attaching my own? > 3. In the first tutorial example client had to use some JBoss specific > libraries on classpath. It is strange to me. Is it normal for any client > of any EJB provider? > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user