You will always need the Tomcat container to host your RPC servlet. In order for your GWT module to communicate with your server, you will need an interface that extends RemoteService which needs to be present in a Servlet container. >From there you will have to look up your ejbs and with EJB3.0 it is easy to do it, you just create the IntialContext and look up your remote beans. I have done a full flow from client-->tomcat COntainer--> App server layer--> ORM(Hibernate) and back with the flow to the client. all the configuration needed on JBOss are 2 xml files that you need to change so you can call your EJB remote interface from your rcp servlet that is hosted over tomcat.
On Mon, Mar 16, 2009 at 6:36 PM, tetsuo <[email protected]>wrote: > > thanks for your fast reply, but iam not looking for a tomcat based > application. the differences within a container based and ejb3 > application is quite big, so the deployment of a tomcat solution, is > not the solution we are looking for. for a web based site, the tomcat > should be enough, for a good design and a distributed computing (3-4-5 > tier) the tomcat container is just a part of a jboss managed > enviroment. look at > http://docs.hp.com/en/5991-5569/img/Apache_Tomcat_Connection.png > > thanks > tet > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
