Hi, > So, if I need webservices and such I should use JBoss?
Figure out which APIs you need and which you don't. "webservices" can be anything and everything ;) Tomcat gives you: servlets, JSPs, JNDI, JSSE. You can connect to databases. You can use frameworks like Struts, Tapestry, etc. You can do all the XML processing you want. I'm not going to go through the whole feature list: you can read that in the release notes. A full J2EE server, such as JBoss, add other things: EJBs, a JMS server, a transaction service (JTA), more management features (although tomcat 4.1.x will be much better in this area). Again, read the release notes for the server you choose. Or get a feature comparison report like: http://www.cutter.com/itreports/j2eev2.html But why are you picking a platform before your app is designed? If you not even sure you need "webservices", you probably aren't ready to select a platform. By the way, people on the list will be happy to help you make choices regarding APIs and containers, but it's a lot easier if you post some requirements / specifications / initial designs... Yoav Shapira Millennium ChemInformatics
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
