Re: Tomcat vs (other container) compatibility
--- HARBOR: http://coolharbor.100free.com/index.htm Now Tomcat is also a cool pojo application server --- - Original Message - From: Mark Thomas [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Sunday, November 18, 2007 2:07 PM Subject: Re: Tomcat vs (other container) compatibility Wade Chandler wrote: As far as others stole Tomcat, I think we need to make sure we always know the entire story Indeed. The other point is that the AL2 license permits this. It isn't theft, it is people/organisations using the software in exactly the way it was intended. Yes... I was being flippant ;) But from a marketing point of view, I think people should now that the ghost (there I do it again;) of Tomcat is in just about every other EJB container out there. In fact I think there should be a list of containers that use forks of Tomcat on the TC site... its just good marketing. People are seeing Tomcat in competition with EJB... I think they should know its a core part of many EJB containers. So they view TC correctly, not as direct competition, but as a subcomponent. Or... people out there, if you making a web site... start with Tomcat, if you later need EJB... pick a container. Tomcat vs EJB is just wrong when people see it as a container war. Its the same reason I went ballistic, when Netbeans 6 defaulted to GlassFish for a WebApp, and didnt even install Tomcat (they have since fixed that). If one is making a simple web site... its just wrong... I think. Large companies sponsor or have sponsored Tomcat and use it in their products... Stole is wrong ;) But then I also think when a container is based on Tomcat, and doesnt expose it as such... thats kinda a like theft;) TC should list those as well ;) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat vs (other container) compatibility
Johnny Kewl wrote: But then I also think when a container is based on Tomcat, and doesnt expose it as such... thats kinda a like theft;) That would be a breach of section 4 of the AL2 license. If you are aware of any such breaches for any Apache software, please let the relevant PMC know. Cheers, Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat vs (other container) compatibility
--- HARBOR: http://coolharbor.100free.com/index.htm Now Tomcat is also a cool pojo application server --- - Original Message - From: Jacob Rhoden [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, November 17, 2007 1:40 PM Subject: Tomcat vs (other container) compatibility Hi, Just wondering if there is anyone who has been or is involved in cross JEE container work, how compatible are tomcat apps with other commercial apps such as OC4J, Websphere, BEA and so on? If you don't use tomcat specific things, does it just work, I ask because the compatibility issue might come up at work. Heres an article from IBM site http://www.ibm.com/developerworks/websphere/library/techarticles/0511_li1/0511_li1.html I have put quite a few TC servlets onto Glassfish... no problem. I think in general you will find very little problems moving Tomcat (A Servlet Container) to one of the above (EJB containers). Both J2EE but they different animals. Tomcat webapps generally migrate easily to most servers because they all stole tomcat to begin with ;) inside most of this EJB containers you will find something that looks very much like Tomcat. So in general no problem... But amongst EJB servers this is not true... ie if you want to move from say WebSphere to Jboss, or Spring or Glassfish... then suicide is a very real possibility ;) Tomcat is actually one of the few common denominators between these servers once you have applied EJB tools, then portability is an issue. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat vs (other container) compatibility
The main point to keep in mind is that Tomcat only implements the Servlet and JSP specifications from JEE, and thus is a Servlet container and is not an EE container. Very important part of the puzzle to keep in mind, so moving from TC to one of the others should be very easy unless of course you are using anything Tomcat specific. In that case you won't be able to just move it without some rewrite. As far as others stole Tomcat, I think we need to make sure we always know the entire story and know whose original investments went into works, though it has come a long long long way since the donation, if we are going to bring it up: http://en.wikipedia.org/wiki/Apache_Tomcat#History Wade - Original Message From: Johnny Kewl [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, November 17, 2007 7:26:41 AM Subject: Re: Tomcat vs (other container) compatibility - Original Message - From: Jacob Rhoden [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, November 17, 2007 1:40 PM Subject: Tomcat vs (other container) compatibility Hi, Just wondering if there is anyone who has been or is involved in cross JEE container work, how compatible are tomcat apps with other commercial apps such as OC4J, Websphere, BEA and so on? If you don't use tomcat specific things, does it just work, I ask because the compatibility issue might come up at work. Heres an article from IBM site http://www.ibm.com/developerworks/websphere/library/techarticles/0511_li1/0511_li1.html I have put quite a few TC servlets onto Glassfish... no problem. I think in general you will find very little problems moving Tomcat (A Servlet Container) to one of the above (EJB containers). Both J2EE but they different animals. Tomcat webapps generally migrate easily to most servers because they all stole tomcat to begin with ;) inside most of this EJB containers you will find something that looks very much like Tomcat. So in general no problem... But amongst EJB servers this is not true... ie if you want to move from say WebSphere to Jboss, or Spring or Glassfish... then suicide is a very real possibility ;) Tomcat is actually one of the few common denominators between these servers once you have applied EJB tools, then portability is an issue. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat vs (other container) compatibility
Michael wrote: Johnny Kewl wrote: --- HARBOR: http://coolharbor.100free.com/index.htm Now Tomcat is also a cool pojo application server --- - Original Message - From: Jacob Rhoden [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, November 17, 2007 1:40 PM Subject: Tomcat vs (other container) compatibility Hi, Just wondering if there is anyone who has been or is involved in cross JEE container work, how compatible are tomcat apps with other commercial apps such as OC4J, Websphere, BEA and so on? If you don't use tomcat specific things, does it just work, I ask because the compatibility issue might come up at work. Heres an article from IBM site http://www.ibm.com/developerworks/websphere/library/techarticles/0511_li1/0511_li1.html I have put quite a few TC servlets onto Glassfish... no problem. no wonder, Glassfish uses TC as servlet container! Actually I think Glassfish uses a fork of the tomcat code from some point in the past. As long as the servlet spec is followed, I would think the servlets would work in either place. --David - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat vs (other container) compatibility
That is more an Application design issue. In short, there are incompatibilities across the various containers. So if you are developing a cross-container application, the simpler it is the more chances of less re-configuration on different containers. However that may be contradictory as more requirements usually results in more complexities. Simple difference, is JNDI. The following are differences in calling a jdbc object called defaultDS: Tomcat/Jetty: java:comp/env/jdbc/defaultDS Orion(Oracle-OC4J)/Tomcat: jdbc/defaultDS JBoss: java:/defaultDS Weblogic: defaultDS And this is just one of the many differences. More off the top of my head, EJBs, Virtual Hosting configuration, etc. Some containers also require container specific XML descriptor in the application e.g. jboss.xml, etc. David Smith wrote: Michael wrote: Johnny Kewl wrote: --- HARBOR: http://coolharbor.100free.com/index.htm Now Tomcat is also a cool pojo application server --- - Original Message - From: Jacob Rhoden [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Saturday, November 17, 2007 1:40 PM Subject: Tomcat vs (other container) compatibility Hi, Just wondering if there is anyone who has been or is involved in cross JEE container work, how compatible are tomcat apps with other commercial apps such as OC4J, Websphere, BEA and so on? If you don't use tomcat specific things, does it just work, I ask because the compatibility issue might come up at work. Heres an article from IBM site http://www.ibm.com/developerworks/websphere/library/techarticles/0511_li1/0511_li1.html I have put quite a few TC servlets onto Glassfish... no problem. no wonder, Glassfish uses TC as servlet container! Actually I think Glassfish uses a fork of the tomcat code from some point in the past. As long as the servlet spec is followed, I would think the servlets would work in either place. --David - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards Gabe Wong NGASI AppServer Manager Application server installation and configuration AUTOMATION http://www.ngasi.com - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
