You want to stop and think about what you are doing before you start configuring such an anti-pattern. I can't belive people still do this. Just because something is technically possible, doesn't mean you should do it.
Colocate Why serialize everything between the servlet and ejb container? This has been discussed so many times before... All I can say is we don't license by the number of cpus the ejb container is deployed on (a major consideration when using other containers where this is the case), there is no need to minimize the ejb container machines. This is usually the real reason people advocate separating servlet and ejb constainers. Pool available via jndi Ridiculous. Let's create a pool to efficiently use resources, but then use each connection from the pool remotely, negating any benefit. The connections will also be held for longer (network latency) and you have to trust the client to use the connection efficiently (i.e. not to hog the resources). Create the pool where it is used, i.e. in the servlet container. Security The only reason not to colocate is because you want the servlet container in the demilitarised zone. If that is true, why have you punctured a hole straight through to your db? And why do you have business logic inside the servlet in the demilitarized zone anyway? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844818#3844818 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844818 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
