Hi Josh,
The concept behind attaching GWT to EJBs is that you want to be able
to call methods on your Session beans from EJB.
Sorry I don't have an example to look at right now.
However, if you're willing to mess around you could probably create
some kind of "Hello, world!" Stateless EJB, define a servlet which is
a subclass of the EJB bridge and which has a reference to your
stateless bean, and call it. If not you, someone will one day figure
this out and add an example ... I don't know when. If you get
something started I might be able to help you get past any obstacles
you encounter with some additional emails. Just make sure you read
the javadoc for the EJB bridge servlet class and my blog post on this
subject at
http://www.dobesland.com/2007/08/01/gwt-to-ejb-bridging/
Note that for a *stateless* bean which is implemented in a thread-safe
manner, you can simplify the getBean() implemenation by using an @EJB
annotation; for example:
@EJB MyEJBInterface bean;
public MyEJBInterface getBean() { return bean; }
The example getBean() in the blog post I linked to was written for a
Stateful bean, and Stateful beans are not thread-safe and thus you
must create a new one for each client session.
--
Dobes Vandermeer
Director, Habitsoft Inc.
dob...@habitsoft.com
778-891-2922