are you using external server and not embedded jetty. If so, you have
to deploy your module in exploded mode, that is not compressed. Then
point your devmode to the exploded folder on the server:
-war /home/${env_var:USER}/your-exploded-web.war
This allows using dev mode without having to recompile.
good luck
On 12 Feb., 20:06, Fernando Barbat <[email protected]> wrote:
> Yes, it has a zero argument constructor. As I said, once I recompile,
> undeploy and deploy again, the problem goes away.
>
> I'm using Eclipse and deploy an EAR in Glasfish v3. This EAR contains
> an EJB jar, a GWT WAR and other jars. I noted that
> IncompatibleRemoteServiceException sometimes raises up after I change
> EJB code.
>
> It's not enough with undeploy and deploy. I also have to recompile to
> get everything working.
>
> Maybe it is a problem with packaging. Maybe the RPC generated security
> files are not getting into the EAR properly.
>
> Any idea about how to solve this? Any idea about how to disable that
> security feature?
>
> Thanks.
>
> On 11 feb, 16:58, nacho <[email protected]> wrote:
>
>
>
>
>
>
>
> > I think that your trouble is that the classes compiled to JS are different
> > to the classes that you have in the server.
>
> > Using dev mode after change in a class that I use in a RPC I just reload the
> > page and the problem is gone.
--
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.
