Yup. That does the ticket!
Here's the code if anyone's interested...
The listener...
package com.inexas.test.server;
import javax.servlet.*;
public class AppStarter implements ServletContextListener {
public void contextInitialized(ServletContextEvent event) {
@ManyToMany relationships are not supported in the current version.
Example Library --- Book
The tutorials suggest that they can be modeled with a ListKey
pointing to the other object in each class. When implementing this I
suspect that this forces an inefficient query to populate the, say
Anyone know of a nice way of initializing the server before the client
gets busy.
The only thing I can think of is overriding init() in every
*.serverXServerImpl and have it call my initialization stuff, e.g.
@Override
public void init() throws ServletException {
Dumb question but did you start your app by running it or in debug mode?
__
Keith Whittingham
Eichstrasse 3, CH-8135, Langnau am Albis
http://www.whittingham.ch
keithwhitting...@mac.com
(M) +41 79 820 6216
On Jun 9, 2009, at 1:54 PM, Peter Kirklewski wrote:
Hi
You should get the first window which is titled Google Web Toolit
Hosted Model / Port 8080 and then a second window with your
application running in it with a Google Web Toolkit logo in the top
right corner.
On Jun 9, 2009, at 2:07 PM, Peter Kirklewski wrote:
There is no such ting as a
for the file that you're breakpointing.
__
Keith Whittingham
Eichstrasse 3, CH-8135, Langnau am Albis
http://www.whittingham.ch
keithwhitting...@mac.com
(M) +41 79 820 6216
On Jun 9, 2009, at 4:16 PM, Peter Kirklewski wrote:
I'm getting both windows in the second
From an architectural point of view I don't think it's very clean to
have classes that belong to the server side on the client side. Sooner
or later I'd regret it I'm sure. No, the more I play around, the more
I like the model I proposed. The OO model on the client side is likely
to be
Inside your xom.xxx.server.Xxxx extends RemoteServiceServlet class you
can call getThreadLocalRequest() and that will give you your servlet
request so you can play with the query (the URL argument list) cookies
and whatever
I want to pass my GWT application a recordID at the time I call
Not an expert but here's a fast answer that I think is right.
The fact that code finds itself somewhere under .../client means that
it will be X-compiled into JavaScript. If it's not there it won't. I
had to move classes there to solve the problem.
The reason for this, I guess, is that you
