We've had EJB's running on a separate JVM (in fact, separate physcial server) for years, with no performance problems. In fact, scalability wise, it's been to our advantage. With unit tests, EJBs are as testable as anything. In fact, I don't see a point in hosting EJBs locally on the same JVM as the application.
But again, that's getting into politics. Every organisation is different. All I meant to say is that we use JBoss 6 with Tapestry in such a way that it runs our EJBs on a separate physcal server, while Jetty runs our Tapestry app. Prior to Tapestry, we had Tomcat running Struts, pretty much same setup except that application framework was crap. Adam On Thu, May 5, 2011 at 5:30 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Thu, 05 May 2011 18:34:18 -0300, Jabbar <aja...@gmail.com> wrote: > >> Hello Adam, >> >> We've always used JBoss, it's the company standard. I could perhaps use >> Glassfish or Jetty to host the application. The application works >> perfectly >> using the run jetty run eclipse plugin. > > What's the error message when you try to run the application in JBoss? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
