What if you want to keep the object detachable?
On May 12, 10:59 pm, Fred Sauer fre...@google.com wrote:
2009/5/12 Miguel Méndez mmen...@google.com
I must admit that I've not personally researched it. I think that it has
been discussed on the appengine user group however. You may also
I'd recommending reading Ray Cromwell's blog. He goes into detail about the
options you have.
Fred
2009/6/10 savioseb savio...@gmail.com
What if you want to keep the object detachable?
On May 12, 10:59 pm, Fred Sauer fre...@google.com wrote:
2009/5/12 Miguel Méndez mmen...@google.com
*This application is out of date, please click the refresh button on
your browser.*
we also had problems with this and in our case it turned out, that an
old backend-application was still acitve under tomcat/webapps.
then the gui-application always connected to this one instead of the
Check that you are using the matching version of the gwt-servlet.jar (i.e.
everything is 1.6.4 or whatever) and that the correct versions of the
compiled servlets are being used on the server.
Ian
http://examples.roughian.com
2009/5/12 Pavel Byles pavelby...@gmail.com
I tried cleaning the
Ian,
I'm using whatever came with the Google Eclipse Plugin (1.6.4)
When I tried updating the plugin there's nothing to update.
Thanks... anymore ideas?
On Tue, May 12, 2009 at 10:44 AM, Ian Bambury ianbamb...@gmail.com wrote:
Check that you are using the matching version of the
OK, so it's not that, then :-(
I don't know if it's still not fixed, but I've had this error message when
the service is returning null and I was expecting it to return something.
Ian
http://examples.roughian.com
2009/5/12 Pavel Byles pavelby...@gmail.com
Ian,
I'm using whatever came with
Check the 'problems' view in eclipse for any warnings of an out of date
gwt-servlet.jar
Alternatively, delete the jar from you WEB-INF/lib and the use the problems
view to right click and bring back in the proper gwt servlet jar.
HTH
Fred
On May 12, 2009 8:04 AM, Pavel Byles
It looks like you are using ORM. There are a couple of places where GWT
serialization and ORM don't play nice together. An exception should be
getting logged on the server if that is the case.
On Tue, May 12, 2009 at 11:14 AM, Fred Sauer fre...@google.com wrote:
Check the 'problems' view in
Fred,
I did this and Eclipse replaced gwt-servlet.jar.
The problem still persists.
On Tue, May 12, 2009 at 11:14 AM, Fred Sauer fre...@google.com wrote:
Check the 'problems' view in eclipse for any warnings of an out of date
gwt-servlet.jar
Alternatively, delete the jar from you WEB-INF/lib
Miguel,
Thanks for the suggestion, there aren't any errors on the server side.
Here's my ...impl method code:
public ListCountry getAllCountries() {
/*PersistenceManager pm = PMF.get().getPersistenceManager();
Query query = pm.newQuery(Country.class);
try {
ListCountry
Ian,
When I inspect the values during debug the object's being returned are not
null. But even if they were null, shouldn't I be able to return null
anyhow?
On Tue, May 12, 2009 at 11:13 AM, Ian Bambury ianbamb...@gmail.com wrote:
OK, so it's not that, then :-(
I don't know if it's still not
I suspect it has something to do with the object I am returning.
When I use the same service to return a String or a simple class that
contains a String everything works fine.
But when I try to return instances of Country then I get the error.
Any ideas why this happens?
Here is the Country
What if you try to have it not be persistable (comment out the persistence
annotations, rebuild, and return a dummy one that was not instantiated by
the ORM code)? I wonder if this is the ORM and GWT-RPC incompatibility.
On Tue, May 12, 2009 at 1:00 PM, Pavel Byles pavelby...@gmail.com wrote:
I believe the server is trying to persist the enhanced version of
the serializable class, which makes it appear as if the class has
changed, triggering the out-of-date exception. I saw something similar
before switching to separate persistable data objects and DTOs.
2009/5/12 Miguel Méndez
Miguel,
YES!
that's it. As soon as I comment out the @PersistenceCapable it works!
Now I know there are issues w/ GWT and enhanced classes, but exactly how am
I supposed to persist data w/o having that annotation?
2009/5/12 Miguel Méndez mmen...@google.com
What if you try to have it not be
I must admit that I've not personally researched it. I think that it has
been discussed on the appengine user group however. You may also want to
search this group.
The problem, as I understand it, is that enhancement adds fields to the
runtime type. But, GWT-RPC works off of the static
2009/5/12 Miguel Méndez mmen...@google.com
I must admit that I've not personally researched it. I think that it has
been discussed on the appengine user group however. You may also want to
search this group.
The problem, as I understand it, is that enhancement adds fields to the
runtime
Thanks Fred,
I saw this b4 but hesitated to try it. Will try it now.
Thanks
On Tue, May 12, 2009 at 1:59 PM, Fred Sauer fre...@google.com wrote:
2009/5/12 Miguel Méndez mmen...@google.com
I must admit that I've not personally researched it. I think that it has
been discussed on the
18 matches
Mail list logo
