BarZ, I am just nipping out, so i don't have time to give you the full story, but i am sure others will pitch in here.
Don't be intimidated with J2EE; its a big ass umbrella, and the chances of you needing to know all of it, are very slim. Just be aware of what each component is for, so should you hit a problem you can maybe look at a particular API. Tomcat and JBoss. Right, Tomcat is not an application server. Or at least in the definition of a J2EE Application server. Tomcat is only a JSP/Servlet container. Thats it. If you are going to be doing JSP/Servlet work, then you can't go too wrong with Tomcat. JBoss on the other hand *is* a J2EE Application, that also provides Servlets/JSP but also an EJB container. We are talking the likes of BEA'WebLogic, IBM'Websphere, Sun'One etc. If you are planning on looking at any of the other API's within the J2EE edition, then you will need a full blown J2EE server, and since JBoss is free, its an excellent starting point. I was involved with an excellent WROX book that covered this all. [Pay particular attention to the JavaMail chapter! <cough> ;-) ] http://www.n-ary.com/products/javaserverbook.cfm You've got a good grounding in Java ... so just treat each part of the J2EE as just another API. Good luck on your journey, alan EditorInChief JavaDevelopersJournal http://alan.blog-city.com/
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
