@ServerOnly annotation on your statusName getter and setter
(Gilead will prevent it to be cloned and merged by beanlib)
- just add a null check condition in your statusName getter and
setter
Regards
Bruno
On 12 mar, 00:06, Itamar Ravid itamar.ira...@gmail.com wrote:
Hi Bruno - first
The best way, IMO, is to not use GWT-RPC, but rather implement an
HttpServlet, that retrieves the data from the database and returns it with
the appropriate Content-Type in response to a GET http request. Then, you
simply place an image in your GWT code, with its source being the path to
the
Hi Bruno - first off, thanks for all of your hard work. Your project is a
real life-saver, and we're using it extensively in our project.
I'd like to report a bug. I have not tested yet with gilead 1.2.2, but I'd
like to report it anyway.
Assume two classes:
public class Status {
Long id;
Awesome! Thanks, Scott.
On Mon, Feb 9, 2009 at 6:33 PM, Scott Blum sco...@google.com wrote:
On Sun, Feb 8, 2009 at 12:11 PM, Itamar Ravid itamar.ira...@gmail.comwrote:
The difficulty arises when using Hosted Mode. First, I have to copy a
modified web.xml to ${project}/tomcat/webapps/ROOT
Hi - I've perused the WAR Design document, but I've several questions that
remained unanswered.
In my project, we use GWT-SL and Gilead - the former for exporting Spring
beans as GWT-RPC services, and the latter for transferring Hibernate-enabled
objects back and forth between the server and
You might want to look into the 'Dynamic Proxy' or 'Stateful Server'
configurations of Gilead. These modes do not impose any technical
inheritance or interface implementation requirements on your POJOs.
Regarding remote services, you'll want to look into GWT-SL - it allows
exporting regular POJOs
