RE: [JBoss-user] Tradeoffs between Tomcat/JBoss vs. Tomcat/hancoded?
Should be very similiar for both approach. The development time for EJB may be a bit longer due to the difficult to do testing. If you did a good design the maintainability should be almost the same. The design for tomcat/handcoded has a tendency to be messy while most people follow J2EE blue print when doing EJB design. David -Original Message- From: David M. Karr [mailto:[EMAIL PROTECTED]] Sent: Monday, October 01, 2001 10:24 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Tradeoffs between Tomcat/JBoss vs. Tomcat/hancoded? David == David You [EMAIL PROTECTED] writes: David I did both. Here are some experience. David Tomcat/handcoded: David Good performance(no RMI call), Do Database update yourself only when David needed. David Handling caching yourself..good or bad depends on what your programs David look like. David very difficult to do long transaction handling. David Easy Unit Testing. David Tomcat/JBoss David internal JMS support David Good transaction handling.. David Option to migrate to a Cluster supported Application Server for David fail-over..scalable..etc. Two other issues: How about estimates for the ratio of development time for either approach? How about maintainability? -- === David M. Karr ; Best Consulting [EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004) ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Tradeoffs between Tomcat/JBoss vs. Tomcat/hancoded?
I did both. Here are some experience. Tomcat/handcoded: Good performance(no RMI call), Do Database update yourself only when needed. Handling caching yourself..good or bad depends on what your programs look like. very difficult to do long transaction handling. Easy Unit Testing. Tomcat/JBoss internal JMS support Good transaction handling.. Option to migrate to a Cluster supported Application Server for fail-over..scalable..etc. david -Original Message- From: David M. Karr [mailto:[EMAIL PROTECTED]] Sent: Monday, October 01, 2001 6:27 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] Tradeoffs between Tomcat/JBoss vs. Tomcat/hancoded? Has anyone estimated development time tradeoffs (and others) between a web application developed with Tomcat/JBoss, as opposed to Tomcat/handcoded? That is, a persistence layer implemented with EJB in JBoss, as opposed to a handcoded JDBC persistence layer? Note that I have little interest in the latter, I'm just trying to find convincing arguments for the former to bring sanity to a project I'm committed to. -- === David M. Karr ; Best Consulting [EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004) ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Tradeoffs between Tomcat/JBoss vs. Tomcat/hancoded?
David == David You [EMAIL PROTECTED] writes: David I did both. Here are some experience. David Tomcat/handcoded: David Good performance(no RMI call), Do Database update yourself only when David needed. David Handling caching yourself..good or bad depends on what your programs David look like. David very difficult to do long transaction handling. David Easy Unit Testing. David Tomcat/JBoss David internal JMS support David Good transaction handling.. David Option to migrate to a Cluster supported Application Server for David fail-over..scalable..etc. Two other issues: How about estimates for the ratio of development time for either approach? How about maintainability? -- === David M. Karr ; Best Consulting [EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004) ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
